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…
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
$ npx -y skills add affaan-m/everything-claude-code --skill benchmark-methodology --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/benchmark-methodologyContext preview
The summary Claude sees to decide when to auto-load this skill.
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
name: benchmark-methodology description: 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 to 5 rubrics and a tension-plot. Precedes competitive-report-structure. license: MIT
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.
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.
dimensions matter most for the client's positioning argument.
recommendations must not break this balance without flagging it.
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.
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?
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.
Wouldn't survive a side-by-side.
expectation, ownable by nobody.
would notice and cite.
bar others react to.
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.
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.
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 di
Your agent can write code, but ECC gives it a coordinated engineering system and toolbox: it plans before it builds, verifies changes with tests, reviews its own work from a fresh context, remembers what matters, and turns repeated wins into reusable skills
Repo: affaan-m/everything-claude-code
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…
Full-stack diagnostic for agent and LLM applications. Audits the 12-layer agent stack for wrapper regression, memory pollution, tool discipline failures,…
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…
Design and optimize AI agent action spaces, tool definitions, and observation formatting for higher completion rates. Use when defining or revising an agent's…
Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports. Use when an agent run fails…
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…