CtrlK
BlogDocsLog inGet started
Tessl Logo

privacy-policy

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

61

Quality

72%

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

70%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, simple review skill with clear sequencing and a clean one-level-deep reference that exists and carries the detail. It loses points on conciseness for restating familiar privacy-law context and on actionability because the executable code is deferred entirely to the reference.

Suggestions

Trim the regulatory recital and restate-from-knowledge Quick Reference bullets to raise conciseness; Claude already knows GDPR/CCPA basics.

Inline at least one minimal concrete artifact (e.g., a footer snippet or the crawlable URL paths) so the body is actionable without opening the reference.

DimensionReasoningScore

Conciseness

The body is lean with terse Check/Fix/Explain/Code Review sections, but the opening GDPR/CCPA/PIPEDA recital and several Quick Reference bullets restate general privacy-law knowledge Claude already has.

2 / 3

Actionability

Check and Fix give specific, checkable guidance (link text 'Privacy Policy', present on all pages, retention disclosure), but the executable code/commands live only in the reference rather than the body, so it is not copy-paste ready on its own.

2 / 3

Workflow Clarity

A simple single-purpose review skill with a clear, well-organized Check -> Fix -> Explain -> Code Review flow; no destructive or batch operation applies that would require an explicit validation checkpoint.

3 / 3

Progressive Disclosure

The body is a concise overview that signals exactly one one-level-deep reference (references/rule.md), which exists and holds the deeper code examples, GDPR Article 13 table, and verification steps.

3 / 3

Total

10

/

12

Passed

Description

75%

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 clear, well-triggered description that distinguishes a narrow privacy niche and answers both what and when. It is held back by a single abstract action verb and limited coverage of natural term variations.

Suggestions

Add concrete actions beyond 'reviewing', e.g. 'audit footer links, verify the linked policy content, and confirm placement on every page' to lift specificity.

Broaden trigger terms to include common variations users say: 'privacy notice', 'GDPR/CCPA compliance', 'privacy link', 'legal footer'.

DimensionReasoningScore

Specificity

Names a concrete domain (privacy policy link review) and locus (footer navigation) but offers only one action verb ('reviewing whether...') rather than multiple specific concrete actions.

2 / 3

Completeness

Opens with an explicit 'Use when reviewing whether...' clause that states both the action (what) and the trigger condition (when), satisfying the explicit-trigger requirement.

3 / 3

Trigger Term Quality

Includes natural terms a user would say ('privacy policy', 'footer navigation') but misses common variations like 'privacy notice', 'GDPR', 'privacy link', or 'legal link'.

2 / 3

Distinctiveness Conflict Risk

The narrow niche of footer privacy-policy link visibility has distinct triggers and is unlikely to overlap with unrelated skills.

3 / 3

Total

10

/

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.