Product Strategist
alirezarezvani/claude-skills
OKR cascade toolkit for product leaders: generates aligned company-to-team OKRs from five strategy types and scores how well they line up.
Analyse competitor moves and translate them into strategic implications for your product roadmap.
Install Competitor Signal Tracker
$ npx skills add mohitagw15856/pm-claude-skills --skill competitor-signal-tracker -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills competitor-signal-tracker --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/competitor-signal-tracker .claude/skills/competitor-signal-tracker && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "competitor-signal-tracker" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/competitor-signal-tracker into .claude/skills/competitor-signal-tracker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-signal-tracker", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/competitor-signal-trackerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill competitor-signal-tracker -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills competitor-signal-tracker --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/competitor-signal-tracker .agents/skills/competitor-signal-tracker && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "competitor-signal-tracker" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/competitor-signal-tracker into .agents/skills/competitor-signal-tracker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-signal-tracker", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill competitor-signal-tracker -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills competitor-signal-tracker --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/competitor-signal-tracker .cursor/skills/competitor-signal-tracker && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "competitor-signal-tracker" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/competitor-signal-tracker into .cursor/skills/competitor-signal-tracker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-signal-tracker", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/competitor-signal-tracker--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill competitor-signal-tracker -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills competitor-signal-tracker --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/competitor-signal-tracker .gemini/skills/competitor-signal-tracker && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "competitor-signal-tracker" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/competitor-signal-tracker into .gemini/skills/competitor-signal-tracker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-signal-tracker", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills competitor-signal-trackerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill competitor-signal-tracker -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/competitor-signal-tracker .github/skills/competitor-signal-tracker && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "competitor-signal-tracker" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/competitor-signal-tracker into .github/skills/competitor-signal-tracker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-signal-tracker", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill competitor-signal-tracker -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills competitor-signal-tracker --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/competitor-signal-tracker .opencode/skills/competitor-signal-tracker && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "competitor-signal-tracker" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/competitor-signal-tracker into .opencode/skills/competitor-signal-tracker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-signal-tracker", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
competitor-signal-tracker- GitHub stars
- 1.4k
- Token cost
- ~969 tokens
- SKILL.md length
- 430 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Analyse competitor moves and translate them into strategic implications for your product roadmap.
- Works in 6 steps: For each competitor update provided,… → Assess: Is this reactive (responding to… → Rate strategic threat level: High /… → …
- A competitor announces a new feature
- SKILL.md covers Required Inputs, Signal Categories to Track, Process and Output Structure, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Competitor Signal Tracker is an agent skill from mohitagw15856/pm-claude-skills. Analyse competitor moves and translate them into strategic implications for your product roadmap. Use when a competitor announces a new feature, pricing change, partnership, or strategic shift, or when producing a periodic competitive intelligence report. Produces a categorised signal analysis with reactive-vs-proactive assessment, threat ratings, specific roadmap implications, and recommended responses with owners. For a recurring whole-market briefing use competitive-intelligence-monitor instead.
Its SKILL.md is about 970 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering Competitor analysis and Product roadmapping. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- A competitor announces a new feature
- Strategic shift
- Producing a periodic competitive intelligence report
Example prompts
- “/competitor-signal-tracker”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- For each competitor update provided, categorise the signal type
- Assess: Is this reactive (responding to market) or proactive (setting direction)?
- Rate strategic threat level: High / Medium / Low / Watch
- Connect to your roadmap: does this accelerate, validate, or challenge any of your bets?
- Recommend a response: Accelerate existing initiative / Deprioritise / Monitor / Investigate further
- Validate — Confirm every High threat has a specific recommended response with an owner. "Monitor" is not an acceptable response for…
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Competitor Signal Tracker loads about 969 tokens when it runs. Until then it costs about 132 tokens; SKILL.md has 430 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 430 words, ~969 tokens.
Download SKILL.mdSave it as
.claude/skills/competitor-signal-tracker/SKILL.md (or your agent's skills folder).- name
- competitor-signal-tracker
- description
- Analyse competitor moves and translate them into strategic implications for your product roadmap. Use when a competitor announces a new feature, pricing change, partnership, or strategic shift, or when producing a periodic competitive intelligence report. Produces a categorised signal analysis with reactive-vs-proactive assessment, threat ratings, specific roadmap implications, and recommended responses with owners. For a recurring whole-market briefing use competitive-intelligence-monitor instead.
Competitor Signal Tracker Skill
Turn scattered competitor information into structured strategic intelligence — not just "what they did" but "what it means for us."
Required Inputs
Ask the user for these if not provided:
- Competitor name(s) and the signals/updates to analyse
- Your product's current roadmap or strategic priorities (to assess relevance)
- Time period the signals cover (this week, this month, etc.)
Signal Categories to Track
- Product signals: New features, removals, UX changes, beta programmes
- Pricing signals: Changes to tiers, free limits, enterprise terms
- Hiring signals: Job postings that reveal strategic bets (e.g., hiring ML engineers = AI investment)
- Partnership signals: Integrations, acquisitions, ecosystem moves
- Messaging signals: Changes in positioning, target audience, value proposition
Process
- For each competitor update provided, categorise the signal type
- Assess: Is this reactive (responding to market) or proactive (setting direction)?
- Rate strategic threat level: High / Medium / Low / Watch
- Connect to your roadmap: does this accelerate, validate, or challenge any of your bets?
- Recommend a response: Accelerate existing initiative / Deprioritise / Monitor / Investigate further
- Validate — Confirm every High threat has a specific recommended response with an owner. "Monitor" is not an acceptable response for High-rated threats.
Output Structure
Competitive Intelligence Report — [Date]
[Competitor Name]
Signal: [What they did] Signal Type: [Product / Pricing / Hiring / Partnership / Messaging] Reactive or Proactive: [assessment] Threat Level: [High / Medium / Low / Watch] Implication for Us: [Specific connection to our roadmap or strategy] Recommended Response: [Action + owner + timeline]
Strategic Summary
[2-3 sentences on the overall competitive landscape shift this period]
Show full SKILL.md (182 more words)Show less
Anti-Patterns
- Do not rate a signal as High threat without explaining the specific roadmap item or customer segment it threatens — unjustified threat ratings lose credibility over time
- Do not treat a hiring signal as definitive proof of a strategic bet — hiring signals require corroboration from product, messaging, or pricing signals before acting on them
- Do not conflate a competitor's announcement with a competitor's shipped capability — press releases and blog posts often describe aspirations, not production features
- Do not recommend "accelerate existing initiative" for every High signal — sometimes the right response is to differentiate harder in an adjacent area rather than race the competitor directly
Quality Checks
- Every signal is categorised (not just described)
- Threat level is justified — not assigned arbitrarily
- High-threat signals have specific recommended responses (not "monitor")
- Implications connect to specific roadmap items or strategic bets
- Strategic summary gives a landscape-level view, not just a list of individual signals
Example Trigger Phrases
- "A competitor just launched this feature: what does it mean for us?"
- "Analyse this competitor's price change."
- "What does their new partnership signal?"
- "Write this month's competitive intelligence report."
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/competitor-signal-tracker of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Competitor Signal Tracker next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Competitor Signal Tracker this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~969 | Automated safety check: Pass | MIT | |
| Product Strategistalirezarezvani/claude-skills | 28k | 2 repos | ~1.8k | Automated safety check: Pass | MIT | |
| Product Competitive AnalysisFokkyp/claude-skills | 226 | — | ~1.2k | Automated safety check: Pass | None | |
| Prd V02 Competitive Landscape Mappingmattgierhart/PRD-driven-context-engineering | 180 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Building ProductGTM-Strategist/gtm-strategist-skills | 264 | — | ~5.8k | Automated safety check: Pass | MIT | |
| Strategizeghaida/intent | 207 | — | ~6.1k | Automated safety check: Pass | CC0-1.0 |
Similar skills
Product Competitive Analysis
Fokkyp/claude-skills
Produces product-manager competitive analysis reports in Chinese, with a confirm-first scoping gate, three-phase evidence collection and single or multi-product modes.
Prd V02 Competitive Landscape Mapping
mattgierhart/PRD-driven-context-engineering
Map the competitive landscape before positioning your product for PRD v0.2 Market Definition.
Building Product
GTM-Strategist/gtm-strategist-skills
A skill your agent uses when the user needs to define their MVP, create a product roadmap, plan metrics and tracking, refine their value proposition with JTBD, or run usability tests.
Strategize
ghaida/intent
Frames product design problems before solutions exist. An agent skill from ghaida/intent.
Product Development
gustavscirulis/snapgrid
End-to-end product development for iOS/macOS apps. An agent skill from gustavscirulis/snapgrid.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Questions about Competitor Signal Tracker
What does Competitor Signal Tracker do?
Analyse competitor moves and translate them into strategic implications for your product roadmap. Competitor Signal Tracker is an agent skill from mohitagw15856/pm-claude-skills. Analyse competitor moves and translate them into strategic implications for your product roadmap.
When should I use Competitor Signal Tracker?
Competitor Signal Tracker fits situations like: A competitor announces a new feature; strategic shift; producing a periodic competitive intelligence report.
How do I install Competitor Signal Tracker in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill competitor-signal-tracker -a claude-code`. Or copy the skill folder (skills/competitor-signal-tracker in mohitagw15856/pm-claude-skills) into .claude/skills/competitor-signal-tracker in your project. Claude Code loads it when a task matches its description.
How do I install Competitor Signal Tracker in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill competitor-signal-tracker -a codex`. Or copy the skill folder (skills/competitor-signal-tracker in mohitagw15856/pm-claude-skills) into .agents/skills/competitor-signal-tracker in your project. Codex loads it when a task matches its description.
Can I use Competitor Signal Tracker in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill competitor-signal-tracker -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/competitor-signal-tracker, .gemini/skills/competitor-signal-tracker, .github/skills/competitor-signal-tracker and .opencode/skills/competitor-signal-tracker in your project.
What does Competitor Signal Tracker need to run?
SKILL.md names no scripts, command-line tools or credentials: Competitor Signal Tracker is instructions for the agent only.
Does Competitor Signal Tracker access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Competitor Signal Tracker safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Competitor Signal Tracker use?
Competitor Signal Tracker is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Competitor Signal Tracker use?
About 969 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Competitor Signal Tracker?
Skills that share tags, products or a category with Competitor Signal Tracker: Product Strategist (alirezarezvani/claude-skills, 28k stars), Product Competitive Analysis (Fokkyp/claude-skills, 226 stars), Prd V02 Competitive Landscape Mapping (mattgierhart/PRD-driven-context-engineering, 180 stars) and Building Product (GTM-Strategist/gtm-strategist-skills, 264 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Competitor Signal Tracker?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.