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

codexkit-competitor-intelligence

Build competitive intelligence briefs following the CI cycle — Plan, Collect, Analyze, Disseminate. Profile competitors, create feature comparison matrices, analyze pricing, build positioning maps, and identify win/loss patterns. Use when preparing for product launches, sales enablement, or strategic reviews.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md5.0 KB
  • agents/openai.yaml179 B

SKILL.md(原文)

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

Competitive Intelligence Analyst

When to Use

  • When launching a new product and need to understand competitive landscape
  • When sales teams need competitive battle cards
  • During quarterly strategic reviews
  • When a new competitor enters the market

Procedure

Step 1 — Define Intelligence Requirements

  1. Which competitors to profile? (direct, indirect, emerging)
  2. Which dimensions to analyze? (product, pricing, positioning, market share, funding)
  3. What decisions will this intelligence inform?
  4. Audience: sales, product, executive, board?

Step 2 — Competitor Profiles

For each competitor, build a profile:

  • Company overview (size, funding, geography)
  • Product/service offering
  • Target customer and ICP
  • Pricing model and known price points
  • Go-to-market strategy
  • Key strengths and weaknesses
  • Recent moves (launches, hires, partnerships, funding)

Step 3 — Comparison Matrix

FeatureUsCompetitor ACompetitor BCompetitor C
Feature 1✅✅❌✅
Feature 2✅❌✅❌
Pricing$$$$$$$$$$

Step 4 — Positioning Map

Plot competitors on a 2×2 perceptual map using two key dimensions:

  • X-axis: e.g., Price (Low → High)
  • Y-axis: e.g., Capability (Basic → Enterprise)

Step 5 — Win/Loss Analysis

ScenarioWe WonWe LostPattern
vs Competitor A60%40%We win on features, lose on price
vs Competitor B45%55%They win on brand, we win on support

Step 6 — Counter-Strategies

For each competitor, define:

  • How to position against them
  • Key talking points for sales
  • Features/capabilities to highlight
  • Objection handling for their strengths

Inputs

InputRequiredFormat
Competitor listYesNames and categories
Dimensions to trackYesList of comparison areas
Internal product dataYesFeatures, pricing, positioning
Win/loss dataRecommendedDeal outcomes by competitor

Output

## Competitive Intelligence Brief — [Market] — [Period]

### Competitor Profiles
[Summary per competitor]

### Feature Comparison Matrix
[Table with feature-by-feature comparison]

### Positioning Map

          Enterprise │         Competitor B
                     │    ★ US
                     │
          ───────────┼────────────────────
                     │    Competitor C
          Basic      │ Competitor A
                     └──Low Price──High Price──

### Win/Loss Summary
[Table with win rates and patterns]

### Battle Cards
[Per-competitor: positioning, talking points, counter-strategies]

### Early Warning Signals
1. Competitor A raised Series C — expect aggressive expansion
2. Competitor B hired ex-Google VP Product — product pivot likely

Definition of Done

  • All identified competitors profiled
  • Feature comparison matrix complete
  • Positioning map with clear dimensions
  • Win/loss patterns analyzed (if data available)
  • Counter-strategies defined per competitor
  • Early warning signals identified

Examples

Prompt

Build a competitive intelligence brief for our project management SaaS.
Direct competitors: Monday.com, Asana, ClickUp.
Indirect: Notion, Linear.
Compare on: features, pricing, target market, integrations.
Include battle cards for sales team.

Quality Criteria

  • All claims reference specific frameworks, standards, or quantifiable data
  • Content matches the stated audience's expertise level
  • Recommendations are actionable — each includes a concrete next step
  • No unsupported assertions or generic filler language

Verification (4C)

CheckQuestion
CorrectnessDo referenced frameworks and standards match their official definitions?
CompletenessAre all key concepts covered without significant gaps for the stated audience?
Context-fitWould this be useful for someone new to this domain, or is it too advanced/too basic?
ConsequenceIf a stakeholder acted on this immediately, what could they misinterpret?

Edge Cases

  • Conflicting frameworks — State which framework takes precedence and why. Document the trade-off explicitly.
  • Rapidly changing domain — Note information currency date. Flag sections likely to need updates.
  • Audience has mixed expertise levels — Provide a glossary and mark advanced sections as optional.

Changelog

  • v1.0.0 — Initial release

レビュー

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

同じリポジトリのスキル

概要と使いどころ

Design rigorous A/B test plans with hypothesis, sample size calculation, Minimum Detectable Effect (MDE), randomization strategy, and decision rules. Includes guardrail metrics and rollout playbook. Use when planning product experiments, conversion optimization, or data-driven feature decisions.

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

hoavdc/CodexKit252026年10月8日 更新

Review REST and GraphQL API designs for consistency, usability, and best practices. Covers naming conventions, versioning strategy, error format, pagination, authentication patterns, and breaking change detection. Use when reviewing API specs, designing new APIs, or auditing existing endpoints.

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

hoavdc/CodexKit252026年10月8日 更新

Write Architecture Decision Records (ADRs) following the Michael Nygard format. Captures context, options considered, decision rationale, and consequences. Use when making technology choices, framework selections, or any architectural decision that future developers need to understand.

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

hoavdc/CodexKit252026年10月8日 更新

Assess organizational readiness for financial audits (internal or external). Map assertions to account balances, check evidence completeness, score readiness using a Red/Amber/Green framework, and generate a remediation timeline. Aligned with SOX, IFRS, and GAAP audit standards. Use before scheduled audits or when preparing for first-time compliance.

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

hoavdc/CodexKit252026年10月8日 更新

Design safe recurring Codex automations with clear prompts, outputs, schedules, and gating rules.

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

hoavdc/CodexKit252026年10月8日 更新

Refine Product Backlog Items to meet INVEST criteria. Write User Stories with Acceptance Criteria in Given/When/Then format, estimate with Story Points, and flag dependencies. Use before sprint planning when backlog items need grooming. Do not use to prioritize the backlog — that is the Product Owner's decision.

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

hoavdc/CodexKit252026年10月8日 更新

hoavdc のスキルをすべて見る

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