CtrlK
BlogDocsLog inGet started
Tessl Logo

different-name

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

28

Quality

19%

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

33%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 contains no actionable instruction, code, or workflow — it merely asserts a naming fact, so it fails on actionability and workflow clarity despite being well-structured.

Suggestions

Add the concrete steps or code the skill is meant to execute, or explicit guidance Claude can follow.

If the skill genuinely performs a task, document a clear sequenced workflow with any needed validation checkpoints.

If the skill is intentionally a stub, state its purpose and intended use so the body conveys actionable direction.

DimensionReasoningScore

Conciseness

The two-line body is lean with no padding or over-explanation of concepts Claude already knows; it is efficient, though the brevity carries little actionable weight.

4 / 5

Actionability

The body only states that "This skill's name doesn't match its parent directory"; it offers no concrete code, commands, or executable guidance whatsoever.

1 / 5

Workflow Clarity

There is no sequence of steps, no action to perform, and no validation; the simple-skill exception does not apply because no unambiguous single action is described.

1 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references and is organized under a clear heading; structure is good though the content is trivially thin.

4 / 5

Total

10

/

20

Passed

Description

5%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 self-referential statement about a naming quirk rather than a capability description; it fails to convey what the skill does, when to use it, or how it differs from others.

Suggestions

Replace the description with the concrete actions the skill performs (e.g., 'Extracts text and tables from PDF files, fills forms, merges documents').

Add an explicit 'Use when...' clause naming the natural trigger phrases and file types a user would mention.

Use third-person action verbs describing capabilities rather than describing the skill's own metadata.

DimensionReasoningScore

Specificity

The phrase "A skill with a name that doesn't match the directory" names a concept (name/directory matching) but provides zero concrete capabilities or actions, landing between entirely vague and minimal-domain.

2 / 5

Completeness

It states neither what the skill does nor when Claude should use it; the description only describes a property of the skill itself, missing both the 'what' and the 'when'.

1 / 5

Trigger Term Quality

No natural trigger keywords a user would actually say; "name that doesn't match the directory" is a self-descriptive quirk rather than a phrase users utter when they need a skill.

1 / 5

Distinctiveness Conflict Risk

The description is entirely generic about the skill's own metadata; it conveys no niche or trigger, so it cannot be distinguished from or avoid conflicting with any other skill.

1 / 5

Total

5

/

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
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.