skill-name

Explain exactly when this skill should fire, what inputs it expects, and what problem it solves.

Quality

28%

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 ./skills/_template/SKILL.md

Quality

Content

57%

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 clean, well-organized template skeleton that is token-efficient but contains no actionable content — every section is an authoring prompt awaiting real instructions. It scores well on structure and brevity but fails on delivering executable guidance.

Suggestions

Replace placeholder prompts with concrete, executable instructions or code examples under each section.

For any multi-step or destructive workflow, add explicit validation/verification checkpoints with commands.

Fill in real trigger conditions, edge cases, and output expectations rather than generic labels.

Dimension	Reasoning	Score
Conciseness	The body is a lean ~35-line skeleton with no padding or explanation of concepts Claude already knows; every line is a short structural prompt.	3 / 3
Actionability	It provides only placeholder prompts ('First action the skill should take', 'What recurring problem does this skill solve?') with no concrete code, commands, or specific guidance.	1 / 3
Workflow Clarity	A numbered 1-2-3 sequence with a 'Verification or handoff' step exists, but the steps are placeholder labels with no real validation checkpoints or content.	2 / 3
Progressive Disclosure	It is under 50 lines with well-organized sections and no bundle files, so the simple-skill allowance applies and the structure is clear.	3 / 3
	Total	9 / 12 Passed

Description

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is an unfilled template description: meta-instructional placeholder text rather than a real skill description. It fails every dimension because it describes no capability, trigger, or niche.

Suggestions

Replace the placeholder with a concrete description of the skill's actual actions (e.g., 'Extract text and tables from PDF files, fill forms, merge documents').

Add an explicit 'Use when...' clause listing natural trigger phrases users would say.

Use third-person voice naming the specific domain and tools so the skill is distinguishable from others.

Dimension	Reasoning	Score
Specificity	The description ('Explain exactly when this skill should fire, what inputs it expects, and what problem it solves') is author-instruction text that names no concrete domain actions, matching the vague/abstract anchor.	1 / 3
Completeness	It answers neither 'what' nor 'when' — it is a prompt instructing the author to write those, with no 'Use when...' clause, so it fails both halves.	1 / 3
Trigger Term Quality	It contains no natural keywords a user would say; the text is meta-guidance to the author rather than trigger terms.	1 / 3
Distinctiveness Conflict Risk	The text is completely generic and contains no domain signals, so it would conflict with essentially any skill.	1 / 3
	Total	4 / 12 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: NateBJones-Projects/OB1
Path: skills/_template/SKILL.md
Commit: 6779106

Reviewed: about 15 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.