CtrlK
BlogDocsLog inGet started
Tessl Logo

cookie-consent

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

65

Quality

78%

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

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

The content is a well-organized instruction-style overview with a clean Check/Fix/Explain/Code Review structure and an appropriate one-level-deep reference to real bundle code. It is lean and actionable, with only minor conciseness and feedback-loop gaps.

DimensionReasoningScore

Conciseness

The body is lean with terse Quick Reference bullets and assumes Claude's competence, but the opening fines sentence and light repetition between Quick Reference and Check are minor motivational padding that keeps it just below the every-token-earns-its-place anchor.

4 / 5

Actionability

Concrete instructions like 'Implement a cookie consent management platform (CMP) that blocks non-essential scripts until consent is granted' and 'Configure analytics and tracking tags to initialize only after explicit consent' give mostly executable guidance, with full code delegated to the reference rather than inlined.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sequence structures the review clearly and the Code Review section adds verification ('verify them against the effective production-like response', 'Check that tracker initialization is gated on consent'), though it lacks an explicit validate-fix-retry feedback loop.

4 / 5

Progressive Disclosure

SKILL.md is a concise overview with a single well-signaled one-level-deep reference ('see references/rule.md') that exists in the bundle, and full code/examples are appropriately split into that file, matching the clear-overview anchor.

5 / 5

Total

17

/

20

Passed

Description

78%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 is well-structured with an explicit 'Use when' trigger, clear domain, and strong completeness. It is slightly limited on specificity (one review action) and has minor overlap risk with broader privacy-review skills.

DimensionReasoningScore

Specificity

Quotes 'reviewing a website for GDPR/CCPA compliance' and 'whether cookie consent is obtained before non-essential cookies are set' name the domain plus a single concrete review action, but do not enumerate multiple distinct actions — matching the 1-2 concrete actions anchor rather than the several-actions anchor at 4.

3 / 5

Completeness

It explicitly answers both what (reviewing a website for GDPR/CCPA cookie-consent compliance) and when (leading 'Use when reviewing a website for GDPR/CCPA compliance...') with concrete trigger phrasing, matching the explicit what-and-when anchor.

5 / 5

Trigger Term Quality

Natural terms 'GDPR/CCPA compliance', 'cookie consent', and 'non-essential cookies' cover what a user would say, but common synonyms like 'cookie banner' or 'tracking cookies' are absent, so it sits at good-but-not-comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

The cookie-consent focus carves a clear niche with distinct triggers, but the broader 'GDPR/CCPA compliance' framing leaves minor overlap risk with general privacy/compliance review skills, so it is mostly distinct rather than minimal-conflict.

4 / 5

Total

16

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
thedaviddias/Front-End-Checklist
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.