Mmcp.market

benchmark-methodology skill

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

Use after competitive-platform-analysis has produced a tiered competitor set. Scores each competitor across nine weighted dimensions (positioning, voice, visual craft, offer packaging, evidence, enterprise-readiness, thought leadership, pricing, client's strategic tension) with explicit 1–5 rubrics and a tension-plot. Precedes competitive-report-structure.

A100/100content scan

Is the benchmark-methodology 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 benchmark-methodology 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/benchmark-methodology ~/.claude/skills/benchmark-methodology
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

Benchmark Methodology

Use this skill to turn a scoped competitor set into comparable, defensible scores. Each competitor is assessed on the same nine dimensions, with explicit 1–5 rubrics, then captured in a uniform profile card. Consistency is the point: scores are only useful if the same evidence would earn the same number for any competitor.

When to Activate

  • A scoped, tiered competitor set from competitive-platform-analysis is ready to score.
  • Need comparable, evidence-anchored scores across competitors — not gut-feel rankings.
  • Client's strategic tension (the paired axes defining their target white-space) has been established.
  • Preparing to produce profile cards for assembly in competitive-report-structure.

Client positioning brief (establish first)

Before scoring, establish the client's positioning brief. It supplies:

intersection marks the client's target white-space. Dimension 9 is always the client's named tension; report both poles separately, never averaged.

  • Strategic tension — the two axes (e.g., memorability × hireability) whose

dimensions matter most for the client's positioning argument.

  • Differentiator — what makes the client's moat. This informs which

recommendations must not break this balance without flagging it.

  • Brand balance — the intended mix of distinct strategic emphases. Strategic

Why these dimensions

The client competes on a specific tension held across two poles, not on service breadth. The dimensions are weighted to reflect that moat. Two dimensions — the tension poles — are scored separately and never averaged together, because the client's strategic question is precisely whether a rival achieves both simultaneously.

The nine dimensions (with weights)

Weights guide synthesis emphasis, not a single blended score (avoid a false composite — see Bias controls). Sum = 100%.

sharp, ownable, and instantly legible? Or generic?

  1. Positioning clarity & distinctiveness (18%) — Is the studio's position

ownable register, or is it interchangeable agency-speak?

  1. Brand voice / verbal distinctiveness (15%) — Does the copy have an

system; site as proof-of-craft.

  1. Visual identity & site craft (15%) — Quality and ownership of the visual

sprints/audits) vs vague. Packaging maturity.

  1. Service offer & packaging (12%) — Productized and legible (named

case-study depth. Proof beyond assertion.

  1. Evidence & credibility (12%) — Named clients, quantified outcomes,

and hold SaaS/fintech/B2B/enterprise work (process, logos, scale, contracts).

  1. Enterprise-readiness / commercial maturity (10%) — Signals they can land

newsletters, frameworks. Depth over volume.

  1. Thought leadership / content presence (8%) — Owned POV: writing, talks,

legible? Productized vs bespoke vs opaque.

  1. Pricing transparency & engagement model (5%) — Is pricing/engagement

report separately**) — Read the tension name and axis descriptions from the client's positioning brief. Plot both; the gap is the insight. The client's target quadrant is the single most important finding: who else is already there?

  1. [Client's strategic tension] (5% as a flag; **score BOTH poles,

Scoring rubric (1–5, applies to dimensions 1–8)

Anchor every score to observable evidence. Generic descriptors below; adapt the specifics per dimension but keep the level meaning constant.

from a template. Active liability.

  • 1 — Absent / generic. No discernible position or craft; indistinguishable

Wouldn't survive a side-by-side.

  • 2 — Below par. Some intent but inconsistent, derivative, or unconvincing.

expectation, ownable by nobody.

  • 3 — Competent / table-stakes. Solid, professional, unremarkable. Meets

would notice and cite.

  • 4 — Strong / distinctive. Clearly above peers; a real strength a buyer

bar others react to.

  • 5 — Category-defining. Best-in-class, ownable, hard to imitate. Sets the

Tension axes (dimension 9) — score each 1–5

Read the axis labels and their 1/3/5 anchors from the client's positioning brief. Example anchors for a memorability × credibility tension:

5: unforgettable, talked-about, distinctively owned.

  • Memorability — 1: forgotten instantly · 3: recognizable in context ·

unexciting · 5: enterprise-trusted, obvious safe choice.

  • Credibility — 1: feels risky/amateur · 3: safe, competent,

Plot competitors on the tension 2×2. The client's target quadrant is named in the positioning brief. Who else occupies that quadrant is the single most important finding of the benchmark.

How to collect the data

For each competitor, work the dimensions in this order (cheapest signal first):

posture, named clients, manifesto/POV. Screenshot the homepage + one case study.

  1. Competitor's own site — positioning, voice, offer packaging, pricing

Distinguish asserted ("we delivered X") from proven (metrics, named, verifiable).

  1. Case studies / work — evidence depth, quantified outcomes, client names.

→ credibility & enterprise-readiness (e.g. Clutch.co or the niche equivalent).

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