CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

privacy-policy

Use when reviewing whether a website has a visible, accessible privacy policy link, particularly in the footer navigation.

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/privacy-policy/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 split skill body: concise sections, concrete check/fix guidance, a clear workflow, and a clean one-level reference to a real bundle file that holds the code examples and legal detail. Remaining improvements are minor — deduplicate the Quick Reference vs Check overlap and make the verification loop explicit.

DimensionReasoningScore

Conciseness

The ~40-line body is lean with no padding over concepts Claude already knows, but there is minor duplication — 'link is present on all pages' and the retention/analytics disclosure requirement each appear in both Quick Reference and Check — matching 'efficient; minor instances that could be trimmed'. It is not 5 because that overlap is real, and not 3 because the redundancy is limited to a couple of sentences rather than several padded sections.

4 / 5

Actionability

For an instruction-only skill the guidance is concrete and specific ('Check whether the website footer contains a link…', 'Verify the linked page contains an actual privacy policy with contact information, what data is collected, and user rights', 'Add a Privacy Policy link… that appears on every page'), matching 'mostly executable guidance; minor gaps'. It is not 5 because code examples and inspection mechanics (anchor text, href, per-page verification) are deferred to the reference rather than covered inline.

4 / 5

Workflow Clarity

The Check → Fix → Explain structure gives a clear sequence, the Check section enumerates ordered verifications (footer link, linked-page content, presence on all pages, retention disclosure), and Code Review adds 'verify them against the effective production-like response' — matching 'clear sequence with most checkpoints present; minor validation gaps'. It is not 5 because there is no explicit fix-then-recheck feedback loop and the check steps are not enumerated as a numbered procedure.

4 / 5

Progressive Disclosure

The bundle structure checks out: the body is a well-organized overview (Quick Reference, Check, Fix, Explain, Code Review) ending in a clearly signaled, one-level-deep pointer — 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — and the split (summary and instructions inline; code examples and GDPR Article 13 detail in the reference, verified to exist) is appropriate, matching the top anchor.

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 tight, well-scoped description with an explicit trigger clause, natural keywords, and low conflict risk. Its main limitation is coverage: it conveys a single review action and lets the 'what' ride inside the 'Use when' clause instead of enumerating concrete capabilities.

Suggestions

State the skill's capabilities separately before the trigger, e.g. 'Checks that a privacy policy link is present in the footer of every page and that the linked page contains the required disclosures.'

Enumerate 2-3 concrete actions (verify link presence on all pages, audit policy content for required GDPR/CCPA disclosures, add a footer link) to lift specificity from one action to several.

Add a couple of natural trigger variations users might say, such as 'privacy notice', 'legal links', or 'GDPR/CCPA privacy policy check'.

DimensionReasoningScore

Specificity

The description names the domain and one concrete review action with useful specifics ("visible, accessible privacy policy link, particularly in the footer navigation"), but it lists only that single action rather than several specific actions, matching the '1-2 concrete actions, not comprehensive' anchor.

3 / 5

Completeness

An explicit 'Use when...' clause answers the 'when', and the what (reviewing for a visible, accessible privacy policy link) is concrete but only embedded inside the when-clause rather than stated separately with multiple trigger phrases, so it fits 'has both what and when; when could be more explicit or specific'.

4 / 5

Trigger Term Quality

Natural phrases a user would say for this need are present ("privacy policy", "link", "website", "footer navigation"), giving good keyword coverage, though common variations like "GDPR compliance", "legal links", or "privacy notice" are missing — matching 'good coverage; a few natural terms missing' rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

'Privacy policy link in the footer navigation' carves out a clear niche with distinct triggers that would not naturally fire adjacent skills (e.g., cookie-consent or terms-of-service checks), matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.

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

Path

skills/privacy-policy/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.