CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

different-name

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

24

Quality

31%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

30%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-minimal but substantively empty: it states that a name mismatch exists without telling Claude what to do about it (detect, fix, or report). Actionability and workflow clarity are at the floor because there is no instruction or process, and progressive disclosure is unremarkable since there is nothing to disclose. The content needs at minimum a statement of the task and one concrete action or validation step.

Suggestions

State the skill's actual task and the concrete action to take, e.g. 'When a skill's frontmatter name differs from its directory name, rename the directory to match the frontmatter name' — this alone would lift actionability off the floor.

Add a minimal validation step such as re-reading the frontmatter after the rename to confirm the match, giving the workflow at least one checkpoint.

If the skill is genuinely this simple, one well-organized section explaining what to do (rather than the fact that a mismatch exists) would let the simple-skill exception apply to workflow clarity.

DimensionReasoningScore

Conciseness

The body ('# Name Mismatch' plus one sentence) is maximally lean with zero over-explanation of concepts Claude already knows. It falls short of 5 only because the single sentence 'This skill's name doesn't match its parent directory' is a packaging fact rather than guidance, so it doesn't fully earn its place in the context window.

4 / 5

Actionability

'This skill's name doesn't match its parent directory' only describes a state; there is no instruction, command, code, or concrete guidance of any kind, matching the 'Entirely vague or abstract; only describes rather than instructs' anchor. Score 2 is excluded because even a high-level hint of what to do about the mismatch is missing.

1 / 5

Workflow Clarity

There are no steps, no sequence, and no task at all — the 'Steps missing or incoherent' anchor. The simple-skill exception cannot lift this because it requires a single unambiguous action, and the body contains no action whatsoever.

1 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), so there are no references to verify and no nested-reference risk. The body has a heading and a single sentence, which is trivially organized but carries no content to structure — best fitting 'some structure' rather than the 5-anchor's well-organized sections with real content.

3 / 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 describes the skill's packaging (a name/directory mismatch) rather than any capability, so it provides no information about what the skill does or when to use it. It matches the rubric's bad-overall pattern of vague, action-free descriptions like 'Helps with documents', but is even less informative since it names no domain at all. A complete rewrite stating concrete actions and explicit 'Use when...' triggers is needed.

Suggestions

Replace the meta-statement with concrete capability verbs, e.g. 'Validates that a skill's frontmatter name matches its directory name and reports mismatches' — name 1-2 specific actions so specificity can clear the lowest anchor.

Add an explicit trigger clause such as 'Use when creating or reviewing skills, or when renaming a skill directory' so completeness includes both 'what' and 'when'.

Include natural trigger terms users would actually say (e.g. 'skill name', 'directory mismatch', 'SKILL.md', 'rename skill') so the description is discoverable and distinguishable from other skill-authoring tools.

DimensionReasoningScore

Specificity

The description 'A skill with a name that doesn't match the directory' names no action and no domain of work — it is a meta-statement about the skill's packaging, matching the 'Entirely vague; no concrete actions' anchor. It cannot score 2 because even a generic action verb like 'Processes PDF files' is absent.

1 / 5

Completeness

Neither 'what does this do' nor 'when should Claude use it' is addressed — the sentence describes the skill's file layout, not a capability, and there is no 'Use when...' clause. This matches the 'missing both what and when' anchor.

1 / 5

Trigger Term Quality

There are no task-related keywords of any kind; no user request would naturally contain these words. Score 2 is excluded because it requires at least one or two generic task keywords, and none are present.

1 / 5

Distinctiveness Conflict Risk

With no capability or domain information, the description is entirely generic and indistinguishable from any other skill, fitting the 'would conflict with virtually any skill' anchor. Score 2 requires at least a broad domain claim, which is not present.

1 / 5

Total

4

/

20

Passed

Validation

100%

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

Kiz8-Team/pi-cwl

Path

packages/coding-agent/test/fixtures/skills/name-mismatch/SKILL.md

Reviewed

Table of Contents

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.