Communitygithub.com

benchmark-methodology

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

What is benchmark-methodology?

benchmark-methodology is a Claude Code agent skill that 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.

Works with~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/affaan-m/ECC/tree/main/skills/benchmark-methodology

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

Documentation

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:

  • Strategic tension — the two axes (e.g., memorability × hireability) whose intersection marks the client's target white-space. Dimension 9 is always the client's named tension; report both poles separately, never averaged.
  • Differentiator — what makes the client's moat. This informs which dimensions matter most for the client's positioning argument.
  • Brand balance — the intended mix of distinct strategic emphases. Strategic recommendations must not break this balance without flagging it.

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%.

  1. Positioning clarity & distinctiveness (18%) — Is the studio's position sharp, ownable, and instantly legible? Or generic?
  2. Brand voice / verbal distinctiveness (15%) — Does the copy have an ownable register, or is it interchangeable agency-speak?
  3. Visual identity & site craft (15%) — Quality and ownership of the visual system; site as proof-of-craft.
  4. Service offer & packaging (12%) — Productized and legible (named sprints/audits) vs vague. Packaging maturity.
  5. Evidence & credibility (12%) — Named clients, quantified outcomes, case-study depth. Proof beyond assertion.
  6. Enterprise-readiness / commercial maturity (10%) — Signals they can land and hold SaaS/fintech/B2B/enterprise work (process, logos, scale, contracts).
  7. Thought leadership / content presence (8%) — Owned POV: writing, talks, newsletters, frameworks. Depth over volume.
  8. Pricing transparency & engagement model (5%) — Is pricing/engagement legible? Productized vs bespoke vs opaque.
  9. [Client's strategic tension] (5% as a flag; score BOTH poles, 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?

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.

  • 1 — Absent / generic. No discernible position or craft; indistinguishable from a template. Active liability.
  • 2 — Below par. Some intent but inconsistent, derivative, or unconvincing. Wouldn't survive a side-by-side.
  • 3 — Competent / table-stakes. Solid, professional, unremarkable. Meets expectation, ownable by nobody.
  • 4 — Strong / distinctive. Clearly above peers; a real strength a buyer would notice and cite.
  • 5 — Category-defining. Best-in-class, ownable, hard to imitate. Sets the bar others react to.

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:

  • Memorability — 1: forgotten instantly · 3: recognizable in context · 5: unforgettable, talked-about, distinctively owned.
  • Credibility — 1: feels risky/amateur · 3: safe, competent, unexciting · 5: enterprise-trusted, obvious safe choice.

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):

  1. Competitor's own site — positioning, voice, offer packaging, pricing posture, named clients, manifesto/POV. Screenshot the homepage + one case study.
  2. Case studies / work — evidence depth, quantified outcomes, client names. Distinguish asserted ("we delivered X") from proven (metrics, named, verifiable).
  3. Review directories — corroborate clients, project size, engagement model → credibility & enterprise-readiness (e.g. Clutch.co or the niche equivalent).
  4. LinkedIn — team size/model, founder narrative, content cadence → thought leadership, model.
  5. Portfolio / craft platforms — craft register (use the showcase native to the niche: design boards, showreels, published samples, etc.).
  6. Content channels — newsletter/talks/writing → thought-leadership depth.

What to record per dimension: the score, one-line justification, and the source link/screenshot that earned it. No score without evidence.

Bias controls

  • No single composite score. Report dimension scores and the tension plot separately. A weighted average hides the asymmetry that matters.
  • Asserted vs proven. Downgrade credibility/evidence scores for self-reported claims with no corroboration. Site copy is marketing, not fact.
  • Aesthetic affinity bias. Reviewers may over-score studios whose aesthetic they share and under-score rivals' commercial strength. Score craft and credibility independently; a "boring" site may be winning bigger clients.
  • Recency / flashiness bias. Award-winning, showpiece work dazzles but may lack commercial depth — verify with directories/clients before scoring credibility.
  • Survivorship. The visible, well-marketed studios aren't the whole market; note strong-but-quiet operators found via directories/reviews.
  • Calibrate across the set, not in isolation. Before finalizing, re-read scores side-by-side — a "4" must mean the same thing for every competitor. Adjust outliers.

Competitor profile card (output format)

Produce one card per profiled competitor — the atomic unit the report assembles from:

## <Competitor name>
- **Profile / Tier:** <positioning stance · specialization · size band> / <Direct | Adjacent | Aspirational>
- **One-liner:** <how they position themselves, in their words>
- **Model / size / geography:** <solo|micro|boutique> · <region> · <pricing/engagement model>
- **Notable clients / evidence:** <named, with proven/asserted tag>

### Dimension scores
| Dimension | Score (1–5) | Justification (1 line) | Source |
|---|---|---|---|
| Positioning clarity & distinctiveness | | | |
| Brand voice / verbal distinctiveness | | | |
| Visual identity & site craft | | | |
| Service offer & packaging | | | |
| Evidence & credibility | | | |
| Enterprise-readiness / commercial maturity | | | |
| Thought leadership / content presence | | | |
| Pricing transparency & engagement model | | | |

### Tension plot
- **[Axis 1 from positioning brief]:** <1–5> — <why>
- **[Axis 2 from positioning brief]:** <1–5> — <why>
- **Quadrant:** <high/high | high-1/low-2 | low-1/high-2 | low/low>

### Read for [client]
- **Strength to learn from:** <…>
- **Weakness to exploit / white-space it exposes:** <…>
- **Threat to [client]:** <…>

Hand the completed cards plus the tension plot to competitive-report-structure.

Anti-Patterns

  • Averaging the tension axes. The two poles of the client's strategic tension must be scored and reported separately. Averaging destroys the insight — the gap between poles is the finding.
  • Scoring without evidence. Every score requires a one-line justification and a source link. A score without evidence is an opinion, not a benchmark.
  • Creating a single composite score. Report dimension scores individually. A weighted average hides the asymmetric strengths that matter for positioning.
  • Applying generic rubric anchors without adapting. The 1–5 anchors must be calibrated to the specific dimension and competitor set. The generic descriptions are a starting point, not a fixed standard.
  • Running before the competitor set is scoped. Use competitive-platform-analysis first to produce a tiered, pruned set. Scoring an unscoped list wastes effort on irrelevant competitors.

Related Skills

  • competitive-platform-analysis — the prerequisite; produces the tiered competitor set this skill scores.
  • competitive-report-structure — the next step; assembles the scored profile cards into a client-deliverable report.

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

accessibility

Design, implement, and audit inclusive digital products using WCAG 2.2 Level AA. Use when building or auditing UI that must meet WCAG 2.2 Level AA, or when reviewing a change for keyboard, contrast, or screen-reader support.

affaan-m/content-engine

Create platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters, and repurposed multi-platform campaigns. Use when the user wants social posts, threads, scripts, content calendars, or one source asset adapted cleanly across platforms.

affaan-m/ECC

Multi-platform content distribution across X, LinkedIn, Threads, and Bluesky. Adapts content per platform using content-engine patterns. Never posts identical content cross-platform. Use when the user wants to distribute content across social platforms.

affaan-m/fal-ai-media

Unified media generation via fal.ai MCP — image, video, and audio. Covers text-to-image (Nano Banana), text/image-to-video (Seedance, Kling, Veo 3), text-to-speech (CSM-1B), and video-to-audio (ThinkSound). Use when the user wants to generate images, videos, or audio with AI.

affaan-m/manim-video

日本語翻訳:このファイルは manim-video 用の日本語翻訳が必要です

affaan-m/remotion-video-creation

Remotion のベストプラクティス - React で動画を作成する。3D、アニメーション、音声、字幕、チャート、トランジションなどをカバーするドメイン固有の29のルール。

affaan-m/video-editing

AI-assisted video editing workflows for cutting, structuring, and augmenting real footage. Covers the full pipeline from raw capture through FFmpeg, Remotion, ElevenLabs, fal.ai, and final polish in Descript or CapCut. Use when the user wants to edit video, cut footage, create vlogs, or build video content.

agent-architecture-audit

Full-stack diagnostic for agent and LLM applications. Audits the 12-layer agent stack for wrapper regression, memory pollution, tool discipline failures, hidden repair loops, and rendering corruption. Produces severity-ranked findings with code-first fixes. Essential for developers building agent applications, autonomous loops, or any LLM-powered feature. Use when an agent or LLM feature misbehaves and the failing layer is unknown, or before shipping an agent stack.

agent-eval

Head-to-head comparison of coding agents (Claude Code, Aider, Codex, etc.) on custom tasks with pass rate, cost, time, and consistency metrics. Use when choosing between coding agents, or when a change to an agent setup needs measured pass rate, cost, and time rather than an impression.

agent-harness-construction

Design and optimize AI agent action spaces, tool definitions, and observation formatting for higher completion rates. Use when defining or revising an agent

agentic-engineering

Operate as an agentic engineer using eval-first execution, decomposition, and cost-aware model routing. Use when planning or executing engineering work that agents will carry out end to end.

agentic-os

Build persistent multi-agent operating systems on Claude Code. Covers kernel architecture, specialist agents, slash commands, file-based memory, scheduled automation, and state management without external databases. Use when building a persistent multi-agent system on Claude Code with its own memory, commands, and scheduling.

agent-introspection-debugging

Structured 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.

agent-payment-x402

Add x402 payment execution to AI agents with per-task budgets, spending controls, and non-custodial wallets. Supports Base through agentwallet-sdk and X Layer through OKX Payments / OKX Agent Payments Protocol. Use when an agent must pay for something itself and needs per-task budgets, spending controls, and a non-custodial wallet.

agent-self-evaluation

Use after completing any non-trivial task. The agent self-rates its output on 5 axes — accuracy, completeness, clarity, actionability, conciseness — with concrete evidence per criterion. Produces a structured 1-5 scorecard with specific improvement suggestions.

agent-sort

Build 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.

ai-first-engineering

Engineering operating model for teams where AI agents generate a large share of implementation output. Use when setting team process, review gates, or ownership rules for a codebase largely written by agents.

ai-regression-testing

Regression testing strategies for AI-assisted development. Sandbox-mode API testing without database dependencies, automated bug-check workflows, and patterns to catch AI blind spots where the same model writes and reviews code. Use when adding regression coverage to AI-assisted code, or when the same model both wrote and reviewed a change.

android-clean-architecture

Clean Architecture patterns for Android and Kotlin Multiplatform projects — module structure, dependency rules, UseCases, Repositories, and data layer patterns. Use when structuring modules, layers, or data flow in an Android or KMP project.

angular-developer

Generates Angular code and provides architectural guidance. Trigger when creating projects, components, or services, or for best practices on reactivity (signals, linkedSignal, resource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, or CLI tooling.

Related Skills