totally-different-name

Valid description, but the name field does not match the parent directory name.

Quality

33%

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

Quality

Content

37%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 a terse, well-structured example demonstrating a name/directory mismatch, but it is purely descriptive—no executable guidance, no workflow, and no validation. It works as an illustration but not as actionable skill content.

Suggestions

Add a concrete action such as a command or check the user can run to detect the name/directory mismatch (e.g., a shell snippet comparing the frontmatter name to the directory).

Provide a short corrective workflow: detect the mismatch, correct the name field, then re-verify it matches the directory.

Include an explicit validation step so a reader can confirm the fix succeeded rather than only learning that a mismatch is disallowed.

Dimension	Reasoning	Score
Conciseness	The two-line body is lean with no padding or basic-concept over-explanation, but bullet 1 ('This skill's frontmatter name does not equal its directory name') restates the title, a minor instance of over-explanation that keeps it just below the 'every token earns its place' anchor.	4 / 5
Actionability	The body only states two facts ('does not equal', 'requires an exact match') with no commands, code, or concrete steps, matching the 'entirely vague or abstract; only describes rather than instructs' anchor rather than the minimal-guidance anchor above.	1 / 5
Workflow Clarity	There is no process or sequence of operations—only descriptive statements—so it matches the 'steps missing or incoherent; no sequence' anchor; the simple-skill exception does not apply because no single action is actually specified.	1 / 5
Progressive Disclosure	At under 50 lines with no bundle files present and no need for external references, the title plus numbered list is well-organized, satisfying the simple-skill exception that lets progressive disclosure score 5 on structure alone.	5 / 5
	Total	11 / 20 Passed

Description

28%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 reads as a meta-commentary about the skill's own frontmatter rather than a statement of capability, offering no trigger guidance and only a vague what. It is concise and narrowly scoped but fails as an actionable, trigger-rich skill description.

Suggestions

Rewrite the description to state the skill's actual capability in third person (e.g., 'Validates that a skill's frontmatter name matches its parent directory name').

Add an explicit 'Use when...' clause naming natural trigger phrases such as 'skill name', 'directory name mismatch', or 'agentskills spec validation'.

Replace the observational phrasing with concrete actions (e.g., 'Checks', 'Reports', 'Validates') so the description instructs rather than describes.

Dimension	Reasoning	Score
Specificity	The phrase 'name field does not match the parent directory name' names a narrow domain but describes no concrete actions the skill performs, fitting the 'names the domain but actions are minimal' anchor rather than the entirely-vague anchor below.	2 / 5
Completeness	It offers only a vague observational 'what' ('Valid description, but...') and entirely lacks any 'when to use' guidance, matching the 'vague what and no when' anchor; the missing 'Use when' clause also caps it well below 3.	2 / 5
Trigger Term Quality	It uses technical phrasing ('name field', 'parent directory name') with no natural trigger phrases a user would say, matching 'one or two generic keywords; missing the natural phrases users say' rather than the jargon-only anchor.	2 / 5
Distinctiveness Conflict Risk	The narrow name/directory-mismatch framing is a fairly distinct niche unlikely to trigger unrelated skills, but it is a metadata concern rather than a capability domain, so it sits at the 'somewhat specific but could overlap' anchor instead of 4.	3 / 5
	Total	9 / 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: saif-shines/doraval
Path: test/fixtures/skills/agentskills-name-mismatch/SKILL.md
Commit: 0fa2092

Reviewed: 1 day 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.