parameters

Use when auditing URL structure or configuring search engine handling of filtered, sorted, or tracked URLs. Applies to e-commerce sites, filtered content directories, and any site appending tracking or session parameters.

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

Quality

Content

53%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, readable audit skill that uses progressive disclosure effectively to defer code examples to references/rule.md. It is held back by an explanatory "Explain" section that restates known concepts, overlap between the Check and Code Review sections, and absent validation checkpoints in the body.

Suggestions

Cut or trim the "Explain" section, which re-teaches crawl budget and PageRank concepts Claude already knows and duplicates the intro.

Merge the near-duplicate "Check" and "Code Review" sections into one audit checklist to remove redundancy.

Surface an explicit verify step in the body (e.g., re-crawl a representative URL set and confirm the canonical tag resolves) rather than leaving all validation in references/rule.md.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient but includes unnecessary explanation (the "Explain" section restates crawl-budget/PageRank concepts Claude already knows and echoes the intro) and notable redundancy between the "Check" and "Code Review" sections, which describe nearly the same audit steps.	3 / 5
Actionability	Guidance is concrete in places ("Strip tracking parameters (utm_*, fbclid, gclid)", "canonicalize to the base URL or self-canonicalize") but several directives stay high-level ("review for potential crawl budget waste", "Identify URLs with 3+ parameters and review") and the executable code lives only in references/rule.md, leaving key implementation details out of the body.	3 / 5
Workflow Clarity	A rough sequence exists (Check → Fix → Explain → Code Review) but there are no explicit validation checkpoints or feedback loops in the body; the verification steps that do exist are buried in references/rule.md rather than surfaced here.	3 / 5
Progressive Disclosure	Content is well organized into clear sections and points cleanly to a single one-level-deep reference ("see references/rule.md") that is a real file, matching the 4 anchor; it stops short of 5 only because the body carries some inline redundancy (Check vs Code Review) that could itself be split out.	4 / 5
	Total	13 / 20 Passed

Description

70%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 solid, trigger-rich description that clearly signals when to use the skill and names a specific SEO niche. Its main weakness is that the stated actions (auditing, configuring handling) are slightly generic and the "what" is not crisply separated from the "when".

Suggestions

Lead with concrete verbs that describe specific outputs (e.g., "Audit URL parameters and configure canonical tags to consolidate filtered, sorted, and tracked URL variants") to lift specificity.

Separate the "what" from the "when": state the capability in one sentence, then the "Use when..." trigger in another, to make completeness unambiguous.

Dimension	Reasoning	Score
Specificity	The description names the domain ("auditing URL structure or configuring search engine handling of filtered, sorted, or tracked URLs") with a couple of concrete actions, but those actions ("auditing", "configuring handling") remain fairly high-level and not comprehensive, fitting the 3 anchor better than 4.	3 / 5
Completeness	It explicitly answers "when" ("Use when auditing URL structure or configuring...") and includes a "what" (auditing/configuring parameter handling), but the what is somewhat blended into the when clause and could be crisper, so it sits just below the 5 anchor.	4 / 5
Trigger Term Quality	Strong natural keyword coverage ("URL parameters", "filtered, sorted, or tracked URLs", "e-commerce sites", "tracking or session parameters") that users would plausibly say, with only minor synonyms/extensions missing, landing above the 3 anchor.	4 / 5
Distinctiveness Conflict Risk	It carves a clear niche (URL-parameter / canonical handling for e-commerce and filtered directories) with distinct triggers, though the opening "auditing URL structure" phrasing is broad enough to risk minor overlap with general SEO/URL skills.	4 / 5
	Total	15 / 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/parameters/SKILL.md
Commit: 30756a7

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