compete
Skill0 starsChanged 8 months agoMITView on GitHub
Competitive Intel mode. Deep competitive analysis: positioning maps, battlecards, win/loss patterns, differentiation strategy. Not a feature comparison table — a strategic assessment with actionable implications for product and sales.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- simota/agent-skillstheir own version, first seen Oct 23, 2026
- MysterionRise/ctf-kittheir own version, first seen Oct 13, 2026
- akachandan1/proofstacktheir own version, first seen Oct 11, 2026
- InSciCo/i-frameworktheir own version, first seen Jul 13, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- simota/agent-skills★ 96same name
- MysterionRise/ctf-kit★ 12same name
- InSciCo/i-framework★ 4same name
- akachandan1/proofstack★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- briefSkill
- launchSkill
- metricsSkill
- prd-reviewSkill
- prdSkill
- prioritizeSkill
- retroSkill
- sprintSkill
- storiesSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 30
If your competitive analysis doesn't change at least one product decision or one sales talking point, it was a waste of time.
- Distinctive: line 223
Use evidence, not opinion.
- Distinctive: line 227
After the landscape analysis, pause: "Does this match your view of the competitive landscape?
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
{{PREAMBLE}}
Competitive Analysis Mode
Philosophy
A feature comparison table is not competitive analysis. Checking boxes tells you what competitors HAVE. It doesn't tell you what they're GOOD at, where they're GOING, or why customers choose them over you.
Competitive analysis should answer three questions:
- Why do we win? (Our actual advantages, not what we wish were advantages)
- Why do we lose? (The real reasons, not the comfortable ones)
- What should we do about it? (Specific product and positioning actions)
If your competitive analysis doesn't change at least one product decision or one sales talking point, it was a waste of time.
Input
Ask the user (via AskUserQuestion):
What kind of competitive analysis do we need?
RECOMMENDATION: Choose A for a comprehensive landscape analysis. Choose C if you have an urgent deal situation.
A) Full landscape — analyze our competitive position across the market B) Head-to-head — deep dive on 1-2 specific competitors C) Battlecard — sales-ready competitive talking points for active deals D) Market positioning — help us find/refine our positioning
Full Landscape Analysis
Step 1: Market Map
MARKET MAP: [Category Name]
═══════════════════════════
Market size: [TAM/SAM/SOM if available, or order of magnitude]
Growth rate: [% YoY or trend]
Key trends: [3-5 forces reshaping this market]
COMPETITIVE LANDSCAPE:
┌─────────────────────────────────────────────────────┐
│ Enterprise │
│ │
│ [Competitor A] ● ● [Competitor B] │
│ │
│ ● [US] │
│ │
│ [Competitor C] ● ● [Competitor D] │
│ │
│ SMB │
├───────────────────┬─────────────────────────────────┤
│ Point Solution │ Platform │
└───────────────────┴─────────────────────────────────┘
Positioning axis rationale:
- X-axis: [Why this dimension matters]
- Y-axis: [Why this dimension matters]Choose axes that reveal strategic insight. "Features vs. Price" is boring. "Time-to-value vs. Customizability" or "Self-serve vs. High-touch" reveals actual competitive dynamics.
Step 2: Competitor Deep Dives
For each significant competitor:
COMPETITOR: [Name]
══════════════════
Overview: [1-2 sentences — what they do, who they serve]
Founded: [Year] | Funding: [Amount/Stage] | Est. Revenue: [Range]
Target customer: [Who they sell to — be specific]
Pricing model: [How they charge]
STRENGTHS (things they're genuinely better at):
1. [Strength] — Evidence: [How you know — reviews, market share, win/loss data]
2. [Strength] — Evidence: [Source]
3. [Strength] — Evidence: [Source]
WEAKNESSES (honest gaps — not just things they don't have):
1. [Weakness] — Evidence: [Source]
2. [Weakness] — Evidence: [Source]
STRATEGIC DIRECTION (where they're heading):
- Recent moves: [Product launches, partnerships, hiring patterns, funding]
- Likely next: [What they'll probably do in 6-12 months]
- Threat level: [Low/Med/High] — [Why]
WIN/LOSS AGAINST THEM:
- We win when: [Specific scenarios — buyer profile, use case, evaluation criteria]
- We lose when: [Specific scenarios — be honest]
- Key differentiator: [The one thing that swings deals]Step 3: Differentiation Matrix
DIFFERENTIATION MATRIX
═══════════════════════
| Dimension | Us | Comp A | Comp B | Comp C |
|-----------|-----|--------|--------|--------|
| [Dimension 1] | [Rating + note] | [Rating] | [Rating] | [Rating] |
| [Dimension 2] | [Rating + note] | [Rating] | [Rating] | [Rating] |
| [Dimension 3] | [Rating + note] | [Rating] | [Rating] | [Rating] |
Rating: ●●●●● (5=leader) to ● (1=lagging)
UNIQUE to us (no competitor has this):
- [Capability/approach]
PARITY (everyone has this — not a differentiator):
- [Capability] — Don't lead with this in sales
TABLE STAKES (must have but doesn't win deals):
- [Capability]Differentiation rules:
- "We have more features" is not differentiation. Everyone claims that.
- Differentiation must be valued by the buyer. Being different in a way nobody cares about is irrelevant.
- The best differentiation is architectural (hard for competitors to copy), not feature-level (easy to copy).
Step 4: Strategic Implications
STRATEGIC IMPLICATIONS
═════════════════════
PRODUCT:
1. [Build/invest in X] — because: [competitive reasoning]
2. [Don't build Y] — because: [competitive reasoning — let competitor own this]
3. [Accelerate Z] — because: [competitive window is closing]
POSITIONING:
1. [Lead with this narrative] — because: [it highlights our strength and their weakness]
2. [Stop saying this] — because: [competitor is stronger here, it invites comparison]
3. [Reframe this] — from [old framing] to [new framing] because [reason]
SALES:
1. [When competing against A, emphasize...] — because: [A is weak here]
2. [When competing against B, emphasize...] — because: [B can't match this]
3. [Avoid this topic against C] — because: [C wins this comparison]Battlecard Mode
Quick, sales-ready competitive cards. One page per competitor.
BATTLECARD: [Competitor Name]
═════════════════════════════
Updated: [Date] | Deals encountered: [N] | Win rate against them: [%]
IN 30 SECONDS:
[Who they are, what they do, why a prospect might consider them. 3 sentences.]
THEIR PITCH:
"[What their sales team says — the narrative they lead with]"
OUR COUNTER:
"[How to reframe — acknowledge their strength, pivot to our advantage]"
LANDMINES (questions to plant in the prospect's mind):
1. "Ask them about [topic]" — [Why this hurts them]
2. "Ask them about [topic]" — [Why this hurts them]
3. "Ask them about [topic]" — [Why this hurts them]
TRAPS (questions they'll ask that are designed to make us look bad):
1. "[Their question]" — Our answer: "[Response that reframes]"
2. "[Their question]" — Our answer: "[Response that reframes]"
WE WIN WHEN:
- [Buyer profile / use case / evaluation criteria that favors us]
WE LOSE WHEN:
- [Buyer profile / use case / evaluation criteria that favors them]
- WHAT TO DO: [Disqualify early, or adjust approach]
KNOCKOUT PUNCH (our single strongest differentiator against them):
"[One sentence that ends the comparison in our favor]"Completion Summary
COMPETITIVE ANALYSIS SUMMARY
═════════════════════════════════════
| Competitors analyzed | ___ |
| Market positioning | [Our position in 1 sentence] |
| Primary differentiator | [Our #1 advantage] |
| Primary vulnerability | [Our #1 weakness to address] |
| Product recommendations | ___ |
| Positioning recommendations | ___ |
| Battlecards generated | ___ |
═════════════════════════════════════
Ready for: /prd (to inform feature decisions) or /brief --audience exec (to present to leadership)Formatting Rules
- Use evidence, not opinion. "We're better at X" needs proof.
- Be honest about weaknesses. The sales team will encounter them regardless — better to prepare.
- Battlecards are living documents. Note the date and review frequency.
- Positioning maps use ASCII art for portability
- After the landscape analysis, pause: "Does this match your view of the competitive landscape? Any competitors I should dig deeper on?"
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

