length

Use when generating URL slugs from article titles, auditing URL structures for unnecessary depth or length, or reviewing URL patterns in a CMS or router configuration.

Quality

68%

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

Quality

Content

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

A well-structured, actionable overview that appropriately defers code and detail to a real one-level reference. Its main weaknesses are intro/Explain redundancy and a lack of explicit validation checkpoints around the risky URL-change/redirect workflow.

Suggestions

Add a validation step to the Fix workflow, e.g. 'Verify old URLs return 301s and check Google Search Console for crawl errors after deployment' — this also lifts the workflow_clarity cap.

Trim redundancy between the intro and 'Explain' sections and drop the John Mueller attribution to tighten token efficiency.

Surface the references/rule.md pointer earlier (e.g. a one-line 'See references/rule.md for executable slug-generation code' near Quick Reference) rather than only at the very end.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with sectioned, dense guidance, but the intro and 'Explain' sections overlap (both cover truncation, readability, crawl distance) and the John Mueller name-drop is padding Claude doesn't need, fitting 'mostly efficient but could be tightened' over anchor 4.	3 / 5
Actionability	Provides concrete thresholds (100 chars, 4 segments), a specific stop-word list, and before/after URL examples plus a sequenced Fix list; executable code is deferred to the reference, which is appropriate for an instruction/review skill, leaving only minor gaps.	4 / 5
Workflow Clarity	The Fix section is sequenced (1–6) but URL changes with 301 redirects are a batch/risky operation with no explicit validation checkpoint (no 'verify redirects resolve', 'check crawl errors'), so per the destructive/batch cap workflow clarity cannot exceed 3.	3 / 5
Progressive Disclosure	The body is a well-organized overview with a single, clearly signaled one-level-deep pointer to references/rule.md (verified to exist), but the reference is surfaced only at the very end rather than navigated inline, keeping it just below anchor 5.	4 / 5
	Total	14 / 20 Passed

Description

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

A strong, trigger-first description with concrete actions and natural keywords covering URL slug generation and structure auditing. The what and when are both present, though tightly merged into a single 'Use when ...' clause.

Dimension	Reasoning	Score
Specificity	Names several concrete actions — 'generating URL slugs from article titles', 'auditing URL structures for unnecessary depth or length', 'reviewing URL patterns in a CMS or router configuration' — matching the 'several specific actions; minor gaps' anchor rather than 5's fully comprehensive coverage.	4 / 5
Completeness	The 'Use when ...' clause gives an explicit trigger, and the embedded actions state what the skill does; both what and when are present, though the what is folded into the when clause rather than stated separately as in anchor 5.	4 / 5
Trigger Term Quality	Includes natural phrases users would say ('URL slugs', 'article titles', 'URL structures', 'URL patterns', 'CMS', 'router configuration'), giving good keyword coverage with a few synonyms missing, fitting anchor 4 over the comprehensive anchor 5.	4 / 5
Distinctiveness Conflict Risk	It carves a clear niche around URL length/depth/slug structure with distinct triggers, but could overlap with adjacent SEO slug skills (stop-words, lowercase), matching 'mostly distinct; minor overlap risk' rather than anchor 5.	4 / 5
	Total	16 / 20 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/length/SKILL.md
Commit: 30756a7

Reviewed: 26 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.