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.

73

Quality

91%

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

The canonical home for this skill is report in evo-hq/evo

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 tight, single-purpose skill body with executable commands, clear guardrails against compute spend, and a sequenced overnight-report workflow with validation discipline.

DimensionReasoningScore

Conciseness

Mostly lean and assumes Claude knows the evo domain, but a few phrases (e.g. "even if the user phrases it casually", "That is it") and repeated no-run lists could be trimmed slightly.

4 / 5

Actionability

Concrete executable commands (evo report, evo status, evo frontier, evo show <id>), specific flags (--color, --watch) with defaults, and exact artifact paths — copy-paste ready.

5 / 5

Workflow Clarity

Numbered overnight-report sequence with explicit read-only guardrails and a validation checkpoint (treat missing artifacts as not-recorded, ask user to start fresh runs rather than rerun).

5 / 5

Progressive Disclosure

Well-organized sections (What it shows, How to invoke, When not to use, Overnight reports) with no bundle files needed; appropriately self-contained for a single-purpose skill under the simple-skill exception.

5 / 5

Total

19

/

20

Passed

Description

100%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 precise, well-scoped description that clearly states both what the skill does and when to use it, with strong natural trigger phrases and explicit negative boundaries to prevent mis-triggering.

DimensionReasoningScore

Specificity

Description lists multiple concrete actions (report best/frontier, scatter plot in chat, score chart) tied to a specific read-only evo reporting domain.

5 / 5

Completeness

Explicitly answers what (read-only evo run reporting) and when (specific trigger phrases and invocation), with concrete negative boundaries (never run benchmarks/gates/Slurm).

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases — "asks what happened overnight", "what improved recently", "best/frontier candidates", "quick score chart", "scatter plot in chat" — plus explicit invocation token "/evo:report".

5 / 5

Distinctiveness Conflict Risk

Niche trigger (evo report) with explicit non-use boundaries distinguishing it from optimization/eval skills, minimal conflict risk.

5 / 5

Total

20

/

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.

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.