CtrlK
BlogDocsLog inGet started
Tessl Logo

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's strategic tension) with explicit 1–5 rubrics and a tension-plot. Precedes competitive-report-structure.

68

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

A well-structured, highly actionable methodology with explicit rubrics, a defined collection procedure, a copy-paste output template, and clear validation via calibration. The main gaps are token-efficiency (heavy repetition of the no-averaging rule) and the absence of progressive disclosure — everything lives in one ~150-line file.

Suggestions

Consolidate the 'score both tension poles, never average them' guidance into one authoritative statement and reference it, rather than restating it in five sections.

Move the nine-dimension definitions and/or the profile-card template into a referenced file (e.g. DIMENSIONS.md or PROFILE-CARD.md) to enable progressive disclosure and shorten the main SKILL.md overview.

DimensionReasoningScore

Conciseness

The body is dense and free of generic filler Claude already knows, but the 'never average the tension axes' rule is restated across at least five sections (Client positioning brief, Why these dimensions, dimension 9, Bias controls, Anti-Patterns) and the tension concept is explained twice; it is mostly efficient but could be tightened, fitting level 2 rather than the every-token-earns-its-place level 3.

2 / 3

Actionability

Provides explicit 1-5 rubric anchors, a numbered data-collection order with per-source extraction guidance ('Screenshot the homepage + one case study', 'Distinguish asserted from proven'), and a copy-paste-ready competitor profile card template; concrete and specific, matching the level-3 anchor for an instruction-only skill.

3 / 3

Workflow Clarity

Clear sequence (positioning brief -> score nine dimensions -> profile cards -> hand to competitive-report-structure) with precondition gating in 'When to Activate' and an explicit validation checkpoint in Bias controls ('re-read scores side-by-side ... a 4 must mean the same thing ... Adjust outliers'), meeting the level-3 clear-sequence-with-validation bar.

3 / 3

Progressive Disclosure

Well-organized into clearly headed sections, but the skill is entirely monolithic (~150 lines with no external detail references); at this length it exceeds the under-50-line simple-skill threshold where organization alone earns a 3, and the dimension definitions and output template are inline content the level-3 anchor expects to be split into signaled one-level-deep references.

2 / 3

Total

10

/

12

Passed

Description

85%

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, specific description that clearly states both what the skill does and when to use it via explicit pipeline triggers. Its main weakness is trigger-term quality: it relies on skill-name references rather than the natural language a user would say when they need competitive benchmarking.

Suggestions

Add natural-language trigger terms a user would actually say, e.g. 'Use when benchmarking competitors, scoring rival agencies, or producing a competitive comparison'.

Lead with the user-facing capability ('Benchmark and score competitors...') before the pipeline-position framing so the trigger is recognizable on its own.

DimensionReasoningScore

Specificity

Lists nine concrete named dimensions ('positioning, voice, visual craft, offer packaging, evidence, enterprise-readiness, thought leadership, pricing, client's strategic tension') plus rubric scoring and a 'tension-plot' — multiple specific concrete actions, matching the level-3 anchor rather than the partial level-2.

3 / 3

Completeness

Explicitly answers what ('Scores each competitor across nine weighted dimensions ... with explicit 1-5 rubrics and a tension-plot') and when ('Use after competitive-platform-analysis has produced a tiered competitor set') with explicit trigger guidance, satisfying the level-3 anchor and avoiding the missing-trigger cap at 2.

3 / 3

Trigger Term Quality

Contains relevant keywords ('competitor', 'scores', 'dimensions', 'rubrics') but is positioned by skill-name reference ('Use after competitive-platform-analysis') rather than natural user phrases like 'benchmark competitors' or 'score these competitors'; missing common variations a user would say, so it is not the full level-3 coverage.

2 / 3

Distinctiveness Conflict Risk

A clear niche — weighted nine-dimension competitor scoring with tension plots — anchored by named pipeline neighbors ('Precedes competitive-report-structure'), making it unlikely to trigger for unrelated skills; matches the level-3 'clear niche with distinct triggers' anchor.

3 / 3

Total

11

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
affaan-m/ECC
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.