competitive-intel
Skill0 starsChanged 7 months agoApache-2.0View on GitHub
Apply honest competitive analysis methodology. Map content battlefields against configured competitors, identify real gaps (not wishful ones), and find defensible white space. If a competitor is strong, say so. White space that doesn't exist isn't an opportunity. Used by /competitor command.
19 other projects use a version of this.
Adopted by
Most recently taken up by
- darkweb19/skillstheir own version, first seen Nov 8, 2026
- memi-design/design-skillstheir own version, first seen Nov 8, 2026
- MoizIbnYousaf/marketing-clitheir own version, first seen Nov 1, 2026
- Hyde-and-Larkin/product-marketing-toolkittheir own version, first seen Nov 1, 2026
- hassanzouhar/market_analyticstheir own version, first seen Sep 24, 2026
- CyranoB/web-foragertheir own version, first seen Sep 17, 2026
Used with
Projects with it also use pricing-strategy.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
silvainfmSkillpricing-strategy
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' or 'monetization.' This skill covers pricing research, tier structure, and packaging strategy.
Also in 3 projects that use this
Other versions19 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 19
- Natan-Mohart/24-strategy-skills-for-claude★ 41same name
- MoizIbnYousaf/marketing-cli★ 33same name
- GTMify/aigtm★ 25same name
- Hassaan146/claude-skills★ 18same name
- XPOZpublic/xpoz-agent-skills★ 15same name
- CyranoB/web-forager★ 10same name
- memi-design/design-skills★ 7same name
- Aditya923-c/xpoz-agent-skills★ 6same name
- RizwanZafaris/product-manager-OS★ 4same name
- saberapp/skills★ 4same name
9 more not listed
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 repository4 other files it gives its agents.
- calendar-plannerSkill
- client-contextSkill
- content-strategistSkill
- editorial-configSkill
The file
We split this skill into the rules it gives an agent
12 rules. 0 are common, 12 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
12
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 21
If any one of these three is false — it's not a real opportunity.
- Distinctive: line 27
When analyzing competitors, draw from these sources in order of reliability:
- Distinctive: line 58
Always check document freshness before trusting competitive intelligence:
- Distinctive: line 78
Start with configured content pillars — these are the themes the client has staked out or wants to own.
- Distinctive: line 129
Every brand tells a story.
- Distinctive: line 146
Every candidate white space must pass all three tests.
- Distinctive: line 170
If yes — the angle is not differentiated.
- Distinctive: line 194
Every competitive recommendation needs a risk read.
- Distinctive: line 215
Use competitor strengths as documented — not softened, not reframed
- Distinctive: line 217
Run the substitution test on every recommended angle
- Distinctive: line 221
Use the three-test validation for every white space candidate
- Distinctive: line 226
Call a competitor strength a weakness
“Common” is measured: kept by at least 6 in 10 of the 15 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 Intel
Honest competitive analysis. If a competitor is strong, say so. White space that doesn't exist isn't an opportunity. The goal is actionable intelligence, not a pep talk.
The Honesty Requirement
This is the foundational rule. Everything else flows from it.
Apply competitor strengths literally. These are genuine strengths — things the competitor actually does well for the audience you're competing for. Do not reframe them as weaknesses. Do not minimize them. Do not suggest you can easily overcome them without a specific, credible plan.
A gap is only an opportunity if all three of these are true:
- The competitor genuinely isn't serving it (confirmed by documented weaknesses or direct assessment)
- The audience actually wants it (confirmed by segment content preferences from client context)
- The client can execute on it (confirmed by team constraints and publishing cadence)
If any one of these three is false — it's not a real opportunity. Cut it.
Competitive Research Methodology
Research Sources
When analyzing competitors, draw from these sources in order of reliability:
Direct Sources (Highest Reliability)
| Source | What to Extract | Reliability |
| Competitor website (homepage, product, about, pricing) | Positioning, messaging, value proposition, target audience | High |
| Competitor blog / resource center | Content themes, publishing frequency, depth, quality | High |
| Competitor newsletter (if accessible) | Email strategy, voice, cadence, engagement tactics | High |
| Competitor social profiles | Content strategy, engagement levels, audience interaction style | High |
| Competitor job postings | Strategic priorities (hiring for new market = expansion signal) | Medium-High |
Client-Provided Sources (Medium-High Reliability)
| Source | What to Extract | Reliability |
| Competitive analysis documents in ~~docs | Pre-analyzed strengths, weaknesses, positioning | Medium-High (may be outdated) |
| Battlecards in ~~docs | Sales-facing competitive intelligence | Medium-High (check freshness) |
| Win/loss notes in ~~docs or ~~crm | Why deals were won or lost against this competitor | High (direct market signal) |
Third-Party Sources (Medium Reliability)
| Source | What to Extract | Reliability |
| Review sites (G2, Capterra, TrustRadius) | Customer sentiment, common praise and complaints | Medium (selection bias) |
| SEO tools (~~SEO if connected) | Keyword rankings, organic traffic, content gaps | Medium-High (data quality varies) |
| Social listening | Share of voice, sentiment, trending topics | Medium |
| Industry analyst reports | Market positioning, category placement | Medium (may not reflect current state) |
Competitive Staleness Check
Always check document freshness before trusting competitive intelligence:
| Age | Status | Action |
| < 30 days | Current | Use as-is |
| 30-90 days | Usable | Use with light verification |
| 90-180 days | Stale | Flag prominently, recommend refresh |
| > 180 days | Outdated | Use for structural context only (who competitors are), not for current assessment |
Flag format:
⚠️ Competitive data for [{competitor}] is [{N}] days old. Positioning and content strategy may have changed.Battlefield Framework
A battlefield is a content topic or format where audience attention is contested. Think of it as a territory that one brand can own — or that multiple brands are fighting over.
Identifying Battlefields
Start with configured content pillars — these are the themes the client has staked out or wants to own. Each pillar is a battlefield. Then identify additional battlefields:
- Topics competitors are investing in that aren't in the client's pillar list
- Emerging topics in the industry that no one owns yet
- Adjacent topics where audience overlap creates competition
Four-Position Framework
For each battlefield, assess each player's position:
| Position | Definition | Signals |
| Dominating | Clear leader — audience goes here first | Ranks #1-3 for key terms, highest content volume and quality, most backlinks, community recognition |
| Competing | Real presence but not the go-to | Ranks on page 1, consistent publishing, some engagement, recognized but not first choice |
| Thin | Occasional coverage, no real position | A few pieces scattered across the topic, no sustained effort, low engagement |
| Absent | Not present at all | No content on this topic |
Battlefield Assessment Table
| Battlefield | You | Competitor A | Competitor B | Competitor C |
| [{Pillar 1}] | [{Position}] | [{Position}] | [{Position}] | [{Position}] |
| [{Pillar 2}] | [{Position}] | [{Position}] | [{Position}] | [{Position}] |
| [{Additional}] | [{Position}] | [{Position}] | [{Position}] | [{Position}] |
Reading the Battlefield
| Pattern | Implication | Action |
| You're Dominating, competitors are Thin/Absent | Defend — maintain quality and cadence | Don't over-invest; protect the lead |
| You're Competing, one competitor Dominates | Challenge — find a differentiated angle | Substitution test required (see below) |
| You're Thin, competitors are Competing | Build or abandon — honest assessment of winnability | Run winnability test from content-strategist |
| Nobody is Dominating | Open battlefield — first-mover advantage possible | Assess audience demand before investing |
| Multiple competitors Dominating | Saturated — differentiation is essential | Only enter with a genuinely unique angle |
Messaging and Positioning Comparison
Messaging Matrix
For each competitor, document their positioning:
| Dimension | Your Brand | Competitor A | Competitor B |
| Core promise | What you promise the audience | What they promise | What they promise |
| Target audience | Who you serve | Who they serve | Who they serve |
| Key differentiator | What you claim only you can do | Their claim | Their claim |
| Tone/Voice | Your voice attributes | Their voice attributes | Their voice attributes |
| Proof points | How you back up claims | How they back up claims | How they back up claims |
| Category framing | How you define the category | How they define it | How they define it |
Narrative Analysis
Every brand tells a story. Identify each competitor's narrative structure:
| Narrative Element | What to Identify |
| Villain | What problem or enemy they position against (status quo, legacy tools, complexity, ignorance) |
| Hero | Who is the hero — the customer? the product? the founder? |
| Transformation | What before/after do they promise? |
| Stakes | What happens if the audience doesn't act? |
This reveals positioning strategy and emotional appeals — useful for finding angles they've left open.
White Space Identification
White space = a battlefield where the client can win and the audience is underserved.
Three-Test White Space Validation
Every candidate white space must pass all three tests. Failing any single test disqualifies it.
| Test | Question | Pass Criteria | Fail Signal |
| Audience demand | Does the target audience actually want this? | Evidence: search volume, community questions, engagement on adjacent content, segment preferences | No evidence of demand, or demand is from a different segment than the client serves |
| Competitive opening | Is this uncontested or weakly contested? | No competitor Dominates this battlefield | A competitor already Dominates with high-quality, comprehensive content |
| Execution reality | Can this client actually build and sustain a position here? | Team has expertise, capacity fits cadence, source material exists | Outside domain expertise, would exceed capacity, no sustainable advantage |
White Space Categories
| Category | Definition | Investment Level | Risk |
| True white space | Uncontested AND audience-relevant AND executable | High — this is rare and worth significant investment | Low — but verify demand before going all-in |
| Contested gap | Competitors are Thin but present — winnable with sustained effort | Medium — requires 90-day commitment, not a quick win | Medium — competitors may respond |
| Temporary gap | Competitor is temporarily absent (seasonal, pivoting, leadership change) | Low — exploit but don't build strategy on it | High — the gap may close |
Differentiation Testing
The Substitution Test
For every recommended content angle, run this test:
"Could [{competitor}] publish this verbatim under their own brand?"
If yes — the angle is not differentiated. Find what only this client can own.
Sources of Differentiation
| Source | How It Creates Moat | Example |
| Proprietary data | Only this brand has this data | Performance benchmarks from your own platform |
| Domain expertise | Deep, specific knowledge competitors can't replicate quickly | 20 years of editorial operations experience |
| Unique perspective | Point of view that competitors won't adopt | Contrarian takes on industry orthodoxy |
| Audience access | Direct relationship with a specific audience segment | Community-sourced insights, subscriber survey data |
| Geographic specificity | Local knowledge competitors can't match | Destination expertise from living in the region |
| Process transparency | Willingness to show how the sausage is made | Behind-the-scenes of your editorial process |
Differentiation Quality Assessment
| Level | Description | Defensibility |
| Structural | Built into the business model — competitors can't copy without changing their business | Very high (years to replicate) |
| Experiential | Built on accumulated experience — competitors can't shortcut the learning | High (months to years) |
| Perspectival | Built on a point of view — competitors could adopt it but probably won't | Medium (can be copied if competitor is willing) |
| Executional | Built on doing it better — competitors could match with effort | Low (weeks to months) |
Risk Assessment
Every competitive recommendation needs a risk read. Don't present opportunities without acknowledging what could go wrong.
Risk Dimensions
| Dimension | Question | What to Assess |
| Counter-move | If the client executes well, how does the competitor respond? | Speed of response, resources available, strategic priority for them |
| Sustainable moat | What makes this position hard to copy? | Time, expertise, data, audience trust, structural advantage |
| Vulnerability | Where is the client exposed if a competitor scales up? | Resource gaps, dependency on a single angle, thin coverage |
| Escalation risk | Could this provoke a competitive response the client can't match? | Budget disparity, team size disparity, distribution advantage |
Risk Rating
| Rating | Definition | Action |
| Low | Competitors are unlikely to respond, or client has structural advantage | Proceed with confidence |
| Medium | Competitors may respond, but client has time and differentiation to build position | Proceed with speed — first-mover advantage matters |
| High | Competitors can and likely will respond with superior resources | Only proceed if differentiation is Structural or Experiential |
Always Do
- Use competitor strengths as documented — not softened, not reframed
- Flag stale competitive data before the analysis
- Run the substitution test on every recommended angle
- Show the battlefield assessment with honest position assessments
- Name the sustainable moat specifically — "domain expertise" alone is not a moat unless you explain what domain and why it's hard to replicate
- Include risk assessment for every strategic recommendation
- Use the three-test validation for every white space candidate
Never Do
- Invent competitors not found in client documents or direct user input
- Call a competitor strength a weakness
- Recommend white space that fails any of the three validation tests
- Skip the risk assessment
- Suggest the client can win where a competitor genuinely dominates without a specific, credible differentiation plan
- Present competitive analysis without checking data freshness
- Recommend competitive moves the team can't sustain at their current capacity
- Ignore the audience demand test — a gap no one cares about isn't an opportunity
Cross-Skill Dependencies
- Receives from: editorial-config (competitor list with strengths/weaknesses, pillars, segments, constraints)
- Receives from: content-strategist (strategic context, goal alignment, history check)
- Used by: /competitor command
- Informs: /audit (competitive dimension of pillar health assessment)
- Informs: /calendar (competitive urgency signals for recommendation sequencing)
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.

