c-level-advisor/skills/competitive-intel/SKILL.md
Systematic competitor tracking that feeds CMO positioning, CRO battlecards, and CPO roadmap decisions. Use when analyzing competitors, building sales battlecards, tracking market moves, positioning against alternatives, or when user mentions competitive intelligence, competitive analysis, competitor research, battlecards, win/loss, or market positioning.
npx skillsauth add alirezarezvani/claude-skills competitive-intelInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Systematic competitor tracking. Not obsession — intelligence that drives real decisions.
competitive intelligence, competitor analysis, battlecard, win/loss analysis, competitive positioning, competitive tracking, market intelligence, competitor research, SWOT, competitive map, feature gap analysis, competitive strategy
Ask in natural language for the deliverable you need:
"Map our competitive landscape" — direct, indirect, and future competitors "Build a battlecard for [competitor]" — sales-ready battlecard "Run a win/loss analysis" — recent wins and losses by reason "What did [competitor] do recently?" — competitor update tracking "Build a competitive positioning map" — 2x2 positioning map
Direct competitors: Same ICP, same problem, comparable solution, similar price point. Indirect competitors: Same budget, different solution (including "do nothing" and "build in-house"). Future competitors: Well-funded startups in adjacent space; large incumbents with stated roadmap overlap.
The 2x2 Threat Matrix:
| | Same ICP | Different ICP | |---|---|---| | Same problem | Direct threat | Adjacent (watch) | | Different problem | Displacement risk | Ignore for now |
Update this quarterly. Who's moved quadrants?
Track these 8 dimensions per competitor:
| Dimension | Sources | Cadence | |-----------|---------|---------| | Product moves | Changelog, G2/Capterra reviews, Twitter/LinkedIn | Monthly | | Pricing changes | Pricing page, sales call intel, customer feedback | Triggered | | Funding | Crunchbase, TechCrunch, LinkedIn | Triggered | | Hiring signals | LinkedIn job postings, Indeed | Monthly | | Partnerships | Press releases, co-marketing | Triggered | | Customer wins | Case studies, review sites, LinkedIn | Monthly | | Customer losses | Win/loss interviews, churned accounts | Ongoing | | Messaging shifts | Homepage, ads (Facebook/Google Ad Library) | Quarterly |
SWOT per Competitor:
Competitive Positioning Map (2 axis): Choose axes that matter for your buyers:
Feature Gap Analysis: | Feature | You | Competitor A | Competitor B | Gap status | |---------|-----|-------------|-------------|------------| | [Feature] | ✅ | ✅ | ❌ | Your advantage | | [Feature] | ❌ | ✅ | ✅ | Gap — roadmap? | | [Feature] | ✅ | ❌ | ❌ | Moat | | [Feature] | ❌ | ❌ | ✅ | Competitor B only |
For Sales (CRO): Battlecards — one page per competitor, designed for pre-call prep.
See templates/battlecard-template.md
For Marketing (CMO): Positioning update — message shifts, new differentiators, claims to stop or start making.
For Product (CPO): Feature gap summary — what customers ask for that we don't have, what competitors ship, what to reprioritize.
For CEO/Board: Monthly competitive summary — 1-page: who moved, what it means, recommended responses.
Monthly (scheduled):
Triggered (event-based):
Quarterly:
This is the highest-signal competitive data you have. Most companies do it too rarely.
When to interview:
Who conducts it:
Question structure:
Aggregate findings monthly:
Signs you're over-tracking competitors:
Signs you're under-tracking:
The right posture:
| Audience | Format | Cadence | Owner | |----------|--------|---------|-------| | AEs + SDRs | Updated battlecards in CRM | Monthly + triggered | CRO | | Product | Feature gap analysis | Quarterly | CPO | | Marketing | Positioning brief | Quarterly | CMO | | Leadership | 1-page competitive summary | Monthly | CEO/COO | | Board | Competitive landscape slide | Quarterly | CEO |
One source of truth: All competitive intel lives in one place (Notion, Confluence, Salesforce). Avoid Slack-only distribution — it disappears.
| Signal | What it means | |--------|---------------| | Competitor's win rate >50% in your core segment | Fundamental positioning problem, not sales problem | | Same objection from 5+ deals: "competitor has X" | Feature gap that's real, not just optics | | Competitor hired 10 engineers in your domain | Major product investment incoming | | Competitor raised >$20M and targets your ICP | 12-month runway for them to compete hard | | Prospects evaluate you to justify competitor decision | You're the "check box" — fix perception or segment |
| Intelligence Type | Feeds To | Output Format | |------------------|----------|---------------| | Product moves | CPO | Roadmap input, feature gap analysis | | Pricing changes | CRO, CFO | Pricing response recommendations | | Funding rounds | CEO, CFO | Strategic positioning update | | Hiring signals | CHRO, CTO | Talent market intelligence | | Customer wins/losses | CRO, CMO | Battlecard updates, positioning shifts | | Marketing campaigns | CMO | Counter-positioning, channel intelligence |
references/ci-playbook.md — OSINT sources, win/loss framework, positioning map constructiontemplates/battlecard-template.md — sales battlecard templatedevelopment
Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says "/cs:weekly-review". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.
development
Use when someone wants to decide whether a meeting is worth calling, price a meeting in dollars, build a timeboxed agenda with desired outcomes, or turn messy meeting notes into owned action items — or says "should this be a meeting", "/cs:meeting-prep", or "/cs:meeting-actions". Runs a cost gate (ASYNC / NOT-READY / MEET), builds a decision-first agenda, and extracts an owner + due-date checklist that flags every orphan.
development
Convert a rambling description of a desired outcome into one polished, autonomous /goal prompt ready to paste into a fresh session. Use when the user says "/fable-goal", "turn this into a goal prompt", "write me a fable prompt", "write the prompt that builds X", or rambles about something they want made and asks for the prompt that makes it happen. The output is a single copy-paste prompt, never the build itself. Do NOT use when the user wants the thing built right now in this session — only when they want the PROMPT that will make it happen in a fresh session.
development
Use when someone wants to plan a deep work day, time-block their calendar or task list, budget or cut shallow work, protect focus hours, track deep-work sessions and streaks, run an end-of-day shutdown ritual, or says "/deep-work" or "/time-block". Classifies tasks deep vs shallow, builds an energy-first time-blocked schedule that refuses deep demand past the 4-hour ceiling, batches shallow work into at most two windows, and logs focus sessions against a weekly target.