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.

67

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/benchmark-methodology/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The content is a well-structured, actionable methodology with an explicit sequenced workflow, evidence/validation checkpoints, and a ready-to-use output template. Its only real weakness is minor verbosity where rationale and bias-control notes restate earlier points.

Suggestions

Tighten 'Why these dimensions' and 'Bias controls' by merging redundancies with the dimension list and Anti-Patterns section to reclaim tokens.

Consider moving the full nine-dimension weights and anchor table into a reference file so SKILL.md stays a lean overview, if the skill grows.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence, avoiding generic concept explanations, but sections like 'Why these dimensions' and parts of 'Bias controls' restate points already made elsewhere and could be trimmed.

4 / 5

Actionability

It provides concrete, usable artifacts: a 1–5 anchor rubric, a numbered data-collection order, and a copy-ready profile-card template with a markdown table; minor gaps are the placeholder axis anchors that depend on the client brief.

4 / 5

Workflow Clarity

The process is explicitly sequenced (establish brief → collect data in cheapest-signal-first order → score with evidence → calibrate across the set) with validation checkpoints ('No score without evidence', 'Calibrate across the set… adjust outliers') and anti-pattern feedback loops.

5 / 5

Progressive Disclosure

It is a self-contained skill with no bundle files and clear section structure (When to Activate, dimensions, rubric, data collection, output format), so for a skill needing no external references the well-organized overview earns the top anchor.

5 / 5

Total

18

/

20

Passed

Description

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

The description is specific and well-scoped to a distinct pipeline niche with concrete actions. Its main weakness is the 'when' trigger being expressed as workflow position rather than natural user-need phrases, leaving trigger term coverage moderate.

Suggestions

Add a 'Use when the user wants to…' clause with natural phrases like 'benchmark competitors', 'score rivals', or 'create comparable competitor ratings'.

Include common synonyms such as 'competitor scoring' or 'competitive benchmarking' so users who don't name the sibling skills still trigger it.

DimensionReasoningScore

Specificity

Lists nine named scoring dimensions and concrete actions (scores each competitor across them with explicit 1–5 rubrics and a tension-plot), giving comprehensive coverage of what it does.

5 / 5

Completeness

Clearly answers 'what' (scores competitors across nine weighted dimensions) and 'when' (use after competitive-platform-analysis produces a tiered set), but the trigger is framed as a pipeline position rather than explicit user-need phrasing.

4 / 5

Trigger Term Quality

References domain terms (competitor set, dimensions, tension-plot) and named sibling skills, but lacks the natural phrases a user would spontaneously say and omits everyday synonyms like 'benchmark competitors' or 'score rivals'.

3 / 5

Distinctiveness Conflict Risk

It is pinned to a specific pipeline (after competitive-platform-analysis, before competitive-report-structure) and a unique nine-dimension scoring task, giving it a clear niche with minimal overlap risk.

5 / 5

Total

17

/

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.

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.