CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cookie-consent

Use when reviewing a website for GDPR/CCPA compliance, specifically whether cookie consent is obtained before non-essential cookies are set.

Quality

80%

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/cookie-consent/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, appropriately brief overview that follows a sound Check → Fix → Explain → Code Review flow and correctly delegates implementation detail to a real, one-level-deep reference file. The main weakness is actionability: the body tells Claude what to verify but not how, and the Fix section remains strategy-level until the reader opens the reference.

Suggestions

Add operational detail to the Check section — e.g., open DevTools Network tab, filter for gtag/gtm/analytics requests, confirm none fire before acceptance and all stop firing after revocation — so the checks are executable without opening the reference.

Trim or relocate the GDPR-fines intro paragraph; if the figures are worth keeping, fold them into the Explain section where they serve the user-facing explanation rather than motivating Claude.

Close the workflow loop explicitly: after applying the Fix, re-run the Check/Code Review verification steps, and state what to do when a tracker still fires (e.g., re-gate the tag and re-verify against the production-like response).

DimensionReasoningScore

Conciseness

The body is dense and mostly earns its tokens — the Quick Reference bullets and Check/Fix sections are tightly written. The two-sentence GDPR-fines intro ("fines up to €20 million or 4% of global annual turnover. Regulators across the EU have actively fined organizations...") is motivational padding Claude does not need and could be trimmed, matching 'efficient; minor instances of over-explanation that could be trimmed'.

4 / 5

Actionability

The Check section gives concrete behavioral checks ("analytics, advertising, and tracking scripts do not load until the user has actively accepted"; reject "without losing access to content"), but no operational detail on how to observe them (e.g., DevTools Network filtering for tracker requests), and the Fix section stays strategy-level ("Implement a cookie consent management platform (CMP)"). This matches 'some concrete guidance but incomplete; missing key details' — the executable specifics are deferred to the reference file rather than summarized, and there is no code or command in the body.

3 / 5

Workflow Clarity

A coherent sequence is present (Quick Reference → Check → Fix → Explain → Code Review) with an explicit verification checkpoint ("verify them against the effective production-like response"). Minor gaps keep it below 5: no explicit re-check-after-fix loop and no guidance on what to do when verification fails. This is a review skill, not a destructive or batch operation, so no cap applies.

4 / 5

Progressive Disclosure

A sub-50-line overview with well-organized sections and a clearly signaled one-level-deep pointer naming exactly what the reference holds ("For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`"). The referenced file exists and contains no nested references, matching the 'clear overview with well-signaled one-level-deep references' anchor.

5 / 5

Total

16

/

20

Passed

Description

82%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 strong, focused description: explicit 'Use when' trigger guidance, concrete domain and action, third-person voice, and a well-defined niche with minimal conflict risk. The only gaps are modest — a single action named rather than several, and a few missing synonyms such as 'cookie banner' or 'tracking cookies'.

DimensionReasoningScore

Specificity

Names the domain ("GDPR/CCPA compliance", "cookie consent", "non-essential cookies") and one concrete review action ("whether cookie consent is obtained before non-essential cookies are set"), matching the '1-2 concrete actions but not comprehensive' anchor. It does not list several actions, ruling out 4, and the action is specific rather than generic, ruling out 2.

3 / 5

Completeness

It explicitly answers both what ("whether cookie consent is obtained before non-essential cookies are set") and when ("Use when reviewing a website for GDPR/CCPA compliance") with concrete trigger phrases. The 'when' is more explicit than the anchor-4 example, so it fits the anchor-5 exemplar of clearly and explicitly answering both.

5 / 5

Trigger Term Quality

Natural phrases a user would say are present — "reviewing a website", "GDPR/CCPA compliance", "cookie consent" — but common variations like "cookie banner", "tracking cookies", or "privacy compliance" are missing, matching 'good keyword coverage; a few natural terms missing'.

4 / 5

Distinctiveness Conflict Risk

Clear niche (cookie consent under GDPR/CCPA for websites) with distinct, unambiguous triggers; minimal overlap risk with other skills, matching the 'clear niche with distinct triggers' anchor.

5 / 5

Total

17

/

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/cookie-consent/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.