mohitagw15856/competitive-analysis
skills/competitive-analysis/SKILL.md
Analyze competitors and create competitive landscape documentation with feature matrices, positioning maps, and strategic recommendations. Use when asked to analyze competitors, create competitive analysis, compare features with competitors, build a competitive landscape, track competitive positioning, or prepare sales battlecard inputs. Produces structured competitor profiles, feature comparison matrix, win/loss analysis, and prioritised strategic recommendations. For a one-off teardown of a single rival use competitor-teardown; for a recurring market briefing use competitive-intelligence-monitor.
$ install --global
skillsauthnpx skillsauth add mohitagw15856/pm-claude-skills competitive-analysisInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jul 2, 2026, 6:51 AM287.1s1 file scanned
SKILL.md
- name:
- competitive-analysis
- description:
- Analyze competitors and create competitive landscape documentation with feature matrices, positioning maps, and strategic recommendations. Use when asked to analyze competitors, create competitive analysis, compare features with competitors, build a competitive landscape, track competitive positioning, or prepare sales battlecard inputs. Produces structured competitor profiles, feature comparison matrix, win/loss analysis, and prioritised strategic recommendations. For a one-off teardown of a single rival use competitor-teardown; for a recurring market briefing use competitive-intelligence-monitor.
Competitive Analysis Skill
Create structured competitive analyses for product decision-making.
Reads from / Writes to the Brain
If a professional-brain (brain/) exists, ground in it instead of re-asking for what you already know:
- Read first:
knowledge/(market + positioning) and competitorentities/. Runpython3 ../professional-brain/scripts/brain_query.py ./brain "<competitor or market>"and carry each fact's provenance tag through — a competitor claim from a press release is[external], not[data]. - 📥 Propose to the Brain: after producing, propose recording new competitor facts to
knowledge/([external]) and creating/updating competitorentities/. Show them, get a yes, then write with../professional-brain/scripts/brain_write.py … --commit(append-only, dry-run by default).
Required Inputs
Ask the user for these if not provided:
- Your product or company (what you're comparing against)
- Competitors to analyze (or ask to identify the top 3-5)
- Analysis focus (full landscape / feature comparison / pricing / positioning / win-loss)
- Audience (product team / leadership / sales / board)
Process
- Gather competitor information from provided inputs and available context
- Build profiles for each competitor
- Create feature comparison matrix on dimensions that matter to the user's customers
- Analyze pricing and positioning
- Identify win/loss patterns and strategic implications
- Validate — Confirm all claims reference a specific source or are flagged as assumptions. Verify feature comparisons note quality differences, not just presence/absence.
Output Structure
1. Executive Summary
- Market Position: Where we stand relative to competitors
- Key Findings: Top 3-5 insights
- Strategic Implications: What this means for the roadmap
2. Competitor Profiles
For each competitor:
- Company Overview: Size, funding, market position
- Target Customer: Who they serve
- Value Proposition: Core positioning
- Strengths / Weaknesses: What they do well and where they fall short
- Recent Activity: Major updates, funding, announcements
3. Feature Comparison Matrix
| Feature | Us | Competitor A | Competitor B | Competitor C | |---------|-----|--------------|--------------|--------------| | [Feature] | ✅ Full | ⚠️ Limited | ❌ None | ✅ Full |
Legend: ✅ Full (production-ready) · ⚠️ Limited/Beta · ❌ None
Include notes on quality and implementation differences where significant.
4. Pricing Comparison
| Plan | Us | Competitor A | Competitor B | |------|-----|--------------|--------------| | Free/Trial | [price] | [price] | [price] | | Pro | [price] | [price] | [price] | | Enterprise | [price] | [price] | [price] |
5. Market Positioning Map
Position competitors on two key dimensions relevant to the market:
- Y-Axis: [e.g., Enterprise vs. SMB]
- X-Axis: [e.g., Simple vs. Comprehensive]
Whitespace Opportunities: [Underserved segments]
6. Win/Loss Analysis
Why We Win:
- Better at: [specific capabilities]
- Customers who value: [what matters to them]
Why We Lose:
- When customers need: [specific requirements]
- Their advantage: [what tips the decision]
7. Strategic Recommendations
Immediate Actions (0-3 months):
- [Action] — [Rationale]
Medium-term (3-12 months):
- [Action] — [Rationale]
Anti-Patterns
- [ ] Do not present competitor feature claims as facts without citing a source or flagging them as assumptions — outdated or incorrect feature data misleads sales and product decisions
- [ ] Do not build a competitive analysis that only covers features — pricing, messaging, go-to-market motion, and who they hire for are equally strategic signals
- [ ] Do not treat all buyers as identical — the same product may win against Competitor A in the enterprise segment and lose in SMB; segment-specific win/loss matters
- [ ] Do not soften weaknesses and threats in the SWOT to avoid internal discomfort — an honest SWOT is only useful if the negatives are real
Quality Checks
- [ ] All competitor claims cite a source or are flagged as assumptions
- [ ] Feature comparison notes quality differences, not just feature presence
- [ ] Strategic recommendations are specific actions, not generic advice
- [ ] Win/loss analysis reflects customer perspective, not internal assumptions
- [ ] Different customer segments are considered (not all buyers value the same things)
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