mohitagw15856/competitive-intelligence-monitor
skills/competitive-intelligence-monitor/SKILL.md
Monitor competitor signals and surface strategic implications for your roadmap. Use when asked to monitor competitors, track the competitive landscape, produce a competitive briefing, or understand what has changed in the market this week or month. Produces a structured intelligence brief with high/medium/low priority signals, roadmap implications, and a strategic landscape summary. For a single competitor announcement use competitor-signal-tracker; for a one-off deep dive use competitor-teardown.
$ install --global
skillsauthnpx skillsauth add mohitagw15856/pm-claude-skills competitive-intelligence-monitorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security scan pending...
This skill is queued for security scanning. Results will appear when the scan completes.
SKILL.md
- name:
- competitive-intelligence-monitor
- description:
- Monitor competitor signals and surface strategic implications for your roadmap. Use when asked to monitor competitors, track the competitive landscape, produce a competitive briefing, or understand what has changed in the market this week or month. Produces a structured intelligence brief with high/medium/low priority signals, roadmap implications, and a strategic landscape summary. For a single competitor announcement use competitor-signal-tracker; for a one-off deep dive use competitor-teardown.
Competitive Intelligence Monitor Skill
Turn scattered competitor updates into structured weekly intelligence — not just "what they did" but "what changed since last week and what it means for us."
Required Inputs
Ask the user for these if not provided:
- Competitors to monitor (list of company names)
- Your current roadmap or strategic priorities (to assess relevance of signals)
- Previous brief or last run summary (for diff mode — what's new vs. last time)
- Time period (this week, this month)
Signal Categories to Monitor
- Product signals: New features, removals, UX changes, beta programmes
- Pricing signals: Changes to tiers, free limits, enterprise terms
- Hiring signals: Job postings revealing strategic bets
- Partnership signals: Integrations, acquisitions, ecosystem moves
- Messaging signals: Changes in positioning, audience, value proposition
Process
First Run (Full Report)
- For each competitor provided, scan all five signal categories
- Categorise each signal found
- Assess: reactive (responding to market) or proactive (setting direction)?
- Rate threat level: High / Medium / Low / Watch
- Connect each signal to a specific item on the provided roadmap
- Recommend response: Accelerate / Deprioritise / Monitor / Investigate
- Validate — Every High signal must have a specific recommended action and owner. "Monitor" is only acceptable for Low and Watch ratings.
Subsequent Runs (Diff Only)
- Compare current signals against previous run summary
- Output ONLY what is new or changed since last run
- Flag if a previously Low signal has escalated to High
- Keep output under 300 words — brevity is the point
Output Structure
Competitive Intelligence Brief — [Date]
New Since Last Run: [n signals]
🔴 High Priority
[Competitor]: [Signal] → [Implication] → [Recommended action + owner]
🟡 Watch
[Competitor]: [Signal] → [Why it matters now]
✅ No Change
[Competitors with no new signals this week]
This Week's Strategic Summary: [2 sentences max — what is the overall competitive landscape doing?]
Anti-Patterns
- [ ] Do not mark a signal as Low priority simply because it is new and unfamiliar — unknown competitive moves often deserve investigation before dismissal
- [ ] Do not provide "monitor" as the recommended response for a High-priority signal — High signals require a specific action with a named owner
- [ ] Do not include signals from competitors that are not relevant to the stated roadmap or strategic priorities — noise reduces the brief's usefulness and trains the team to ignore it
- [ ] Do not produce a diff-mode brief that is longer than the full report — if the diff output exceeds 300 words, it is a full report, not a diff
Quality Checks
- [ ] Every High-priority signal has a specific response action and owner
- [ ] Signals are categorised (not just listed as "they did X")
- [ ] Roadmap connections are specific (not "generally relevant")
- [ ] Diff mode output is under 300 words
- [ ] Strategic summary describes the landscape trend, not just repeats individual signals
Related Skills
mohitagw15856/win-loss-analysis
business
VerifiedTrustedCommunity
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
1,117SKILL.mdUpdated Jul 2, 2026
mohitagw15856/which-skill
development
VerifiedTrustedCommunity
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
1,117SKILL.mdUpdated Jul 2, 2026
mohitagw15856/vuln-triage
testing
VerifiedTrustedCommunity
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
1,117SKILL.mdUpdated Jul 2, 2026
mohitagw15856/voice-of-customer-program
development
VerifiedTrustedCommunity
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.
1,117SKILL.mdUpdated Jul 2, 2026