trailing-slash

Use when applies to all static and dynamic websites. Use when auditing a site for duplicate content, setting up a new site, or after migrating platforms that changed URL conventions.

Quality

61%

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/trailing-slash/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 a well-structured, actionable overview that uses progressive disclosure effectively, delegating executable framework code to a real one-level reference. Its main weaknesses are a slightly redundant concept-explaining intro and an implicit (reference-only) post-fix verification step in the audit workflow.

Suggestions

Trim or remove the opening paragraph that re-explains duplicate content and PageRank splitting, since that concept is covered in references/rule.md and is already familiar.

Add an explicit post-fix verification step to the body (e.g. "After applying redirects, re-test both slash variants to confirm one returns 301 and the other 200, and re-crawl the affected URL set") rather than leaving it only in the reference.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with a tight Quick Reference and short Check/Fix sections, but the opening paragraph re-explains the duplicate-content/PageRank concept Claude already knows and overlaps with the same explanation in references/rule.md, so it could be tightened.	2 / 3
Actionability	For an instruction/audit skill the guidance is concrete and specific — test that both slash variants do not return HTTP 200 with one 301-redirecting, enforce one convention, update links/sitemap/canonical tags — and references/rule.md supplies copy-paste executable code (Next.js, Nginx, Apache, curl, canonical HTML).	3 / 3
Workflow Clarity	The Check → Fix sequence is clear and well-organized, but the body itself lacks an explicit post-fix validation/re-verification checkpoint for this batch URL-auditing task; that verification step lives only in the reference rather than the body workflow.	2 / 3
Progressive Disclosure	The body is a concise overview split into clear sections with a single, well-signaled one-level-deep reference ("see references/rule.md"), and the referenced file exists in the bundle, giving easy navigation without nested references.	3 / 3
	Total	10 / 12 Passed

Description

50%

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 but is weakened by a grammatically broken opening clause ("Use when applies to..."), the absence of the skill's defining term "trailing slash", and a missing concrete "what" statement. It lands in the middle of the scale across all dimensions.

Suggestions

Add a concrete "what" statement before the triggers, e.g. "Enforces consistent trailing slash usage across a site to prevent duplicate-content and canonicalization issues."

Include the core natural trigger term "trailing slash" plus "canonical tags" and "301 redirects", which are currently absent despite being the skill's subject.

Fix the broken leading clause "Use when applies to all static and dynamic websites" into a grammatical trigger such as "Use when auditing or configuring any static or dynamic website."

Dimension	Reasoning	Score
Specificity	It names the domain ("all static and dynamic websites", "duplicate content", "URL conventions") and trigger scenarios ("auditing", "setting up", "migrating platforms"), but lists no concrete actions the skill performs such as enforcing redirects or setting canonical tags.	2 / 3
Completeness	The explicit "Use when..." clause answers "when" clearly, but the "what" is only weakly implied by "applies to all static and dynamic websites" and never states the actual capability (enforcing consistent trailing slash usage), so it cannot reach 3.	2 / 3
Trigger Term Quality	Natural SEO terms like "duplicate content", "setting up a new site", and "migrating platforms" are present, but the core term "trailing slash" is entirely absent, alongside missing common variations like "canonical" and "301 redirect".	2 / 3
Distinctiveness Conflict Risk	It is anchored to a specific SEO/URL niche, but because "trailing slash" is not named and "auditing a site for duplicate content" is broad, it could overlap with adjacent canonical-tag or redirect SEO skills.	2 / 3
	Total	8 / 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/trailing-slash/SKILL.md
Commit: 48405aa

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