CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

minimal-good

Use when testing doraval validate and drift commands.

Quality

63%

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

Fix and improve this skill with Tessl

tessl review fix ./test/fixtures/skills/minimal-good/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 appropriately short and well-organized for a simple skill, but its guidance is not actionable: the test-running step has no actual command, verification is unspecified, and the `echo hello` code block is a placeholder unrelated to the workflow. The dangling 'MUST follow the rubric' instruction also adds noise without informational value.

Suggestions

Replace 'Run the test suite' with the actual executable command (e.g. the specific test runner invocation for doraval) so the step is copy-paste ready.

Make 'Verify the output' concrete: state what output to expect, what 'passing' looks like, and what to do when a check fails (a validate -> fix -> retry loop).

Either connect the `echo hello` code block to the actual workflow or remove it, and drop the 'MUST follow the rubric / MUST NOT skip steps' lines that reference material not present in the skill.

DimensionReasoningScore

Conciseness

The body is very lean with no concept over-explanation, but 'MUST follow the rubric. MUST NOT skip steps.' references an external rubric not present in the skill, and 'Ensure all checks pass' restates step 2 — minor tokens that could be trimmed. Anchor 4 ('minor instances of over-explanation that could be trimmed') fits better than 5.

4 / 5

Actionability

The real steps are high-level hints: 'Run the test suite' gives no command, suite name, or entry point, and 'Verify the output' is vague. The only executable code (`echo hello`) is a placeholder unconnected to the task, matching anchor 2 ('minimal concrete guidance; high-level hints but missing the specific steps to execute') rather than 3.

2 / 5

Workflow Clarity

A rough sequence exists (run tests, then verify output) and 'Ensure all checks pass' implies a checkpoint, but steps lack executable detail and validation is implicit only. This matches anchor 3 ('steps listed but validation gaps; checkpoints missing or implicit'), not 4 which requires concrete commands per step.

3 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, and needs no external references; content is organized into a heading, numbered step list, note, and code block. Per the simple-skill scoring note, well-organized short content with no needed references scores 5.

5 / 5

Total

14

/

20

Passed

Description

51%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 has strong trigger terms and is highly distinct due to the niche 'doraval' tooling references, but it is incomplete: it tells when to use the skill without ever stating what the skill does. It also lacks concrete action verbs, leaving the capability set entirely implicit.

Suggestions

Add a 'what' clause describing the concrete actions the skill performs, e.g. 'Runs the doraval test suite and checks validate/drift command output against expected results.'

Expand trigger coverage with a few natural variations users might say, such as 'testing doraval', 'validating doraval output', or 'checking for drift'.

State the expected outcome or scope (e.g. which commands are covered and what 'passing' means) so the description answers both 'what' and 'when'.

DimensionReasoningScore

Specificity

The description names the domain ('doraval validate and drift commands') but states no concrete actions — there is no verb describing what the skill does. It matches anchor 2 ('Names the domain but actions are minimal or generic') rather than 3, which requires 1-2 concrete actions.

2 / 5

Completeness

Only 'when' is present ('Use when testing...') with no 'what' — the skill's actual behavior is never described. This exactly matches anchor 2 ('only when is present without what') and falls short of anchor 3, which requires a clear 'what'.

2 / 5

Trigger Term Quality

Terms like 'testing', 'doraval', 'validate', 'drift', and 'commands' are the natural phrases a user of this tool would say. Good keyword coverage per anchor 4, but not 5 since no synonyms or variations (e.g. 'check', 'run') are included.

4 / 5

Distinctiveness Conflict Risk

The description is tied to a niche tool ('doraval') with distinct subcommand triggers ('validate', 'drift'), giving it a clear niche with minimal conflict risk against other skills, matching anchor 5.

5 / 5

Total

13

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

saif-shines/doraval

Path

test/fixtures/skills/minimal-good/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.