CtrlK
BlogDocsLog inGet started
Tessl Logo

report

Read-only evo run reporting. Use when the user invokes /evo:report, asks what happened overnight, asks what improved recently, asks for the best/frontier candidates, asks for a quick score chart without opening the dashboard, or wants the scatter plot in chat output. Never run benchmarks, gates, Slurm commands, evo run, or ad-hoc verification scripts for report requests.

79

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

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

A well-structured, single-purpose read-only reporting skill that stays lean, leads with an executable command and concrete flags, and sequences the multi-step overnight case clearly. It is self-contained with clean section organization and no unnecessary concept exposition.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence; the chart legend (dot colors, star marker, yellow spine, stair line) is custom evo-dashboard semantics that earns its tokens rather than generic explanation, and no basic concepts are re-explained.

3 / 3

Actionability

Provides a copy-paste 'evo report' code block plus concrete flags with defaults ('--color always|never|auto', '--watch [SECONDS]') and a specific list of read-only subcommands, giving fully executable, copy-paste-ready guidance.

3 / 3

Workflow Clarity

The primary action is unambiguous (run 'evo report', print output verbatim), and the overnight case is a clear 4-step numbered procedure with a reporting checklist; because all operations are read-only, the missing-validation cap for destructive/batch work does not apply.

3 / 3

Progressive Disclosure

The skill is self-contained with no bundle files and no nested references, organized into clear sections (What it shows, How to invoke, When not to use, Overnight/Improvement Reports); for a single-purpose skill this well-organized structure earns the top anchor.

3 / 3

Total

12

/

12

Passed

Description

100%Weight 40%Scale 1-3

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, third-person description that concisely states a read-only reporting purpose, gives an explicit and natural 'Use when...' trigger set, and uses negative constraints to sharply delineate it from compute-spending skills. It covers what, when, and distinctiveness without padding.

DimensionReasoningScore

Specificity

Names the domain ('Read-only evo run reporting') alongside multiple concrete actions such as 'quick score chart', 'scatter plot in chat output', and 'best/frontier candidates', matching the anchor for listing multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers 'what' (read-only evo run reporting with scope set by the negative constraints) and 'when' via a present 'Use when...' clause with multiple triggers, satisfying the both-what-and-when anchor.

3 / 3

Trigger Term Quality

Includes natural phrases a user would actually say ('what happened overnight', 'what improved recently', 'best/frontier candidates', 'quick score chart') plus the explicit /evo:report invocation, giving good coverage of natural trigger terms.

3 / 3

Distinctiveness Conflict Risk

The narrow evo-reporting niche, distinct /evo:report trigger, and explicit 'Never run benchmarks, gates, Slurm commands, evo run...' exclusion clearly separate it from sibling execution skills, making wrong-skill conflicts unlikely.

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
evo-hq/evo
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.