Benchmark MethodologySAFE
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Overview
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
8c9f7312d3d6OBSERVED · 2026-10-22What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
---
name: benchmark-methodology
description: "Score a scoped competitor set into comparable profile cards: nine weighted dimensions (positioning, voice, visual craft, offer packaging, evidence, enterprise-readiness, thought leadership, pricing, client tension) with 1-5 evidence-anchored rubrics and a tension 2x2 plot. Use when benchmarking or scoring competitors, building a competitive comparison matrix, or grading rival positioning before assembling the report; runs after competitive-platform-analysis and before competitive-report-structure."
license: MIT
---
# 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 boardTrust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | NA |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
8c9f7312d3d6full audit observations/trust-audit/skill/affaan-m__benchmark-methodology.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-22 | 8c9f7312d3d6 | SAFE | B | 89 | first audit |
Questions
What does the benchmark-methodology — affaan-m/everything-claude-code skill do?
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Is benchmark-methodology — affaan-m/everything-claude-code safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can benchmark-methodology — affaan-m/everything-claude-code access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (8c9f7312d3d6), read on 2026-10-22. The repository is watched, and a new audit runs when it changes — this is the first audit.
Add this badge to your README
Shows this page's audit result and links back to it. It updates when the audit does.
[](https://modelsatlas.com/skills/affaan-m/benchmark-methodology/)
Not your listing, or something out of date? Claim or update your listing.