slug-keywords

Use when applies to blog posts, product pages, and any content page with editable URL slugs. Use when building a URL strategy for a new site or auditing existing URLs for keyword inclusion.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/slug-keywords/SKILL.md

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.

The body is well structured with actionable check/fix guidance and exemplary progressive disclosure to a single real reference file. Its weaknesses are mild redundancy across the intro, Quick Reference, and Explain sections, an irrelevantly padded Code Review section, and the absence of post-fix validation steps in a workflow that involves site-wide batch URL changes.

Suggestions

Add an explicit validation step to the Fix workflow (e.g., 'After deploying redirects, re-crawl the affected URLs and monitor Google Search Console for crawl errors') to create a feedback loop.

Trim redundancy: drop or merge the intro sentence and Explain section with the overlapping Quick Reference bullet.

Remove or rewrite the Code Review section's references to 'structured data, and response headers', which are not relevant to URL slug keywords.

Dimension	Reasoning	Score
Conciseness	The body is compact, but there is redundancy: the intro sentence ('Descriptive URL slugs help users and search engines understand page content before visiting') duplicates the fourth Quick Reference bullet, the Explain section restates it again, and the Code Review section's 'structured data, and response headers' are largely irrelevant to URL slugs and read as template padding.	3 / 5
Actionability	The Check section gives specific flag criteria ('numeric IDs only, random strings, session tokens, dates without a descriptive slug, or overly generic words (/page, /item, /post)') and the Fix section gives concrete remedies (lowercase hyphenated slugs, 301 redirects, update internal links, sitemaps, canonical tags). Minor gaps remain: no crawl command and no inline good/bad slug examples (deferred to the reference).	4 / 5
Workflow Clarity	The Check → Fix → Explain → Code Review sequence is present, but validation checkpoints after fixes are missing or implicit — there is no step to verify redirects, re-crawl, or confirm no ranking loss. Site-wide slug changes with 301 redirects are a batch/risky operation, so the missing feedback loop caps this dimension at 3.	3 / 5
Progressive Disclosure	The ~45-line body is well organized into clear sections (Quick Reference, Check, Fix, Explain, Code Review) and delegates full details to a single, clearly signaled, one-level-deep reference ('see references/rule.md'), which exists and does not nest further.	5 / 5
	Total	15 / 20 Passed

Description

61%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, explicit trigger guidance with natural phrasing, but it is entirely when-oriented: it never states what the skill does (checking, fixing, and explaining keyword-rich slugs) as a capability. Adding a leading capability statement would raise both completeness and specificity.

Suggestions

Prepend an explicit capability statement, e.g., 'Checks and fixes URL slugs to include the page's primary keyword... ' before the 'Use when' clauses, so the 'what' is explicit rather than implied.

Add natural synonyms such as 'permalink', 'SEO', and 'slug optimization' to the trigger coverage.

Mention the concrete outcomes the skill provides (slug rules, 301 redirect guidance, code-review checks) to make the actions more comprehensive.

Dimension	Reasoning	Score
Specificity	The description names the domain ('editable URL slugs', 'keyword inclusion', 'blog posts, product pages') and two concrete actions ('building a URL strategy for a new site', 'auditing existing URLs for keyword inclusion'), but coverage is not comprehensive — the core capability of checking and rewriting slugs is never named.	3 / 5
Completeness	Explicit 'Use when...' triggers are present ('Use when applies to blog posts...', 'Use when building a URL strategy...'), but the description is composed entirely of trigger clauses; what the skill actually does is only weakly implied via 'auditing existing URLs for keyword inclusion' rather than explicitly stated as a capability.	3 / 5
Trigger Term Quality	Good natural-language coverage: 'blog posts', 'product pages', 'editable URL slugs', 'URL strategy', 'auditing existing URLs', 'keyword inclusion'. A few common synonyms users would say are missing, such as 'permalink', 'SEO', or 'slug' on its own, so it falls short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	The niche (keyword inclusion in URL slugs) is clear and triggers are specific, but there is minor overlap risk with closely related SEO/URL skills (e.g., URL length, canonical URL, or general SEO audit skills), and 'any content page' is somewhat broad.	4 / 5
	Total	14 / 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/slug-keywords/SKILL.md
Commit: 7bfd868

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.