CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

to-benchmark

Create a benchmark skill from an issue. The benchmark skill runs coding agents against main and an optional branch and reports whether the issue's behaviour improved.

Quality

72%

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 ./.agents/skills/to-benchmark/SKILL.md
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.

The body is a tight, procedural, instruction-only skill with concrete defaults, exact paths, and well-signalled one-level references; no bundle files exist alongside it. Its consistent weakness is minor rather than structural: an inline version requirement, an unlinked KNOWN_ISSUES.md reference, and no post-creation validation of the generated skill.

Suggestions

Move the Codex CLI version requirement out of the body and into KNOWN_ISSUES.md, keeping only the link inline, to remove time-sensitive information from SKILL.md.

Add a validation step after step 5 (e.g., run one repeat of the created benchmark skill to confirm it executes and appends to results.jsonl) before reporting to the user.

Link KNOWN_ISSUES.md and list it in the Reference section so all bundle files are discoverable in one place.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — no basic concepts are explained, and dense domain facts (plugin loading per agent, gitignore behaviour, "Progress is counted in tool calls, never turns") each earn their place. It is not 5 because the inline version requirement "gpt-6.1-sol needs Codex CLI 0.160.0 or later" is time-sensitive information that belongs in KNOWN_ISSUES.md rather than the body.

4 / 5

Actionability

Guidance is concrete throughout: exact output paths (".agents/benchmark-skills/bench-<behaviour>/"), the specific files to copy and edit (TEMPLATE.md, run.py, plot.py), and precise defaults to offer ("claude-opus-5-5", "gpt-6.1-sol", 5 repeats, one lane per agent per arm). It falls short of anchor 5 because the actual run mechanics are deferred to referenced files and the created skill's invocation is only described in one sentence at the end.

4 / 5

Workflow Clarity

A clear 6-step sequence with explicit checkpoints and feedback loops — smoke runs with "expect to revise" in step 2 and "Revise until approved" in step 4. It is not 5 because there is no validation step after writing the benchmark skill (step 5) before reporting to the user (step 6), e.g., a single smoke repeat to confirm the skill runs.

4 / 5

Progressive Disclosure

Well-organized sections (Purpose, Input, Output, Procedure, Reference) with one-level-deep, clearly signalled references — TEMPLATE.md, run.py, plot.py, and EXAMPLE.md are each linked with a stated purpose. It is not 5 because KNOWN_ISSUES.md is mentioned in plain text without a link or listing in the Reference section, and the dense plugin/MCP paragraph in Output could sit in a reference file.

4 / 5

Total

16

/

20

Passed

Description

58%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 states a clear, concrete capability set in third person without fluff, but it entirely lacks a "when to use" clause and natural trigger phrasing. Its strong "what" is undermined by missing trigger guidance, which caps completeness and trigger-term quality at the midpoint.

Suggestions

Add a "Use when..." clause with concrete triggers, e.g., "Use when asked to benchmark, A/B test, or measure whether a branch or PR fixes an issue's behaviour."

Include natural synonyms users would say, such as "compare", "regression", or "measure improvement", to broaden trigger-term coverage.

Briefly extend the capability list (e.g., tracking metrics per run and comparing arms) to push specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Lists three concrete actions — "Create a benchmark skill from an issue", "runs coding agents against main and an optional branch", "reports whether the issue's behaviour improved" — which goes beyond the 1–2 actions of anchor 3. It stops short of anchor 5 because capabilities like the comparison, metrics, and user-confirmation workflow are not mentioned.

4 / 5

Completeness

The "what" is clear (creates a benchmark skill that runs agents against main and a branch and reports improvement), but there is no "Use when..." clause or equivalent trigger guidance, capping completeness at 3 per the judging guidelines. It is above anchor 2 because the "what" is concrete, not vague.

3 / 5

Trigger Term Quality

Relevant keywords are present ("benchmark", "issue", "branch", "coding agents") but there are no natural variations or synonyms a user might say (e.g., "A/B test", "regression", "measure", "compare"), matching anchor 3. It is not 4 because coverage lacks the natural phrasing breadth, and not 2 because the terms are domain-specific rather than generic.

3 / 5

Distinctiveness Conflict Risk

The niche — benchmarking coding-agent behaviour on an issue across main versus a branch — is quite distinct from typical skills, fitting "mostly distinct; minor overlap risk". It is not 5 because the description carries no distinct trigger phrases, leaving slight overlap risk with general testing or benchmarking skills.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 5 missing

Warning

Total

15

/

16

Passed

Repository

withcoral/coral

Path

.agents/skills/to-benchmark/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.