hyphens

Use when auditing URL structures for word separator format, generating slugs from titles, or planning a URL migration from underscores or spaces to hyphens with appropriate redirects.

Quality

70%

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 ./skills/hyphens/SKILL.md

Quality

Content

57%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Well-structured with a clear, signaled reference file, but the body carries redundant concept explanations and an incomplete inline snippet, and its migration workflow lacks the validation checkpoint that a batch URL change requires.

Suggestions

Remove the '## Explain' section (it duplicates the intro) and trim '## Code Review' (it restates '## Check') to eliminate redundancy and respect the token budget.

Add a verification step to the '## Fix' migration workflow — e.g., confirm old URLs return 301, crawl for 404s, monitor Search Console — surfacing the verification content that already lives in references/rule.md.

Make the inline slug snippet complete (add .trim() and leading/trailing-hyphen stripping) or point readers to the full toSlug function in references/rule.md instead of a partial fragment.

Dimension	Reasoning	Score
Conciseness	The intro explains a concept Claude already knows ('Google's search systems interpret hyphens in URLs as word boundaries...'), and the '## Explain' section restates the same hyphens-vs-underscores point while '## Code Review' largely rephrases '## Check'; not a 1 because Check/Fix are concrete and useful, not a 3 because the redundancy and concept explanation could be cut.	2 / 3
Actionability	Provides concrete flagging rules ('Underscores (_)... Spaces encoded as %20 or +... Mixed separators') and a 7-step Fix with an executable slug snippet, but the inline snippet is a minimal fragment missing trim/edge-case handling and the complete examples are deferred to the reference, so it is not fully copy-paste ready inline.	2 / 3
Workflow Clarity	The Fix section is a clearly sequenced 7-step migration workflow, but it has no validation/verification checkpoint (e.g., confirm 301s resolve, check for 404s) for what is a batch/destructive URL change; per the rubric, missing feedback loops in such operations caps this at 2.	2 / 3
Progressive Disclosure	An organized overview body signals a single one-level-deep reference — 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' (verified to exist) — with detailed code appropriately split into that file; not a 2 because the reference is clearly signaled and one level deep rather than buried or nested.	3 / 3
	Total	9 / 12 Passed

Description

82%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, well-triggered description occupying a clear niche, but it merges the capability statement into the 'Use when' clauses instead of leading with an explicit 'what this does' statement as the reference examples do.

Suggestions

Lead with a concise capability statement (e.g., 'Audits URL word separators and generates hyphenated slugs.') before the 'Use when' trigger so the 'what' is explicit and separate from the 'when'.

Replace the jargon phrase 'word separator format' with a more natural term a user would say, such as 'hyphens vs underscores in URLs'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'auditing URL structures for word separator format, generating slugs from titles, or planning a URL migration from underscores or spaces to hyphens with appropriate redirects' — matching the anchor for several specific concrete actions; not a 2 because it goes beyond naming a domain to enumerating distinct activities.	3 / 3
Completeness	The 'Use when...' trigger is explicit and strong, but the description lacks a standalone capability statement — the 'what' is folded into the trigger clauses rather than stated independently, so unlike the reference examples (which lead with a capability then 'Use when'), it does not cleanly answer 'what does this do' as a distinct claim.	2 / 3
Trigger Term Quality	Covers natural terms users would say — 'URL migration', 'slugs', 'hyphens', 'underscores', 'redirects' — giving good coverage despite the slightly jargon-y 'word separator format'; not a 2 because the natural-term spread is broad rather than sparse.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (URL word-separator format / slug generation / underscore-to-hyphen migration with redirects) with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/hyphens/SKILL.md
Commit: 48405aa

Reviewed: about 13 hours 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.