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.

67

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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 review skill that uses progressive disclosure effectively to defer code examples to a real reference file. The main gaps are a duplicated background paragraph hurting conciseness and implicit rather than explicit validation checkpoints in the review workflow.

Suggestions

Remove or trim the opening GDPR fines paragraph in the body since the same text appears in references/rule.md, keeping the body focused on what to do.

Add an explicit verification checkpoint to the Code Review section (e.g., 'After flagging a violation, confirm the tracker no longer initializes on reload and that a persistent cookie-settings control exists').

Consider adding one minimal inline code snippet showing consent-gated script loading so the body is self-sufficient for the most common case before deferring to the reference.

DimensionReasoningScore

Conciseness

The body is mostly lean with well-organized Quick Reference, Check, Fix, Explain, and Code Review sections, but the opening fines paragraph ('fines up to €20 million or 4% of global annual turnover') is background padding that is duplicated verbatim in references/rule.md and could be tightened.

2 / 3

Actionability

Gives concrete, specific instructions such as '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', which are directly actionable even without inline code.

3 / 3

Workflow Clarity

The Check → Fix → Explain → Code Review sections provide a recognizable sequence, but validation checkpoints are only implicit ('verify them against the effective production-like response') rather than explicit validate-fix-retry feedback loops, which caps this at the mid anchor.

2 / 3

Progressive Disclosure

The body is a concise overview with clearly signaled one-level-deep navigation ('see references/rule.md'), and the referenced file exists in the bundle, giving easy navigation without nested reference chains.

3 / 3

Total

10

/

12

Passed

Description

90%

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, well-targeted description with an explicit 'Use when' trigger and natural keywords. Its only weakness is specificity, since it describes one focused action rather than a list of several concrete capabilities.

DimensionReasoningScore

Specificity

Names a concrete domain ('reviewing a website for GDPR/CCPA compliance') and a specific action ('whether cookie consent is obtained before non-essential cookies are set'), but does not enumerate multiple distinct concrete actions, so it stops short of the top anchor.

2 / 3

Completeness

Explicitly states what the skill does ('reviewing... whether cookie consent is obtained before non-essential cookies are set') and when to use it ('Use when reviewing a website for GDPR/CCPA compliance'), answering both what and when with an explicit trigger.

3 / 3

Trigger Term Quality

Includes natural terms a user would actually say — 'cookie consent', 'GDPR/CCPA compliance', 'non-essential cookies' — giving good coverage rather than technical jargon.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (cookie consent under GDPR/CCPA) with distinct triggers, making it unlikely to fire for unrelated privacy or general review skills.

3 / 3

Total

11

/

12

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.