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

64%

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

57%

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

The skill is well-structured with good progressive disclosure — a lean overview pointing to a real reference file — but the body is held back by redundant Check/Code Review sections, a restated-concepts Explain block, and a workflow that lacks any verification checkpoint for a batch audit.

Suggestions

Merge the near-duplicate "Check" and "Code Review" sections into one, and trim the "Explain" section to avoid re-teaching crawl budget / duplicate content.

Add a concrete verification step to the workflow, e.g. after adding canonical tags, confirm resolution via the URL Inspection tool or a fetched-header check.

Include at least one executable artifact inline — a sample `<link rel="canonical">` tag or a parameter-stripping snippet — so the guidance is copy-paste ready, not just directional.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient but redundant — the "Check" and "Code Review" sections repeat the same enumerate/verify/count guidance, and the "Explain" section re-states concepts (crawl budget, duplicate content, PageRank dilution) that an SEO-aware Claude already knows.	2 / 3
Actionability	It gives concrete direction with named parameters (utm_*, fbclid, gclid, page, sort) and named actions, but provides no executable artifact inline (no canonical-tag markup, no parameter-stripping method) and defers all implementation to the reference, leaving key details missing.	2 / 3
Workflow Clarity	A loose Check→Fix sequence is present, but there are no validation or verification checkpoints, and for a batch site-wide audit the rubric caps workflow clarity at 2 in the absence of a verify step.	2 / 3
Progressive Disclosure	The SKILL.md is a concise overview that clearly signals a single one-level-deep reference ("see references/rule.md"), which exists in the bundle, giving well-organized navigation with no nesting.	3 / 3
	Total	9 / 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, explicit trigger guidance and a distinct niche, but its capability statement is thin and fused into the "Use when" clause rather than standing on its own. It reads more as a trigger context than a crisp what-it-does declaration.

Suggestions

Lead with a concrete capability clause before the trigger, e.g. "Consolidates URL parameter variants under canonical tags to preserve crawl budget and PageRank. Use when…".

Name the concrete actions the skill performs (strip tracking parameters, set canonical tags, audit crawl budget) instead of the generic "auditing URL structure / configuring search engine handling".

Add the symptom terms users actually mention ("duplicate content," "canonical tags," "crawl budget") so the trigger terms match real phrasings.

Dimension	Reasoning	Score
Specificity	The description names the domain and a couple of actions ("auditing URL structure or configuring search engine handling"), but it is not a comprehensive list of concrete actions — it omits the actual substance like canonical consolidation or parameter stripping.	2 / 3
Completeness	The "when" is explicit ("Use when auditing URL structure…"), but the "what" is only fused into the trigger clause rather than stated as a standalone capability, so it does not clearly answer both halves like the level-3 anchor.	2 / 3
Trigger Term Quality	It covers a good spread of natural terms a user would say — "URL parameters," "filtered," "sorted," "tracked URLs," "e-commerce sites," and "tracking or session parameters" — matching the level-3 anchor for natural-term coverage.	3 / 3
Distinctiveness Conflict Risk	It carves a clear niche (SEO URL-parameter handling for filtered/sorted/tracked URLs and e-commerce) with distinct triggers, making it unlikely to fire for an unrelated skill.	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/parameters/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.