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

competitive-strategist

Expert competitive intelligence and strategy guidance for B2B/SaaS companies. Use when conducting competitive research, creating battlecards, analyzing win/loss data, building market landscape maps, positioning against alternatives, handling competitive objections, writing comparison pages, or developing sales enablement for competitive situations. Use for competitive monitoring, feature comparisons, and market intelligence gathering.

インストール方法を見る

含まれるファイル(12)

  • SKILL.md6.7 KB
  • rules/_sections.md1.6 KB
  • rules/analysis-win-loss.md7.1 KB
  • rules/battlecard-creation.md6.4 KB
  • rules/comparison-feature-strategy.md6.9 KB
  • rules/enablement-sales-training.md8.1 KB
  • rules/landscape-mapping.md6.5 KB
  • rules/messaging-competitive-claims.md7.5 KB
  • rules/messaging-objection-handling.md7.3 KB
  • rules/monitoring-systems.md8.2 KB
  • rules/positioning-differentiation.md5.5 KB
  • rules/research-methodologies.md5.2 KB

SKILL.md(原文)

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

Competitive Strategist

Expert competitive intelligence and positioning guidance for winning in crowded markets — from research methodologies to sales enablement and everything in between.

Philosophy

Competitive strategy isn't about copying competitors or tearing them down:

  1. Know yourself first — You can't position against others until you know your own strengths
  2. Focus on customers, not competitors — What they need matters more than what rivals do
  3. Be honest — Lies and FUD destroy credibility faster than any competitor
  4. Stay current — Markets move fast; stale intel costs deals

How This Skill Works

When invoked, apply the guidelines in rules/ organized by:

  • research-* — Competitive research methodologies and intelligence gathering
  • analysis-* — Win/loss analysis and market landscape mapping
  • battlecard-* — Battlecard creation, structure, and maintenance
  • positioning-* — Positioning against alternatives and differentiation
  • messaging-* — Competitive messaging and objection handling
  • enablement-* — Sales enablement for competitive situations
  • monitoring-* — Competitive monitoring systems and alerts

Core Frameworks

The Competitive Intelligence Cycle

┌─────────────────────────────────────────────────────────────┐
│                                                             │
│   ┌──────────┐    ┌──────────┐    ┌──────────┐             │
│   │  GATHER  │───▶│ ANALYZE  │───▶│  SHARE   │             │
│   │  (Intel) │    │ (Insight)│    │ (Enable) │             │
│   └──────────┘    └──────────┘    └──────────┘             │
│        ▲                                │                   │
│        │          ┌──────────┐          │                   │
│        └──────────│  UPDATE  │◀─────────┘                   │
│                   │ (Iterate)│                              │
│                   └──────────┘                              │
│                                                             │
└─────────────────────────────────────────────────────────────┘

Competitive Positioning Matrix

Positioning TypeWhen to UseKey Approach
Head-to-headYou're stronger on key dimensionsDirect comparison
Niche downCompetitor owns general categoryOwn a specific segment
ReframeCompetitor's strength is irrelevantChange the criteria
LeapfrogNew capability they can't matchFuture-oriented vision
CoexistDifferent jobs to be doneComplement, don't compete

Competitor Tiers

TierDescriptionMonitoring FrequencyDepth of Analysis
PrimaryDirect competitors, same ICPWeeklyDeep battlecards
SecondaryAdjacent solutions, partial overlapMonthlyOverview cards
EmergingStartups, potential disruptorsQuarterlyWatch list
AlternativesStatus quo, DIY, spreadsheetsOngoingPain point mapping

Win/Loss Analysis Framework

Deal Outcome
    │
    ├── Won Against Competitor
    │   ├── What differentiated us?
    │   ├── What did they say about competitor?
    │   └── What would have changed their mind?
    │
    └── Lost to Competitor
        ├── What was the deciding factor?
        ├── Where did we fall short?
        └── What could we have done differently?

The Battlecard Structure

SectionPurposeUpdate Frequency
OverviewQuick context, what they doQuarterly
PositioningHow we win, key differentiatorsMonthly
LandminesQuestions to ask that expose weaknessesAs discovered
Objection HandlingResponses to "Why not [competitor]?"As encountered
Proof PointsCustomer quotes, case studiesAs available
Pricing IntelKnown pricing, packagingAs discovered

Competitive Response Spectrum

SituationResponseExample
They launch feature you haveEmphasize experience, depth"We've had this for 2 years, here's what we've learned"
They launch feature you don'tRoadmap or reframe"We're focused on X because customers told us Y matters more"
They cut priceHold on value"You get what you pay for — here's the TCO comparison"
They spread FUDCorrect with facts"That's not accurate — here's the truth with proof"
They announce fundingIgnore or pivot to stability"We've been profitable since 2019"

Intelligence Sources (Ranked by Value)

  1. Win/loss interviews — First-party, high signal
  2. Sales call recordings — Real objections, real context
  3. Customer feedback — Why they chose you (and considered others)
  4. G2/Capterra reviews — Volume of sentiment data
  5. LinkedIn activity — Hiring, messaging, customer posts
  6. Job postings — Strategic direction signals
  7. Press/funding news — Major moves, positioning shifts
  8. Product trials — Hands-on intel (respect ToS)

Anti-Patterns

  • FUD tactics — Spreading fear, uncertainty, doubt backfires
  • Obsessing over competitors — Customer needs > competitor moves
  • Stale battlecards — Outdated intel loses deals
  • One-size-fits-all — Different competitors need different strategies
  • Ignoring the real competitor — Often it's "do nothing" or spreadsheets
  • Attacking instead of differentiating — Negative selling repels buyers
  • Hoarding intel — Unshared intelligence is worthless
  • Copying competitors — You become undifferentiated

レビュー

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

同じリポジトリのスキル

概要と使いどころ

Expert full-cycle enterprise sales strategist for B2B SaaS. Use when planning sales strategy, pipeline management, deal progression, account planning, competitive displacement, or territory optimization. Covers multi-threading, executive engagement, champion development, buying committee navigation, and complex deal orchestration. Use for enterprise selling, account expansion, land-and-expand, and quota attainment.

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

ncklrs/startup-os-skills522026年2月27日 更新

adr

無料

Expert Architecture Decision Record (ADR) creation and lifecycle management based on Olaf Zimmermann's methodology. Use when creating ADRs, reviewing architectural decisions, evaluating decision readiness, writing MADR templates, assessing decision quality, or managing ADR logs. Covers the full lifecycle from readiness (START criteria) through creation, MADR formatting, completion (ECADR criteria), and ongoing maintenance.

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

ncklrs/startup-os-skills522026年2月27日 更新

Hand off code review to OpenAI Codex CLI. Use when asked to "review code with codex", "codex review", "get a second opinion on code", "review my changes", "review this PR", or when you want AI-powered code review from a different model perspective.

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

ncklrs/startup-os-skills522026年2月27日 更新

Expert community-led growth and community management guidance. Use when building developer communities, Discord/Slack communities, online communities, managing community platforms, designing member onboarding, creating engagement programs, running ambassador programs, measuring community health, setting up moderation systems, or implementing DevRel strategies. Use for community-led growth, member activation, user-generated content programs, and community governance.

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

ncklrs/startup-os-skills522026年2月27日 更新

Master orchestrator that chains all Remotion video creation skills together in a single automated pipeline. Takes a creative brief and produces a complete, production-ready Remotion video project. Use when starting a new video from scratch, when asked to "create a video", "make a video", "build a complete video", or "video from idea to code".

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

ncklrs/startup-os-skills522026年2月27日 更新

Strategic Customer Success leadership guidance for CS org design, customer segmentation and tiering (tech touch, low touch, high touch), success metrics and KPIs (NRR, GRR, NPS, CSAT, CES), playbook development, executive stakeholder management, CS technology stack strategy, value realization frameworks, and customer journey mapping. Use when building CS teams, defining customer segments, designing playbooks, measuring success outcomes, or implementing CS platforms.

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

ncklrs/startup-os-skills522026年2月27日 更新

ncklrs のスキルをすべて見る

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