CtrlK
BlogDocsLog inGet started
Tessl Logo

third-party-cookies

Use when reviewing a website for privacy compliance, third-party resource loading, or cookie consent implementation.

60

Quality

70%

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/third-party-cookies/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 review skill with clear progressive disclosure to a real reference file; main weakness is mild over-explanation of background context Claude already knows.

Suggestions

Trim the introductory paragraph and Quick Reference facts that restate what third-party cookies are and generic GDPR penalty figures.

Make the verify checkpoint explicit as its own numbered step rather than embedding it in the Code Review prose.

DimensionReasoningScore

Conciseness

Mostly efficient with clear sections, but the intro and Quick Reference explain context Claude largely already knows (e.g. what third-party cookies do, the 4% GDPR penalty), which could be trimmed.

3 / 5

Actionability

Provides concrete, executable guidance — specific DevTools panels (Network, Application > Cookies), concrete identification steps, and specific remediation actions — with only minor gaps in the Fix section.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections give a clear sequence, and Code Review includes a verify step ('verify them against the effective production-like response'), though other checkpoints are implicit.

4 / 5

Progressive Disclosure

The body is a well-organized overview (Quick Reference, Check, Fix, Explain, Code Review) with a clearly signaled one-level-deep pointer to references/rule.md, which exists and holds the detailed implementation material.

5 / 5

Total

16

/

20

Passed

Description

70%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 solid 'Use when...' description with concrete triggers and a clear niche, but it describes one review action across multiple targets rather than multiple distinct capabilities.

Suggestions

Add 1-2 more concrete verbs beyond 'reviewing' (e.g. 'Audits, flags, and reports') to lift specificity.

Include the natural term 'third-party cookies' explicitly since it is the skill's primary subject.

DimensionReasoningScore

Specificity

Names the domain (privacy compliance, third-party resource loading, cookie consent) and the concrete action 'reviewing a website', but the only verb is 'reviewing' applied to several targets rather than a comprehensive list of distinct actions.

3 / 5

Completeness

Explicitly answers both 'what' (reviewing a website for privacy compliance, third-party resource loading, cookie consent) and 'when' ('Use when...') with concrete trigger phrases, but the 'what' is a single review action whose scope could be more specific.

4 / 5

Trigger Term Quality

Includes natural phrases users would say ('privacy compliance', 'third-party resource loading', 'cookie consent implementation') with good coverage, though a few common synonyms (e.g. 'third-party cookies', 'tracking') are missing.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (third-party cookies / privacy compliance) with distinct triggers and minimal overlap risk, though it sits close to broader privacy-auditing skills.

4 / 5

Total

15

/

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.