本文へ移動
cccskills
無料GitHub で公開

competitive-intel

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.

インストール方法を見る

含まれるファイル(4)

  • SKILL.md8.4 KB
  • LICENSE1.0 KB
  • references/ci-playbook.md9.7 KB
  • templates/battlecard-template.md3.5 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Attribution: Sourced from alirezarezvani/claude-skills by Alireza Rezvani.

Competitive Intelligence

Systematic competitor tracking. Not obsession — intelligence that drives real decisions.

Keywords

competitive intelligence, competitor analysis, battlecard, win/loss analysis, competitive positioning, competitive tracking, market intelligence, competitor research, SWOT, competitive map, feature gap analysis, competitive strategy

Quick Start

/ci:landscape         — Map your competitive space (direct, indirect, future)
/ci:battlecard [name] — Build a sales battlecard for a specific competitor
/ci:winloss           — Analyze recent wins and losses by reason
/ci:update [name]     — Track what a competitor did recently
/ci:map               — Build competitive positioning map

Framework: 5-Layer Intelligence System

Layer 1: Competitor Identification

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 ICPDifferent ICP
Same problemDirect threatAdjacent (watch)
Different problemDisplacement riskIgnore for now

Update this quarterly. Who's moved quadrants?

Layer 2: Tracking Dimensions

Track these 8 dimensions per competitor:

DimensionSourcesCadence
Product movesChangelog, G2/Capterra reviews, Twitter/LinkedInMonthly
Pricing changesPricing page, sales call intel, customer feedbackTriggered
FundingCrunchbase, TechCrunch, LinkedInTriggered
Hiring signalsLinkedIn job postings, IndeedMonthly
PartnershipsPress releases, co-marketingTriggered
Customer winsCase studies, review sites, LinkedInMonthly
Customer lossesWin/loss interviews, churned accountsOngoing
Messaging shiftsHomepage, ads (Facebook/Google Ad Library)Quarterly

Layer 3: Analysis Frameworks

SWOT per Competitor:

  • Strengths: What do they do well? Where do they win?
  • Weaknesses: Where do they lose? What do customers complain about?
  • Opportunities: What could they do that would threaten you?
  • Threats: What's their existential risk?

Competitive Positioning Map (2 axis): Choose axes that matter for your buyers:

  • Common: Price vs Feature Depth; Enterprise-ready vs SMB-ready; Easy to implement vs Configurable
  • Pick axes that show YOUR differentiation clearly

Feature Gap Analysis:

FeatureYouCompetitor ACompetitor BGap status
[Feature]✅✅❌Your advantage
[Feature]❌✅✅Gap — roadmap?
[Feature]✅❌❌Moat
[Feature]❌❌✅Competitor B only

Layer 4: Output Formats

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.

Layer 5: Intelligence Cadence

Monthly (scheduled):

  • Review all tier-1 competitors (direct threats, top 3)
  • Update battlecards with new intel
  • Publish 1-page summary to leadership

Triggered (event-based):

  • Competitor raises funding → assess implications within 48 hours
  • Competitor launches major feature → product + sales response within 1 week
  • Competitor poaches key customer → win/loss interview within 2 weeks
  • Competitor changes pricing → analyze and respond within 1 week

Quarterly:

  • Full competitive landscape review
  • Update positioning map
  • Refresh ICP competitive threat assessment
  • Add/remove companies from tracking list

Win/Loss Analysis

This is the highest-signal competitive data you have. Most companies do it too rarely.

When to interview:

  • Every lost deal >$50K ACV
  • Every churn >6 months tenure
  • Every competitive win (learn why — it may not be what you think)

Who conducts it:

  • NOT the AE who worked the deal (too close, prospect won't be candid)
  • Customer success, product team, or external researcher

Question structure:

  1. "Walk me through your evaluation process"
  2. "Who else were you considering?"
  3. "What were the top 3 criteria in your decision?"
  4. "Where did [our product] fall short?"
  5. "What was the deciding factor?"
  6. "What would have changed your decision?"

Aggregate findings monthly:

  • Win reasons (rank by frequency)
  • Loss reasons (rank by frequency)
  • Competitor win rates (by competitor, by segment)
  • Patterns over time

The Balance: Intelligence Without Obsession

Signs you're over-tracking competitors:

  • Roadmap decisions are primarily driven by "they just shipped X"
  • Team morale drops when competitors fundraise
  • You're shipping features you don't believe in to match their checklist
  • Pricing discussions always start with "well, they charge X"

Signs you're under-tracking:

  • Your AEs get blindsided on calls
  • Prospects know more about competitors than your team does
  • You missed a major product launch until customers told you
  • Your positioning hasn't changed in 12+ months despite market moves

The right posture:

  • Know competitors well enough to win against them
  • Don't let them set your agenda
  • Your roadmap is led by customer problems, informed by competitive gaps

Distributing Intelligence

AudienceFormatCadenceOwner
AEs + SDRsUpdated battlecards in CRMMonthly + triggeredCRO
ProductFeature gap analysisQuarterlyCPO
MarketingPositioning briefQuarterlyCMO
Leadership1-page competitive summaryMonthlyCEO/COO
BoardCompetitive landscape slideQuarterlyCEO

One source of truth: All competitive intel lives in one place (Notion, Confluence, Salesforce). Avoid Slack-only distribution — it disappears.


Red Flags in Competitive Intelligence

SignalWhat it means
Competitor's win rate >50% in your core segmentFundamental 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 domainMajor product investment incoming
Competitor raised >$20M and targets your ICP12-month runway for them to compete hard
Prospects evaluate you to justify competitor decisionYou're the "check box" — fix perception or segment

Integration with C-Suite Roles

Intelligence TypeFeeds ToOutput Format
Product movesCPORoadmap input, feature gap analysis
Pricing changesCRO, CFOPricing response recommendations
Funding roundsCEO, CFOStrategic positioning update
Hiring signalsCHRO, CTOTalent market intelligence
Customer wins/lossesCRO, CMOBattlecard updates, positioning shifts
Marketing campaignsCMOCounter-positioning, channel intelligence

References

  • references/ci-playbook.md — OSINT sources, win/loss framework, positioning map construction
  • templates/battlecard-template.md — sales battlecard template

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Use when long-lived agents, project memories, system prompts, or playbooks are repeatedly summarized, rewritten, or optimized and risk losing domain detail, provenance, or execution learnings.

日本語の概要は準備中です。原文の説明を表示しています。

mouadja02/skills102026年10月16日 更新

Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.

日本語の概要は準備中です。原文の説明を表示しています。

mouadja02/skills102026年10月16日 更新

Adds educational comments to a code file so it becomes a learning resource, asking for the file (with a list of close matches) if none is given. Use when preparing code for learners, onboarding, or teaching.

日本語の概要は準備中です。原文の説明を表示しています。

mouadja02/skills102026年10月16日 更新

Write, debug, and optimize Adobe Illustrator automation scripts using ExtendScript (JavaScript/JSX). Use when creating or modifying scripts that manipulate documents, layers, paths, text frames, colors, symbols, artboards, or any Illustrator DOM objects. Covers the complete JavaScript object model, coordinate system, measurement units, export workflows, and scripting best practices.

日本語の概要は準備中です。原文の説明を表示しています。

mouadja02/skills102026年10月16日 更新

Patterns and techniques for adding governance, safety, and trust controls to AI agent systems. Use this skill when: - Building AI agents that call external tools (APIs, databases, file systems) - Implementing policy-based access controls for agent tool usage - Adding semantic intent classification to detect dangerous prompts - Creating trust scoring systems for multi-agent workflows - Building audit trails for agent actions and decisions - Enforcing rate limits, content filters, or tool restrictions on agents - Working with any agent framework (PydanticAI, CrewAI, OpenAI Agents, LangChain, AutoGen)

日本語の概要は準備中です。原文の説明を表示しています。

mouadja02/skills102026年10月16日 更新

Check any AI agent codebase against the OWASP Agentic Security Initiative (ASI) Top 10 risks. Use this skill when: - Evaluating an agent system's security posture before production deployment - Running a compliance check against OWASP ASI 2026 standards - Mapping existing security controls to the 10 agentic risks - Generating a compliance report for security review or audit - Comparing agent framework security features against the standard - Any request like "is my agent OWASP compliant?", "check ASI compliance", or "agentic security audit"

日本語の概要は準備中です。原文の説明を表示しています。

mouadja02/skills102026年10月16日 更新

mouadja02 のスキルをすべて見る

このスキルの問題を報告する