skill-one

Sample skill

Quality

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 ./tests/fixtures/sample-plugin/skills/skill-one/SKILL.md

Quality

Content

0%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 one-line placeholder ("Skill body.") with no executable guidance, workflow, or structure, and no bundle files exist to provide progressive disclosure. It scores at the floor on every dimension.

Suggestions

Replace the placeholder with concrete, executable guidance (e.g. working code examples or specific commands) covering the skill's primary task.

Add a clear sequenced workflow with validation checkpoints if the task involves multi-step or risky operations.

Move detailed or reference material into separate files under references/ and link to them from the SKILL.md overview to establish progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is a single placeholder line ("Skill body.") that adds nothing Claude does not already know; it is token waste rather than lean, useful content.	1 / 5
Actionability	No concrete code, commands, or steps are provided — the body only describes via a placeholder word and does not instruct.	1 / 5
Workflow Clarity	There is no sequence of steps and no validation checkpoints, only a non-instructional placeholder.	1 / 5
Progressive Disclosure	The content has no structure, section headers, or references, and no bundle files exist to organize, making it un-navigable.	1 / 5
	Total	4 / 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 bare placeholder ("Sample skill") that conveys no capability, no trigger context, and no distinction from other skills. It fails every dimension of the rubric at the lowest anchor.

Suggestions

Replace "Sample skill" with concrete actions and a named domain, e.g. "Extract text and tables from PDF files, fill forms, merge documents."

Add an explicit "Use when..." clause naming natural trigger phrases users would actually say.

Include relevant file extensions and synonyms to distinguish this skill from adjacent ones and reduce conflict risk.

Dimension	Reasoning	Score
Specificity	The description is "Sample skill" — it names no domain and no concrete actions, matching the entirely-vague anchor with pure abstract language.	1 / 5
Completeness	Both the "what does this do" and "when should Claude use it" answers are missing, with only a placeholder word present.	1 / 5
Trigger Term Quality	"Sample skill" contains no natural keywords a user would say to invoke a capability, only generic placeholder language.	1 / 5
Distinctiveness Conflict Risk	The description is entirely generic and would conflict with virtually any other skill, providing no distinguishing niche.	1 / 5
	Total	4 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
description_field	'description' is very short (12 chars), consider making it more detailed	Warning

	Total	15 / 16 Passed

Repository: EveryInc/compound-engineering-plugin
Path: tests/fixtures/sample-plugin/skills/skill-one/SKILL.md
Commit: 8a6e0a2

Reviewed: 3 days 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.