Mmcp.market

competitive-platform-analysis skill

by affaan-m·affaan-m/ECC·269k stars·MIT

Use when scoping a competitive landscape — identifying, categorising, and score-filtering a competitor set before any benchmarking begins. Decides who counts as a competitor, which tier they belong to, and which sources to mine. First step in the three-skill competitive pipeline; precedes benchmark-methodology.

A100/100content scan

Is the competitive-platform-analysis skill safe?

Clean: nothing in its files matched our rules. We read 2 files in the folder on 2026-09-28.

No findings.

Install the competitive-platform-analysis skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description.

git clone --depth 1 https://github.com/affaan-m/ECC.git /tmp/ECC
mkdir -p ~/.claude/skills
cp -r /tmp/ECC/.agents/skills/competitive-platform-analysis ~/.claude/skills/competitive-platform-analysis
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

Competitive Platform Analysis

Use this skill to decide who to benchmark and where to find them before any scoring begins. A competitive analysis is only as good as its frame: the wrong set makes the client look either unbeatable or doomed. The goal is a defensible, decision-relevant set — not an exhaustive census.

When to Activate

  • About to start a competitive benchmarking project and need to define the competitor set first.
  • Unsure which companies belong in Direct / Adjacent / Aspirational tiers.
  • Need a defensible, pruned scope for a market landscape report.
  • Has a positioning brief and wants to identify who contests that position.
  • First step before running benchmark-methodology.

Client positioning brief (establish first)

Before scoping the set, establish the client's positioning brief. If you don't already have it, run a short brand-discovery interview to elicit it — do not invent one and do not scope the set blind. The brief supplies:

how it presents itself.

  • Identity / aesthetic register — what kind of studio or company this is and

prioritize by distinctiveness vs. capability overlap vs. price).

  • Offer — what services or products it delivers.
  • Target clients — who it sells to.
  • Differentiator — the moat or positioning argument the client believes in.
  • Scoping consequence — the implication for how to weight competitors (e.g.,

(e.g., memorability × hireability).

  • Strategic tension — the paired axes that define the client's white-space

Do not proceed without the positioning brief. A competitor list scoped without the client's lens is noise, not intelligence. The scoping consequence in particular determines which competitors are strong rivals (those that contest the client's moat) vs. merely overlapping on service menu.

Selection criteria

For each candidate, capture these axes — they decide both inclusion and tier:

agency. Match the client's own band; same-band studios are the realistic head-to-head set.

  • Size / model — solo, micro-studio (2–8), boutique (sub-30), mid-size

the client's offer. Tighter overlap = more direct.

  • Niche / specialization — how closely the candidate's focus overlaps with

Note whether they win the same clients the client targets.

  • Geography / market — EU vs US vs global-remote; language; time-zone reach.

day-rate; transparent vs "contact us". Signals positioning maturity.

  • Pricing & engagement model — productized sprints, retainer, project,

to the client's aesthetic register = more they contest the client's distinctiveness.

  • Portfolio style — generic vs. opinionated/editorial vs. contrarian. Closer

story includes public process work, open tooling, or documented systems.

  • Technical depth / craft maturity — relevant if the client's credibility

is it interchangeable? Weight this per the client's scoping consequence.

  • Brand strength — does the studio have an ownable verbal/visual identity, or

Player taxonomy — axes to populate across

Don't sort competitors into niche-specific buckets; sort them along a few generic axes so the landscape isn't skewed toward one archetype. These axes apply to any creative-service market (design, motion, copywriting, branding, content, film, etc.). Aim for breadth across each axis first, then prune to the most instructive.

voice, POV) vs capability-led (competes on craft, throughput, outcomes). Populate both poles; the client's closest mirror sits at its own end.

  1. Positioning stance — brand-led / editorial (competes on identity,

generalist (broad service menu). Tighter overlap with the client's focus = more direct.

  1. Specialization — specialist (one tight discipline or vertical) vs

enterprise-scale. Same-band players are the realistic head-to-head; larger bands are the aspirational/commercial-maturity reference.

  1. Size / model — solo / micro vs boutique vs mid-size vs

vs bespoke (custom project / retainer). Signals positioning maturity.

  1. Engagement format — productized (named sprints, audits, fixed packages)

manifesto-driven*. The opinionated end is key for distinctiveness benchmarking in any niche.

  1. Distinctiveness posture — conventional / safe vs *contrarian /

case depth) vs aesthetic-led (portfolio, awards). Tells you how each player earns trust.

  1. Evidence / credibility model — outcome-led (metrics, named clients,

identity* (including senior independents who prove the "memorable solo brand" model).

  1. Brand strength of the operator — interchangeable vs *cult / ownable

win the same clients the client targets.

  1. Market / reach — local / regional vs global-remote; note whether they

Plot each candidate on the relevant axes; a competitor is direct when it sits near the client on positioning, specialization, size, and market at once.

Competitive tiers (how the set resolves)

Group the final set into three tiers — this structure carries through to the report:

head-to-head.

  • Direct — same band, overlapping offer, same client targets. The realistic

that pressures at the edges.

  • Adjacent — partial overlap (one capability, or a different client size)

brand or commercial maturity sets the bar to aim at.

  • Aspirational — players the client is not competing with today but whose

freelancers — note as a threat vector, not a profiled competitor unless materially relevant.)*

  • *(Watch also for substitutes: no-code/AI tools, in-house teams, generalist

Data sources (where to look)

Match the source to the dimension you need. The platform types below are generic; substitute the ones native to the client's niche (e.g. Dribbble/Behance for design, showreel/Vimeo for motion, writing samples/published work for copy):

More skills from affaan-m/ECC

  • AaccessibilityWCAG 2.2 レベル AA 標準を用いてインクルーシブなデジタルプロダクトを設計・実装・監査します。Web 用のセマンティック ARIA および Web・ネイティブプラットフォーム(iOS/Android)のアクセシビリティトレイトを生成するために使用します。
  • Aagent-architecture-auditエージェントおよび LLM アプリケーション向けのフルスタック診断。12 層のエージェントスタックにおけるラッパーリグレッション、メモリ汚染、ツール規律の失敗、隠れた修復ループ、レンダリング破損を監査します。重要度順の発見事項とコードファーストの修正を生成します。エージェントアプリケーション、自律ループ、または LLM を活用した機能を構築する開発者に必須です。
  • Aagent-evalカスタムタスクでコーディングエージェント(Claude Code、Aider、Codex など)をヘッドツーヘッドで比較し、合格率、コスト、時間、一貫性のメトリクスを測定します
  • Aagent-harness-constructionAI エージェントのアクション空間、ツール定義、観測フォーマットを設計・最適化して完了率を向上させます。
  • Aagent-introspection-debuggingStructured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports. Use when an agent run fails and you need a reproducible diagnosis instead of a retry.
  • Aagent-introspection-debuggingキャプチャ、診断、封じ込め回復、内省レポートを使用した AI エージェント障害のための構造化された自己デバッグワークフロー。
  • Aagent-payment-x402タスクごとのバジェット、支出コントロール、ノンカストディアルウォレットを備えた x402 決済実行を AI エージェントに追加します。agentwallet-sdk を通じて Base をサポートし、OKX Payments / OKX エージェント決済プロトコルを通じて X Layer をサポートします。
  • Aagent-sortBuild an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.
  • Aagent-sort並行リポジトリ対応のレビューパスを使用して、スキル、コマンド、ルール、フック、エクストラを DAILY と LIBRARY のバケットに分類することで、特定のリポジトリ向けのエビデンスに基づいた ECC インストール計画を構築します。プロジェクトが完全なバンドルをロードする代わりに実際に必要なものに ECC をトリミングする必要がある場合に使用します。
  • Aagentic-engineeringOperate as an agentic engineer using eval-first execution, decomposition, and cost-aware model routing. Use when AI agents perform most implementation work and humans enforce quality and risk controls.
  • Aagentic-engineering評価ファースト実行、分解、コスト対応モデルルーティングを使用してエージェニックエンジニアとして動作します。
  • Aagentic-osClaude Code 上に永続的なマルチエージェントオペレーティングシステムを構築します。カーネルアーキテクチャ、スペシャリストエージェント、スラッシュコマンド、ファイルベースのメモリ、スケジュールされた自動化、外部データベースなしの状態管理をカバーします。

All agent skills → · MCP servers