CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

benchmark-methodology

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.

70

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-crafted instruction-only skill body: concrete rubrics, weights, an ordered evidence-collection procedure, explicit bias controls, and a copy-paste output template. It consistently sits just below the top anchors due to repetition between sections, an unspecified tension-plot artifact, and absent failure/recovery guidance.

Suggestions

Consolidate the "score both poles separately / never average" and "no single composite score" guidance — currently stated in four or more places (positioning brief, Why these dimensions, dimension 9, Tension axes, Bias controls, Anti-Patterns) — into one authoritative statement with cross-references.

Specify how the tension 2x2 plot is actually produced (artifact format, axes, quadrant labeling) and add one worked example of a filled profile card row so the output is unambiguous.

Add an explicit recovery step for missing evidence (e.g., what to record when no source supports a dimension) and merge the overlapping Bias controls and Anti-Patterns sections, or move one into a reference file.

DimensionReasoningScore

Conciseness

The body is dense and prescriptive with no explanation of concepts Claude already knows ("No score without evidence", "Distinguish asserted from proven"), but "score BOTH poles, report separately" and the no-single-composite rule are each repeated in four or more places, and "Bias controls" substantially overlaps "Anti-Patterns". That is minor trimmable repetition (anchor 4), not the unnecessary explanation that would warrant 3.

4 / 5

Actionability

Guidance is mostly executable: exact dimension weights, anchored 1-5 rubric, an ordered six-source collection procedure (site, case studies, directories, LinkedIn, portfolio, content channels), and a copy-paste profile card template with a table. It falls short of 5 because "Plot competitors on the tension 2x2" never specifies the artifact format, and there is no worked example of a scored dimension or filled card row.

4 / 5

Workflow Clarity

The sequence is clear and well-ordered — establish the positioning brief first, collect in cheapest-signal-first order, then "Calibrate across the set, not in isolation... re-read scores side-by-side... Adjust outliers" is an explicit pre-finalize checkpoint. It is not 5 because there is no recovery guidance for common failure states (e.g., what to do when no evidence can be found for a dimension).

4 / 5

Progressive Disclosure

No bundle files exist, and the single ~180-line body is well organized with clear section headers (When to Activate, dimensions, rubric, data collection, bias controls, output format, anti-patterns, related skills). It is not 5 because at this length some self-contained blocks (bias controls/anti-patterns, the card template) could live in a one-level reference file, and the skill exceeds the under-50-line simple-skill case where organization alone earns a 5.

4 / 5

Total

16

/

20

Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person voice, explicit what and when with concrete trigger phrases, an enumerated action inventory, and explicit pipeline positioning that separates it from sibling skills. The only weakness is residual overlap with the sibling competitive-* skills in the shared "competitor" trigger space.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Score a scoped competitor set into comparable profile cards", "nine weighted dimensions" with the dimension names enumerated, "1-5 evidence-anchored rubrics", and "a tension 2x2 plot" — giving comprehensive, specific coverage of what the skill does. It is not a 4 because there are no meaningful gaps in the action inventory.

5 / 5

Completeness

Both questions are answered explicitly and concretely: what ("Score a scoped competitor set into comparable profile cards...") and when ("Use when benchmarking or scoring competitors, building a competitive comparison matrix, or grading rival positioning"), plus pipeline positioning ("runs after competitive-platform-analysis and before competitive-report-structure"). This matches the 5 anchor exactly.

5 / 5

Trigger Term Quality

It covers the natural phrasings users would actually say: "benchmarking", "scoring competitors", "building a competitive comparison matrix", and "grading rival positioning" — several synonyms of the same trigger act. Below-anchor check: no commonly used natural term for this task is missing, so it is not a 4.

5 / 5

Distinctiveness Conflict Risk

The niche is clear (evidence-anchored competitor benchmarking into profile cards) and the description explicitly disambiguates from its siblings via ordering ("runs after competitive-platform-analysis and before competitive-report-structure"). It is not 5 because a user asking to "analyze competitors" or "benchmark rivals" could plausibly trigger the sibling analysis/report skills, leaving minor overlap risk with closely related skills.

4 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

affaan-m/ECC

Path

skills/benchmark-methodology/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.