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

72%

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

72%

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

The body is concise and well-structured with clean progressive disclosure to a real reference file, but its workflow omits an explicit post-fix verification checkpoint and the body itself carries no executable code or examples.

Suggestions

Add an explicit verification step in the main workflow (e.g. after Fix: 'Verify redirects resolve (200/301) and re-crawl affected URLs before sign-off') to close the feedback loop for batch/destructive changes.

Inline at least one minimal executable example (e.g. a shell command to find numeric-ID URLs) so the body is copy-paste ready rather than deferring all code to the reference.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence — each section (Quick Reference, Check, Fix, Explain, Code Review) is terse with no padding or explanation of concepts Claude already knows, so every token earns its place.	3 / 3
Actionability	Guidance is concrete ('Crawl the site and examine URL paths. Flag URLs that contain...', 'Set up 301 redirects from old URLs to new slugs') but there is no executable code or copy-paste example in the body itself — those are deferred to references/rule.md, leaving key details inline-incomplete.	2 / 3
Workflow Clarity	The Check → Fix → Explain → Code Review sequence is present, but the main flow lacks an explicit verify-after-fix checkpoint; because this involves batch/destructive operations (site crawl, rewriting slugs, 301 redirects), the missing feedback loop caps workflow clarity per the rubric's destructive-operation note.	2 / 3
Progressive Disclosure	The skill is under 50 lines with well-organized sections and a single clearly-signaled one-level-deep reference to references/rule.md (verified to exist), so navigation is clean and content is appropriately split.	3 / 3
	Total	10 / 12 Passed

Description

72%

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 trigger-term coverage and a distinct niche, but its capability statement is weak — the 'Use when applies to' phrasing never names what the skill actually does, leaving the 'what' only implied.

Suggestions

Add an explicit capability verb, e.g. 'Audits and rewrites URL slugs to include target keywords' before the trigger clause.

Fix the grammatically awkward 'Use when applies to blog posts' phrasing to a natural trigger such as 'Use when working with blog posts, product pages, or any page with editable URL slugs'.

Dimension	Reasoning	Score
Specificity	It names the domain ('blog posts, product pages, and any content page with editable URL slugs') but never states concrete actions verbs, using the awkward 'applies to' phrasing rather than naming what the skill does, matching 'Names domain and some actions, but not comprehensive.'	2 / 3
Completeness	It has explicit 'when' triggers but the 'what does this do' is only implied (no verb like 'check' or 'fix' is stated), so it does not clearly answer both what AND when; the odd 'Use when applies to' phrasing weakens the capability statement.	2 / 3
Trigger Term Quality	Natural user-facing terms are well covered — 'blog posts', 'product pages', 'URL slugs', 'URL strategy', 'auditing existing URLs', 'keyword inclusion' — the kind of phrases a user would actually say.	3 / 3
Distinctiveness Conflict Risk	The niche is specific (editable URL slugs and keyword inclusion in URLs) with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 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/slug-keywords/SKILL.md
Commit: 48405aa

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