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

70%

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

71%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, appropriately brief body that keeps code in a real one-level-deep reference file and gives concrete audit/fix criteria (named tracking parameters, a 3+ parameter threshold). The notable defect is the near-duplicate 'Check' and 'Code Review' sections, which waste tokens without adding guidance, and the absence of a post-fix validation step.

Suggestions

Merge the 'Check' and 'Code Review' sections — they repeat the same enumeration, canonical-tag check, and tracking-parameter verification; one consolidated section would save tokens without losing guidance.

Add a short validation step after 'Fix' (e.g., re-verify that each parameterized URL's canonical tag excludes tracking parameters and points to the intended base URL).

Include one inline canonical-tag example so the fix pattern is usable without opening the reference file.

Dimension	Reasoning	Score
Conciseness	Mostly efficient, but the 'Check' and 'Code Review' sections substantially duplicate each other (both enumerate parameter patterns, check for canonical tags, and verify tracking parameters are stripped). Not 2 because there is no padded explanation of concepts Claude already knows — the redundancy is the only tightening needed.	3 / 5
Actionability	Concrete, specific guidance throughout: 'Strip tracking parameters (utm_*, fbclid, gclid)', 'Identify URLs with 3+ parameters', 'canonicalize to the base URL or self-canonicalize consistently'. Code examples are appropriately deferred to the verified references/rule.md, so this instruction-only skill only misses a minor inline canonical-tag example.	4 / 5
Workflow Clarity	Clear Check -> Fix -> Explain sequence for a single audit task, with concrete criteria at each step. Not 5 because there is no post-fix verification checkpoint (e.g., re-check that canonical tags are present and correct after applying fixes). The destructive/batch cap does not apply since this is a read-only audit workflow.	4 / 5
Progressive Disclosure	A lean ~33-line overview with clear section headers, and a well-signaled one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — file verified to exist) that carries the code examples. This is the ideal split for a simple skill.	5 / 5
	Total	16 / 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 description with an explicit 'Use when...' trigger, a defined niche, and good natural keywords for e-commerce and directory sites. Its main weakness is that the 'what' is thin — two abstract actions with no mention of concrete outputs like canonical tags or parameter stripping — and it could add the most common synonyms such as 'URL parameters' and 'duplicate content'.

Suggestions

Add the concrete actions the skill performs (e.g., 'check canonical tags on parameterized URLs and strip tracking parameters (utm_*, fbclid, gclid)') to raise specificity.

Include the most natural trigger phrases users would say: 'URL parameters', 'duplicate content', 'canonical tags', 'crawl budget'.

State the 'what' as a separate clause before the 'Use when...' trigger so both parts are independently explicit.

Dimension	Reasoning	Score
Specificity	Names the domain (URL parameters / search engine handling) with two concrete actions ('auditing URL structure', 'configuring search engine handling of filtered, sorted, or tracked URLs'), but coverage is not comprehensive. Matches anchor 3 rather than 4 because the actions are few and somewhat abstract, with no mention of the concrete outputs (canonical tags, parameter stripping).	3 / 5
Completeness	Both what (audit URL structure / configure search engine handling) and when ('Use when auditing... or configuring...') are present and explicit. Not 5 because what and when are fused into a single sentence rather than clearly separated with concrete trigger phrases; not 3 because neither element is missing or vague.	4 / 5
Trigger Term Quality	Good natural keyword coverage: 'filtered, sorted, or tracked URLs', 'e-commerce sites', 'filtered content directories', 'tracking or session parameters'. Not 5 because common variations users would say ('URL parameters', 'duplicate content', 'canonical', 'utm') are missing.	4 / 5
Distinctiveness Conflict Risk	Clear niche (URL parameter handling for SEO) with distinct triggers ('filtered, sorted, or tracked URLs', 'tracking or session parameters'). Minor overlap risk with closely related SEO skills such as a canonical-url skill, matching anchor 4 rather than 5.	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: 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.