competitive-brief
Skill1 starsChanged 7 months agoMITView on GitHub
Create a competitive analysis brief for one or more competitors or a feature area. Use when informing product strategy or feature prioritization, building sales battle cards, prepping board or investor materials, or deciding where to differentiate vs. match. Trigger phrases: "competitive analysis", "competitor comparison", "how do we compare to", "battle card for", "competitive landscape", "what is X doing", "feature comparison", "competitive brief on", "analyze our competitors", "positioning vs"
8 other projects use a version of this.
Adopted by
Most recently taken up by
- Alter-ai/skill-labtheir own version, first seen Nov 15, 2026
- AndyMelnykov/pm-loopstheir own version, first seen Oct 20, 2026
- erickdronski/gtm-skillstheir own version, first seen Oct 16, 2026
- anthropics/knowledge-work-pluginstheir own version, first seen Oct 13, 2026
- shahbazaliofficial/Claude-Skillstheir own version, first seen Oct 13, 2026
- vantionlabs/saas-startertheir own version, first seen Oct 9, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- anthropics/knowledge-work-plugins★ 36ksame name
- vantionlabs/saas-starter★ 9same name
- AndyMelnykov/pm-loops★ 1same name
- Alter-ai/skill-lab★ 0same name
- erickdronski/gtm-skills★ 0same name
- IcodeNet/agent-skills★ 0same name
- KevinReactiv8/claude-skills★ 0same name
- shahbazaliofficial/Claude-Skills★ 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 repository164 other files it gives its agents.
- instrument-data-to-allotropeSkill
- literature-reviewSkill
- nextflow-developmentSkill
- scientific-problem-selectionSkill
- scvi-toolsSkill
- single-cell-rna-qcSkill
- discover-brandSkill
- enforce-voiceSkill
- generate-guidelinesSkill
- csat-reportSkill
- customer-escalationSkill
- customer-researchSkill
- draft-responseSkill
- kb-articleSkill
- sentiment-analysisSkill
- ticket-triageSkill
- analyzeSkill
- build-dashboardSkill
- create-vizSkill
- data-context-extractorSkill
- data-modelingSkill
- data-pipelineSkill
- etl-designSkill
- explore-dataSkill
- sql-queriesSkill
- statistical-analysisSkill
- validate-dataSkill
- write-querySkill
- accessibility-reviewSkill
- component-librarySkill
- design-critiqueSkill
- design-handoffSkill
- design-systemSkill
- frontend-designSkill
- research-synthesisSkill
- user-researchSkill
- ux-copySkill
- wireframingSkill
- Agent DevelopmentSkill
- CLAUDE.md ManagementSkill
- MCP Server BuilderSkill
- Plugin DevelopmentSkill
- Prompt EngineeringSkill
- Skill CreatorSkill
- curriculum-designSkill
- lesson-planningSkill
- quiz-generatorSkill
- study-guideSkill
- tutoringSkill
- api-designSkill
- architectureSkill
- ci-cd-pipelineSkill
- code-reviewSkill
- database-migrationSkill
- debugSkill
- dependency-auditSkill
- deploy-checklistSkill
- documentationSkill
- error-handlingSkill
- git-workflowSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
5
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 12
Create structured competitive analysis briefs that inform product strategy, sales positioning, and executive decision-making.
- Distinctive: line 25
If the user provides a competitor name without context, ask: "What dimension matters most right now -- are you trying to win deals against …
- Distinctive: line 53
Use: Full / Partial / Beta / None / Unknown.
- Distinctive: line 57
Place competitors on two axes most relevant to the market:
- Distinctive: line 138
Keep to one page per competitor
“Common” is measured: kept by at least 6 in 10 of the 8 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
Competitive Analysis Brief
Create structured competitive analysis briefs that inform product strategy, sales positioning, and executive decision-making. Compare features, pricing, positioning, strengths, and weaknesses.
Workflow
Step 1: Scope the Analysis
Clarify before starting:
- Competitors: Which specific companies or products? Limit to 2-4 for depth.
- Dimensions: Features, pricing, positioning, GTM, or all of the above?
- Audience: Sales team (battle card), exec team (strategic), or product team (tactical)?
- Your product: What is your current positioning and key differentiators?
If the user provides a competitor name without context, ask: "What dimension matters most right now -- are you trying to win deals against them, decide what to build next, or understand their strategy?"
Step 2: Gather Intelligence
For each competitor, collect across these categories:
| Category | What to Capture |
| Product | Core features, recent launches, platform/integrations, UX approach |
| Positioning | Tagline, target persona, key messaging, value prop |
| Pricing | Model (per-seat, usage, flat), tiers, published pricing, free tier |
| GTM | Sales motion (PLG, sales-led, hybrid), channels, partnerships |
| Strengths | What they do better than you or the market |
| Weaknesses | Where they fall short, common complaints, gaps |
| Trajectory | Funding, hiring patterns, recent announcements, strategic direction |
Sources to check: product pages, pricing pages, changelog/release notes, G2/Capterra reviews, job postings, press releases, analyst reports.
Step 3: Build the Comparison
Feature Matrix
| Feature | Your Product | Competitor A | Competitor B |
| [Feature 1] | Full | Partial | None |
| [Feature 2] | Partial | Full | Full |
| [Feature 3] | None | Full | Partial |
Use: Full / Partial / Beta / None / Unknown. Add brief notes for nuance.
Positioning Map
Place competitors on two axes most relevant to the market:
Enterprise-grade
|
[Comp B] | [You]
|
Simple ----------------+---------------- Powerful
|
[Comp C] | [Comp A]
|
SMB-focusedChoose axes that reveal strategic gaps, not ones where everyone clusters.
Pricing Comparison
| Your Product | Competitor A | Competitor B | |
| Free tier | Yes/No | Yes/No | Yes/No |
| Entry price | $/mo | $/mo | $/mo |
| Mid-tier | $/mo | $/mo | $/mo |
| Enterprise | Custom | Custom | Custom |
| Model | Per-seat | Usage | Flat |
Step 4: Derive Insights
For each competitor, write:
### [Competitor Name]
**In one sentence**: [What they are and who they serve]
**Where they win**: [1-2 specific areas where they outperform you]
**Where they lose**: [1-2 specific areas where they fall short]
**Their bet**: [The strategic direction they are pursuing]
**Your response**: [What you should do about it -- match, differentiate, or ignore]Step 5: Compile the Brief
## Competitive Analysis: [Topic/Area]
Date: [Date] | Author: [Name]
### Executive Summary
[3-5 sentences: market landscape, your position, key takeaway]
### Competitor Profiles
[One section per competitor]
### Feature Comparison
[Matrix]
### Positioning Map
[2x2 or narrative]
### Pricing Landscape
[Comparison table]
### Strategic Implications
1. [Where to differentiate]
2. [Where to match / reach parity]
3. [Where to ignore]
### Recommendations
- [Action 1]: [Rationale]
- [Action 2]: [Rationale]
- [Action 3]: [Rationale]Output Variants
For sales teams (battle card):
- Lead with objection handling and win/loss talking points
- Include "When they say X, we say Y" scripts
- Keep to one page per competitor
For executives:
- Lead with strategic implications and market dynamics
- Include market share estimates and trajectory
- Focus on where to invest vs. divest
For product teams:
- Lead with feature gaps and parity requirements
- Include user experience comparisons
- Map to roadmap decisions
Examples
Example 1: Direct Competitor
User: "Create a competitive brief on Notion vs. our wiki product." Response: Compare along documentation, collaboration, integrations, pricing, and enterprise readiness. Highlight where Notion's flexibility is a strength (customization) and weakness (lack of structure for large teams).
Example 2: Feature Area
User: "How does our AI feature compare to competitors?" Response: Build a feature matrix of AI capabilities across 3-4 competitors. Note which are shipping AI as core vs. add-on, pricing implications, and user reception from review sites.
Example 3: Market Entry
User: "We're entering the analytics space. Who are we up against?" Response: Map the competitive landscape by segment (enterprise vs. SMB, technical vs. business user). Identify the most and least crowded positions. Recommend a positioning angle.
Best Practices
- Be specific, not generic. "Their search is faster" is useless. "Their search returns results in <200ms with typo tolerance; ours takes 1-2s without" is actionable.
- Separate fact from opinion. Label what is verified (pricing page, product demo) vs. inferred (strategy, roadmap).
- Update regularly. Competitive landscapes shift. Note the date of analysis and flag areas likely to change.
- Include your weaknesses. The brief loses credibility if it only highlights where you win. Honest assessment drives better strategy.
- Focus on what matters to customers. Competitors may have 50 features you lack, but only 3 matter to your buyers.
- Check G2 and Capterra reviews. Real user complaints reveal weaknesses that marketing hides.
- Watch their job postings. Hiring patterns reveal strategic direction 6-12 months before product launches.
- Talk to churned customers. Users who left you for a competitor (or vice versa) are the best source of competitive insight.
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.

