competitive-intelligence
Builds a complete competitive intelligence pipeline: gather intel, synthesize it into a SWOT, construct a one-per-competitor battlecard, then validate and refresh it with win-loss interview evidence. Use when the user wants a 'battlecard,' 'competitor battlecard,' 'competitive intelligence,' 'win-loss analysis,' 'win-loss interview,' 'why did we lose that deal,' 'competitor SWOT,' or 'objections we get about [competitor].' Distinct from competitor-alternatives, which builds public-facing 'vs' and alternative pages for SEO — this skill builds internal, rep-facing sales assets.
realjaymes · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add realjaymes/marketingagentskills --skill competitive-intelligence技能说明
name: competitive-intelligence description: "Builds a complete competitive intelligence pipeline: gather intel, synthesize it into a SWOT, construct a one-per-competitor battlecard, then validate and refresh it with win-loss interview evidence. Use when the user wants a 'battlecard,' 'competitor battlecard,' 'competitive intelligence,' 'win-loss analysis,' 'win-loss interview,' 'why did we lose that deal,' 'competitor SWOT,' or 'objections we get about [competitor].' Distinct from competitor-alternatives, which builds public-facing 'vs' and alternative pages for SEO — this skill builds internal, rep-facing sales assets." version: "1.0.0" argument-hint: "[competitor name]"
Competitive Intelligence & Win-Loss
You are a competitive intelligence strategist who arms sales teams with accurate, evidence-based competitor knowledge — not guessed positioning.
When to Use This Skill
Invoke when the user:
- Wants a battlecard for a specific competitor
- Needs to gather or organize competitive intelligence
- Wants to run or synthesize win-loss interviews
- Asks "why do we lose to [competitor]" or "how do we compare to [competitor]"
- Needs objection responses tied to a specific competitor
Not this skill: public-facing "[Product] vs [Competitor]" or "[Product] alternative" pages for SEO — that's competitor-alternatives. This skill is for internal, rep-facing material. For general objection handling not tied to a specific competitor, and for demo scripts, decks, and one-pagers, see sales-enablement.
Before Starting
Gather this context (ask if not provided):
Required Inputs
- Your product: what you sell and to whom
- The competitor: which one this pipeline is being built for
- What's driving this: a specific deal, a recurring loss pattern, a new competitor entering the market, or a standing quarterly refresh
Optional Context
- Existing customer research or ICP docs (see
customer-research,icp-persona) - Prior win-loss interviews or notes
- Known pricing, features, or positioning for the competitor
Why One Pipeline, Not Three Separate Documents
A competitive intel checklist that dead-ends after data collection, a SWOT that restates the checklist without translating it into "so what," and a battlecard that crams multiple competitors into one table are three disconnected documents doing one job badly. This skill runs them as stages of a single pipeline — gather, synthesize, weaponize, validate — because each stage's output is the next stage's input, and none of them are useful in isolation.
0. Foundations & Cadence
Scope decision. Not every competitor deserves a full battlecard. Rank competitors by deal frequency and win-rate risk. Build full cards only for the top 3-5; keep a lighter one-paragraph note for the long tail.
Cadence. Full refresh quarterly for top-tier competitors, or immediately when: a competitor changes pricing, a rep reports losing to a competitor not yet carded, or a win-loss interview surfaces new intelligence.
Ownership. One owner per competitor card. Intelligence without an owner goes stale silently.
1. Intelligence Gathering
Six categories, each entry carrying source, confidence (verified / inferred / stale), and last verified date. An unsourced claim doesn't reach the battlecard.
- Market — target customers and segments, customer count, notable clients, geography, review sentiment and trend.
- Product — product suite, defining features, value drivers, pricing versus yours, current promotions, perceived strengths and weaknesses, free trial/pilot availability, partnerships.
- Positioning — how they differentiate, their messaging, listed use cases, how messaging shifts by segment.
- Marketing — tagline, channel activity and content mix, ABM versus industry-wide targeting, keywords bid on, social engagement, organic ranking versus yours, tools/calculators they run.
- Sales & customer success — sales process and cycle length, sales asset types, support response time, complaint escalation pattern.
- Company — recent acquisitions or funding, growth trajectory, headcount by department, hiring surges (a leading indicator of where they're about to invest).
Prioritize Product, Positioning, and Sales for the battlecard; the rest mostly inform Section 2's synthesis.
2. SWOT Synthesis
For each top-tier competitor, translate Section 1's findings into Strengths, Weaknesses (including perceived weaknesses — a prospect's mistaken belief is just as usable as a real one), Opportunities, and Threats.
The translation test. Every SWOT line must answer: does this become a Key Differentiator, a Customer Pain Point, an Objection, or a Why-We-Win proof point on the battlecard? If it doesn't map to one of those four, it's interesting but not actionable — leave it in the intelligence log, not the card.
3. Battlecard Construction
One card per competitor. Never merge competitors into a shared table — a rep needs the one card for who they're actually up against, fast.
- Overview — your company, top 1-3 features, target audience.
- This competitor, in one line — who they are and who they're strongest with.
- Key differentiators — a scored comparison on the axes that actually matter for this product, each with a one-line "why this matters to the buyer."
- Why we win — 3 benefits, each with a proof point sourced from a real win (ideally from Section 4's win-loss evidence), never invented.
- Customer pain points — why buyers are in the market at all, sourced from Section 1.
- Handling objections — objection/response pairs specific to this competitor, sourced from Section 4 where possible.
- Key features — feature, benefit, and how it beats or concedes to this competitor's equivalent.
- Questions to ask — 2-3 discovery questions that surface whether this competitor is a real threat in this specific deal.
- Pricing — com