CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

54

Quality

61%

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 ./skills/length/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 with excellent progressive disclosure to a single real reference file. The main weaknesses are duplicated criteria across Quick Reference/Check/Explain (token waste) and a missing validation/verification step in the URL-change workflow, which the rubric caps at 3 given the batch nature of site-wide URL restructuring.

Suggestions

Add a verification step to the Fix workflow: after implementing 301 redirects, verify each old URL returns a 301, confirm sitemaps and internal links resolve, and check crawl errors before considering the change complete.

Consolidate the duplicated criteria: merge the Quick Reference bullets into the Check section (or vice versa) and trim the Explain section to only Google-specific guidance not already stated.

Define how to distinguish evergreen from dated content (the one criterion left implicit), so the date-removal step is unambiguous.

DimensionReasoningScore

Conciseness

The body is mostly on-point, but the Quick Reference bullets, the Check criteria, and the Explain section repeat the same points (100-char limit, segment count, stop words, shareability), and appeals like 'Google's John Mueller has confirmed' add rationale Claude largely already knows. It is not 2 because there is no generic primer material and the document is short; it is not 4 because the duplication between three sections is real trimming opportunity.

3 / 5

Actionability

Concrete, executable guidance throughout: exact thresholds ('Path length over 100 characters', 'More than 4 path segments'), an enumerated stop-word list, and before/after fix examples ('/a-comprehensive-guide-to-css-grid-layout' → '/css-grid-guide'). It is not 5 because no code or command is included in the body and some criteria are left to judgment (e.g., what counts as 'evergreen content'); it is well above 3's pseudocode level.

4 / 5

Workflow Clarity

The Check → Fix sequence is well-ordered with numbered remediation steps, but site-wide URL restructuring is a batch/risky operation and there is no validation or verification step (e.g., test that 301 redirects resolve, verify sitemaps/internal links, monitor crawl errors). Per the rubric's cap for batch operations without validation, workflow clarity cannot exceed 3; it is not 2 because the sequence itself is clear and complete.

3 / 5

Progressive Disclosure

The body is a lean overview with well-labeled sections and a clear one-level-deep pointer at the end ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md'), and the referenced file exists with no further nesting. Content is appropriately split between overview and detail, matching the anchor-5 example structure; no organization gaps found.

5 / 5

Total

15

/

20

Passed

Description

57%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 has strong, specific trigger phrasing with natural keywords, but it consists solely of 'Use when...' conditions and never says what the skill actually does. Adding a leading capability statement (e.g., 'Flags and shortens overly long or deeply nested URLs') would lift completeness significantly.

Suggestions

Add a leading 'what' statement before the trigger clause, e.g. 'Flags and fixes overly long or deeply nested URLs by shortening slugs and flattening paths. Use when...'.

Include common trigger synonyms such as 'permalinks', 'clean URLs', or 'shorten URLs' to broaden natural keyword coverage.

State the skill's output explicitly (audit findings, remediation steps, 301 redirect guidance) so users know what result to expect.

DimensionReasoningScore

Specificity

Lists three concrete action phrases ('generating URL slugs from article titles', 'auditing URL structures for unnecessary depth or length', 'reviewing URL patterns in a CMS or router configuration'), so it sits at anchor 4 rather than anchor 3's '1-2 concrete actions'. It falls short of 5 because it never states the skill's actual capability or outcome (e.g., flagging and shortening overlong URLs), leaving minor gaps in coverage.

4 / 5

Completeness

The description is entirely a 'Use when...' trigger clause with no statement of what the skill does, matching anchor 2 ('only when is present without what', e.g. 'Use when working with documents'). It is not 3 because anchor 3 requires a clear 'what', which is absent; it is not 1 because the 'when' is specific rather than vague.

2 / 5

Trigger Term Quality

Includes natural phrases users would say — 'URL slugs', 'article titles', 'CMS', 'router configuration', 'URL patterns' — giving good keyword coverage. It is not 5 because common variations like 'permalinks', 'clean URLs', 'shorten URLs', 'slugify', or 'SEO' are missing.

4 / 5

Distinctiveness Conflict Risk

URL slug generation and structure auditing is a fairly distinct niche, but 'generating URL slugs' and stop-word/length guidance overlaps with closely related slug-hygiene and SEO skills. Minor overlap risk with sibling rules keeps it at 4 rather than a clear-niche 5.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
thedaviddias/Front-End-Checklist
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.