CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/parameters/SKILL.md
SKILL.md
Quality
Evals
Security

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, actionable audit skill with a clean overview-to-reference split and explicit checkpoints in the Check phase. Its main weaknesses are redundancy between the Check and Code Review sections and the Explain section re-covering the intro, plus the absence of any post-fix verification step.

Suggestions

Merge or differentiate the Check and Code Review sections — they currently repeat the same identify/check/verify instructions almost verbatim.

Trim the Explain section, which restates the intro's duplicate-content/crawl-budget rationale, or fold its one non-redundant point into the intro.

Add a short post-fix verification step (e.g., re-crawl affected URL variants or confirm canonical tags resolve to the preferred URL) to close the workflow's validation gap.

DimensionReasoningScore

Conciseness

Individual sections are tight, but "Code Review" repeats nearly the same instructions as "Check", and "Explain" re-states the intro's duplicate-content/crawl-budget points — mostly efficient with unnecessary duplication that could be tightened. Not a 2, since no section explains background concepts at padding length.

3 / 5

Actionability

Gives concrete parameter lists (utm_*, fbclid, gclid, page, sort), a literal example URL (?color=red&size=large&sort=price&utm_source=google), a 3+ parameter threshold, and specific directives (add canonical tags to the parameter-free URL, self-canonicalize consistently). Minor gap: no inline canonical-tag example, which is deferred to references/rule.md, so not a 5.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sequence is coherent, and Check includes explicit checkpoints ("check whether the page has a canonical tag", "verify that tracking-only parameters are excluded", "identify URLs with 3+ parameters and review"). A minor gap: no post-fix re-validation step, so not a 5; checkpoints are explicit rather than implicit, so above 3.

4 / 5

Progressive Disclosure

A short, well-sectioned overview body with a clearly signaled one-level-deep pointer to the real references/rule.md file for "full implementation details, code examples, and framework-specific guidance". Content is appropriately split and easy to navigate, matching the top anchor.

5 / 5

Total

16

/

20

Passed

Description

53%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.

The description has a strong, explicit trigger clause with a well-defined niche, but it is entirely when-oriented: the skill's concrete capabilities (e.g., canonicalizing parameter variants, stripping tracking parameters) are never stated, and natural trigger terms like "URL parameters", "query strings", and "canonical" are missing.

Suggestions

Lead with a what-clause stating concrete actions, e.g., "Audits URL parameters and configures canonical tags to consolidate filtered, sorted, and tracked URL variants."

Add natural trigger keywords users would actually say — "URL parameters", "query strings", "canonical tags", "duplicate content", "crawl budget" — to the Use-when clause.

Mention the deliverable (an audit report of parameter handling with canonical-tag recommendations) so the what is explicit rather than implied.

DimensionReasoningScore

Specificity

Names the domain and 1-2 actions ("auditing URL structure", "configuring search engine handling") but lists no concrete operations such as adding canonical tags or stripping tracking parameters. It is not several specific actions (4) nor merely a domain name with generic verbs (2).

3 / 5

Completeness

The "when" is explicit and well-scoped ("Use when auditing URL structure or configuring search engine handling..."), but the "what" — what the skill actually does — is only weakly implied through the trigger verbs rather than stated. Anchor 4 requires both explicitly; anchor 2 fits only when no what is conveyed at all, and the verbs do convey some.

3 / 5

Trigger Term Quality

Includes some natural terms ("filtered, sorted, or tracked URLs", "tracking or session parameters", "e-commerce sites") but misses common variations users would say, such as "URL parameters" as a unit, "query strings", "canonical", or "duplicate content". Coverage is present but not comprehensive enough for 4.

3 / 5

Distinctiveness Conflict Risk

Niche triggers around parameter handling on filtered/sorted/tracked URLs and e-commerce sites make it mostly distinct, with only minor overlap risk against closely related SEO skills (canonical tags, duplicate content). Not a 5 because those sibling-SEO overlaps remain plausible.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/parameters/SKILL.md

Reviewed

Table of Contents

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.