valid-skill

A valid skill for testing purposes.

Quality

16%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./legacy_pi_mono_code/pi-mono/packages/coding-agent/test/fixtures/skills/valid-skill/SKILL.md

The canonical home for this skill is valid-skill in can1357/oh-my-pi

Quality

Content

33%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 token-efficient but content-free: it describes the file's compliance with a standard rather than instructing Claude to do anything. It contains no actionable guidance and no workflow, making it unusable as a skill body despite its small size.

Suggestions

Replace the meta-statement with concrete, executable guidance for the skill's actual task (specific commands, code, or step-by-step instructions).

If the skill genuinely has a single purpose, state that one action unambiguously so workflow clarity can benefit from the simple-skill exception.

Remove the 'follows the Agent Skills standard' sentence — it explains nothing and spends tokens without adding capability.

Dimension	Reasoning	Score
Conciseness	The body is only two lines with no padded explanations of concepts Claude already knows. It falls short of a 5 because the sentence "This is a valid skill that follows the Agent Skills standard" is a meta-statement that could be trimmed — it adds no value — but there are no unnecessary explanations beyond that.	4 / 5
Actionability	"This is a valid skill that follows the Agent Skills standard" only describes the file; there is no code, command, or concrete instruction anywhere in the body. This matches the anchor 'Entirely vague or abstract; only describes rather than instructs' and is not level 2, which requires at least high-level hints toward execution.	1 / 5
Workflow Clarity	No steps, sequence, or single actionable task is present, so the simple-skill exception (a single unambiguous action) cannot apply. It matches anchor 1 ('Steps missing or incoherent') and cannot be level 2 because no rough sequence exists either.	1 / 5
Progressive Disclosure	The skill is under 50 lines with no external references needed and nothing inlined that belongs in a separate file. It falls between the simple-skill exception (5, requiring well-organized sections) and anchor 3 (content that should be separate is inline): a single bare heading over one filler sentence provides minimal organization, so 4 is the best fit.	4 / 5
	Total	10 / 20 Passed

Description

0%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 a placeholder that fails all four dimensions: it states no capability, no domain, no trigger conditions, and nothing that distinguishes it from any other skill. It is the archetype of a bad description like 'Helps with documents' but with even less information, since not even a domain is named.

Suggestions

State what the skill actually does using concrete third-person verbs and a named domain (e.g., 'Validates SKILL.md files against the Agent Skills frontmatter schema').

Add an explicit 'Use when...' clause with natural trigger phrases and file extensions users would say (e.g., 'Use when checking or reviewing skill files, SKILL.md, or frontmatter validity').

Remove 'for testing purposes' unless the skill's genuine purpose is testing — as written it reads as filler and invites no relevant triggering.

Dimension	Reasoning	Score
Specificity	"A valid skill for testing purposes" names no domain and no concrete actions — it is a pure abstract meta-statement, matching anchor 1 ('Entirely vague; no concrete actions'). It cannot be level 2, since that anchor at least names a domain ('Processes PDF files').	1 / 5
Completeness	Neither 'what' (no capability described) nor 'when' (no 'Use when...' clause) is present; the description only asserts the skill is 'valid' and 'for testing purposes'. This matches anchor 1 ('Missing both what and when'), and the missing-trigger cap of 3 is irrelevant because even the 'what' is absent.	1 / 5
Trigger Term Quality	The description contains no keywords a user would naturally say when needing this skill — no domain nouns, no synonyms, no file extensions. This matches anchor 1 ('No natural keywords; only technical jargon or entirely generic language').	1 / 5
Distinctiveness Conflict Risk	"A valid skill for testing purposes" is entirely generic and indistinguishable from any other placeholder skill, so it would conflict with virtually anything. It matches anchor 1 and not anchor 2, which requires at least a broad domain like 'document files'.	1 / 5
	Total	4 / 20 Passed

Validation

100%

Warnings & errors only

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: Dicklesworthstone/pi_agent_rust
Path: legacy_pi_mono_code/pi-mono/packages/coding-agent/test/fixtures/skills/valid-skill/SKILL.md
Commit: 38d4f88

Reviewed: 2 hours ago

Table of Contents

Discovery Implementation Validation

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.