Tessl • The package manager for agent skills

Blog Docs Log inGet started

SkillPublic

gdpr-data-handling

Practical implementation guide for GDPR-compliant data processing, consent management, and privacy controls.

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/gdpr-data-handling/SKILL.md

The canonical home for this skill is gdpr-data-handling in rmyndharis/antigravity-skills

Quality

Content

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

The body is lean and well-sectioned but nearly empty of substance: instructions are generic boilerplate rather than actionable GDPR guidance, there is no concrete workflow, and the single referenced resource file is missing from the bundle. The skill reads as a template skeleton rather than a usable implementation guide.

Suggestions

Replace the generic instruction bullets with concrete GDPR guidance, e.g., a DSR intake-to-response workflow, consent-record data model, and lawful-basis checklist.

Fix or remove the dangling reference: `resources/implementation-playbook.md` is cited twice but does not exist in the bundle.

Delete the tautological 'Do not use this skill when the task is unrelated to gdpr data handling' section and instead fold the trigger list into the description's Use-when guidance.

Dimension	Reasoning	Score
Conciseness	The body is short and free of concept-explanation padding, but the generic instruction bullets ("Clarify goals, constraints, and required inputs") and the tautological "Do not use when the task is unrelated to gdpr data handling" section are filler that could be trimmed. This matches anchor 3: mostly efficient with some unnecessary content.	3 / 5
Actionability	The Instructions section is placeholder-level generic ("Apply relevant best practices and validate outcomes") with no concrete GDPR guidance — no consent-record patterns, DSR handling steps, or retention rules. The only concrete pointer, "open resources/implementation-playbook.md", targets a file that does not exist in the bundle. This matches anchor 2: high-level hints missing the specific steps to execute.	2 / 5
Workflow Clarity	The bullets imply a rough generic sequence (clarify goals, apply best practices, validate) but contain no GDPR-specific steps, no sequencing of a real workflow, and no validation checkpoints for risky operations like data deletion or batch erasure. This matches anchor 2: rough sequence with many gaps and no real validation.	2 / 5
Progressive Disclosure	Sections are clearly labeled and the reference to `resources/implementation-playbook.md` is signaled one level deep under Resources. However, that file does not exist anywhere in the bundle, making it a dangling reference that breaks navigation — more than the minor organization gaps of anchor 4, so it lands at anchor 3.	3 / 5
	Total	10 / 20 Passed

Description

61%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 reasonably specific, distinct description that clearly states what the skill covers, but it omits any "when to use" trigger guidance and lacks common synonym terms users might say. Adding an explicit trigger clause with variations (data protection, right to erasure, DSRs) would raise both completeness and trigger quality.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when building systems that process EU personal data, implementing consent flows, or handling data subject requests').

Include common synonyms users naturally say: 'GDPR compliance', 'data protection', 'right to be forgotten / erasure', 'data subject requests (DSRs)'.

Replace the generic 'Practical implementation guide' framing with concrete actions such as 'Implement consent records, retention policies, and DSR workflows'.

Dimension	Reasoning	Score
Specificity	The description names the GDPR domain and enumerates three sub-areas ("data processing, consent management, and privacy controls"), but "Practical implementation guide" is generic with no concrete action verbs. It sits above anchor 2 (purely generic actions) thanks to the enumerated scope, but below anchor 4 which requires several specific actions.	3 / 5
Completeness	The "what" is clearly stated (implementation guide for GDPR-compliant processing, consent, privacy controls) but the description contains no "Use when..." clause or equivalent trigger guidance, capping completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	"GDPR", "consent management", "privacy controls", and "data processing" are natural phrases users would say when needing this skill. It falls short of anchor 5 because common variations like "data protection", "right to be forgotten", or "data subject requests" are absent.	4 / 5
Distinctiveness Conflict Risk	GDPR is a well-defined niche with distinct triggers, giving minimal conflict risk. It is not a 5 because "privacy controls" and "data processing" have some overlap with general privacy or security-architecture skills.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/gdpr-data-handling/SKILL.md
Revision: 64adc55

Reviewed: 20 hours ago

Discovery Implementation Validation

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.

gdpr-data-handling

Table of Contents

Is this your skill?