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.

64

Quality

76%

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.

A well-structured, appropriately concise review skill that defers implementation detail to a real, clearly signaled reference file. Its concrete verification guidance makes it actionable; the only notable gaps are a high-level Fix section without body-level code and the absence of a post-fix re-validation loop.

DimensionReasoningScore

Conciseness

The body is mostly lean with well-organized sections; the one dispensable piece is the opening fine-amounts paragraph ('fines up to €20 million or 4% of global annual turnover'), which is context Claude already knows. Not a 5 due to that padding; not a 3 because everything else earns its place.

4 / 5

Actionability

As an instruction-only skill the guidance is concrete: specific verifiable behaviors ('Verify that analytics, advertising, and tracking scripts do not load until the user has actively accepted', 'verify them against the effective production-like response'). Not a 5 because the Fix section stays high-level ('Implement a cookie consent management platform (CMP)') with no code in the body.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sequence is coherent for a review skill, and an explicit verification checkpoint exists ('verify them against the effective production-like response'). Not a 5 because there is no re-validation loop after applying fixes; not a 3 because verification is explicit rather than implicit.

4 / 5

Progressive Disclosure

The body is a clear overview with well-signaled, one-level-deep references: 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — and that file exists in the bundle with the deferred code examples (255 lines). Content is appropriately split between overview and reference.

5 / 5

Total

17

/

20

Passed

Description

73%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 focused, well-triggered description with a clear niche and explicit 'Use when' guidance. Its main weakness is that it conveys a single embedded action rather than a concrete list of capabilities, and it misses natural trigger synonyms like 'cookie banner' or 'consent notice'.

Suggestions

State the concrete actions the skill performs (e.g., 'Audit websites for consent-before-tracking violations, flag non-compliant scripts and cookies, and recommend consent-gated fixes') before the 'Use when' clause to lift specificity beyond one embedded action.

Add natural trigger variations users actually say, such as 'cookie banner', 'consent notice', 'consent banner', or 'tracking cookies', to broaden keyword coverage toward the top anchor.

DimensionReasoningScore

Specificity

The description names the domain ('GDPR/CCPA compliance', 'cookie consent') and one concrete action ('whether cookie consent is obtained before non-essential cookies are set'), but does not list several specific actions. It matches 'names domain and 1-2 concrete actions' better than anchor 4, which expects multiple specific actions listed.

3 / 5

Completeness

An explicit 'Use when...' clause is present, and the 'what' (reviewing whether cookie consent is obtained before non-essential cookies are set) is discernible. It falls short of anchor 5 because the 'what' is embedded inside the when-clause rather than clearly stated as a separate capability list.

4 / 5

Trigger Term Quality

Includes natural trigger terms users would say — 'GDPR', 'CCPA', 'cookie consent', 'non-essential cookies' — giving good keyword coverage. Not a 5 because common variations like 'cookie banner', 'consent notice', or 'tracking cookies' are absent.

4 / 5

Distinctiveness Conflict Risk

A clear niche — cookie consent compliance under GDPR/CCPA — with distinct trigger phrases unlikely to fire for unrelated skills. Overlap with generic privacy or compliance skills is minimal because the triggers are specific to cookies and consent.

5 / 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.

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