template-skill

Replace with description of the skill and when Claude should use it.

2.27x

Quality

Does it follow best practices?

Impact

100%

2.27x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./claude/skills/template-skill/SKILL.md

Quality

Content

7%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 an empty template stub with no instructions, examples, workflow, or referenced materials. Every dimension scores at or near the floor because there is no actual skill content to evaluate.

Suggestions

Replace the placeholder with the skill's core instructions: the concrete actions Claude should take, with executable code or commands for the common cases.

If the skill is multi-step, list the steps in sequence with explicit validation checkpoints before any destructive or batch operation.

Keep detail that Claude already knows out of SKILL.md and move large reference material into files under references/ with one-level-deep, clearly signaled links.

Dimension	Reasoning	Score
Conciseness	The body is a single placeholder line ("# Insert instructions below") — not verbose, so it is above the score-1 'severely verbose' anchor, but the tokens present are meta-instruction rather than skill content, so they do not 'earn their place' and it falls well below the lean-and-informative score-5 anchor.	2 / 5
Actionability	No concrete code, commands, or specific guidance appear — only a directive to insert instructions, matching 'Entirely vague or abstract; no concrete code or commands' and not reaching score 2 which requires at least high-level hints.	1 / 5
Workflow Clarity	There are no sequenced steps, no checkpoints, and no validation; the body has no workflow at all, matching the 'Steps missing or incoherent; no sequence' anchor.	1 / 5
Progressive Disclosure	There is no meaningful structure or navigation and no bundle files exist in references/, scripts/, or assets/; the single placeholder header provides nothing to navigate, matching the 'no structure; impossible to navigate' end of the scale rather than the simple-skill exception which requires well-organized sections.	1 / 5
	Total	5 / 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.

This is an unfilled template description that provides no information about the skill's purpose, domain, or activation triggers. It fails every dimension because it is placeholder text rather than a real description.

Suggestions

Replace the placeholder with a concrete statement of what the skill does, e.g. '<action> <object> from <input> and produce <output>'.

Add an explicit 'Use when...' clause naming the natural phrases, file types, or situations that should trigger this skill.

Use third-person voice and include synonyms/file extensions users would actually say to improve trigger-term quality and distinctiveness.

Dimension	Reasoning	Score
Specificity	The description is a literal placeholder ("Replace with description of the skill and when Claude should use it.") that names no domain and lists zero concrete actions, matching the 'Entirely vague; no concrete actions' anchor.	1 / 5
Completeness	It answers neither 'what does this do' nor 'when should Claude use it' — the placeholder explicitly asks the author to supply both, matching 'Missing both what and when' rather than score 2 which requires at least a vague what or when.	1 / 5
Trigger Term Quality	No natural keywords or file extensions appear; the text is meta-instruction rather than language a user would say, fitting the 'No natural keywords' anchor and not rising to score 2 which requires at least generic keywords.	1 / 5
Distinctiveness Conflict Risk	With no domain or trigger specificity, the placeholder would conflict with virtually any skill, matching the 'Entirely generic' anchor; it cannot reach score 2's 'very broad' bar without naming a domain.	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: einverne/dotfiles
Path: claude/skills/template-skill/SKILL.md
Commit: 7d18cf4

Reviewed: 4 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.