different-name

A skill with a name that doesn't match the directory.

Quality

13%

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 ./packages/coding-agent/test/fixtures/skills/name-mismatch/SKILL.md

Quality

Content

26%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 terse and unpadded but substantively empty: it states a name-mismatch fact without giving any actionable instruction or workflow. Structure is clean for its minimal size, yet actionability and workflow clarity sit at the floor.

Suggestions

Add concrete, executable guidance — e.g., a command or check to detect the mismatch (such as comparing the YAML 'name' field against the parent directory name).

Provide a short workflow with an explicit validation step (e.g., read frontmatter, compare to directory, report mismatch) so the sequence is unambiguous.

State the single intended action explicitly so the simple-skill workflow-clarity exception can apply.

Dimension	Reasoning	Score
Conciseness	The body is two short lines with no padding or over-explanation, so it is not verbose; but the tokens convey no actionable skill content, so they do not fully 'earn their place' as the score-5 anchor requires — it lands at the efficient-but-thin midpoint of 3.	3 / 5
Actionability	The body only states 'This skill's name doesn't match its parent directory.' — it describes a fact rather than instructing any concrete, executable action, matching the score-1 anchor 'Entirely vague or abstract; no concrete code or commands; only describes rather than instructs'.	1 / 5
Workflow Clarity	There is no sequence of steps and no stated action to perform, so the simple-skill exception (which requires an unambiguous single action) does not apply; this matches the score-1 anchor 'Steps missing or incoherent; no sequence'.	1 / 5
Progressive Disclosure	The skill is under 50 lines with no external references needed (no references/, scripts/, or assets/ directories exist), and it has a clear single heading with appropriately scoped one-line content — good structure for its size with only the minor gap of having nothing substantive to organize, placing it at 4 rather than 5.	4 / 5
	Total	9 / 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 meta-statement about a name mismatch rather than a description of any capability; it conveys no actions, triggers, use-conditions, or distinguishable niche. It sits at the floor of every dimension.

Suggestions

Rewrite the description to state the skill's actual capability in third person (e.g., 'Detects and reports when a skill's name frontmatter differs from its parent directory').

Add a 'Use when...' clause naming the concrete trigger condition so the 'when' is explicit.

Include a natural trigger term a user would actually say (e.g., 'skill name mismatch', 'name does not match directory').

Dimension	Reasoning	Score
Specificity	The description 'A skill with a name that doesn't match the directory' names no concrete actions or capabilities whatsoever — it only states a meta-fact about the skill's naming, matching the score-1 anchor 'Entirely vague; no concrete actions; pure abstract language'.	1 / 5
Completeness	It answers neither 'what does this do' (no capability is described) nor 'when should Claude use it' (no 'Use when...' trigger), matching the score-1 anchor 'Missing both what and when'. The missing trigger clause would cap completeness at 3, but here both are absent so it falls to 1.	1 / 5
Trigger Term Quality	There are no natural keywords a user would say to invoke this skill; the phrase describes a structural defect rather than a task, matching the score-1 anchor of only generic/technical language with no natural user phrases.	1 / 5
Distinctiveness Conflict Risk	The statement is entirely generic meta-commentary with no niche or distinct trigger, so it would conflict with any skill, matching the score-1 anchor 'Entirely generic; would conflict with virtually any skill'.	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: can1357/oh-my-pi
Path: packages/coding-agent/test/fixtures/skills/name-mismatch/SKILL.md
Commit: cabfa74

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.