gdpr-data-handling

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

Quality

27%

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

18%Scale 1-5

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

This skill is essentially a hollow template with no actionable GDPR-specific content. The instructions are generic boilerplate that could apply to any domain, and all substantive guidance is deferred to a referenced file that doesn't exist in the bundle. For a topic as complex and consequential as GDPR data handling, the skill needs concrete implementation patterns, code examples, validation steps, and specific workflows for consent management and data subject requests.

Suggestions

Add concrete, executable code examples for key GDPR operations: consent recording, data subject access request handling, data deletion/anonymization with validation steps.

Replace the generic instruction bullets with GDPR-specific workflows — e.g., a numbered sequence for processing a DSR with validation checkpoints (verify identity, locate data, confirm deletion, audit log).

Either provide the referenced `resources/implementation-playbook.md` bundle file or inline the essential patterns directly in the SKILL.md body.

Add specific data structures or schemas for consent records, processing logs, and DPIA templates rather than abstract descriptions.

Dimension	Reasoning	Score
Conciseness	The content is relatively short but includes some unnecessary filler like the generic 'Do not use this skill when' section and the overly vague instructions that don't add GDPR-specific value. The instructions read like generic skill boilerplate rather than domain-specific guidance.	3 / 5
Actionability	The instructions are entirely vague and abstract — 'Clarify goals, constraints, and required inputs' and 'Apply relevant best practices' provide zero concrete guidance on GDPR implementation. There are no code examples, no specific commands, no concrete steps for consent management, DSR handling, or any of the listed use cases. Everything is deferred to a bundle file that doesn't exist.	1 / 5
Workflow Clarity	There is no meaningful workflow defined. The four bullet points under Instructions are generic platitudes with no sequencing, no validation checkpoints, and no specific steps for any GDPR process. Data handling operations (especially deletion/anonymization) are destructive and require validation steps, which are completely absent.	1 / 5
Progressive Disclosure	The skill references `resources/implementation-playbook.md` for detailed patterns, which is a reasonable structure in theory, but the bundle file doesn't exist. The SKILL.md itself contains almost no substantive content, making it an empty shell that delegates everything to a missing file. The reference is clear but the content split is dysfunctional.	2 / 5
	Total	7 / 20 Passed

Description

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

The description identifies a clear domain (GDPR compliance) but remains at a high level without specifying concrete actions or providing trigger guidance for when Claude should select this skill. The terms used are relevant but lack the specificity and comprehensiveness needed for reliable skill selection among many options.

Suggestions

Add a 'Use when...' clause with explicit trigger phrases like 'Use when the user asks about GDPR compliance, data protection regulations, cookie consent, privacy policies, data subject access requests (DSARs), or right to erasure.'

Replace broad category names with concrete actions, e.g., 'Generates privacy policies, implements cookie consent banners, drafts DSAR response templates, audits data processing activities for GDPR compliance.'

Include common synonyms and related terms users might naturally say, such as 'data protection', 'EU privacy law', 'personal data', 'right to be forgotten', and 'data breach notification'.

Dimension	Reasoning	Score
Specificity	Names the domain (GDPR compliance) and mentions broad areas like 'data processing', 'consent management', and 'privacy controls', but these are high-level categories rather than concrete actions. No specific actions like 'generate privacy policies', 'audit data flows', or 'create consent forms' are listed.	2 / 5
Completeness	Provides a vague 'what' (implementation guide for GDPR-compliant data processing, consent management, privacy controls) but has no 'when' clause at all. There is no explicit trigger guidance for when Claude should select this skill, which per the rubric should cap completeness at 3, and the weak 'what' brings it to 2.	2 / 5
Trigger Term Quality	Includes relevant keywords like 'GDPR', 'data processing', 'consent management', and 'privacy controls' that users might mention. However, it misses common synonyms and related terms like 'data protection', 'right to be forgotten', 'DSAR', 'cookie consent', 'privacy policy', or 'personal data'.	3 / 5
Distinctiveness Conflict Risk	The GDPR focus provides some distinctiveness, but 'data processing' and 'privacy controls' are broad enough to overlap with general security, compliance, or data engineering skills. The description could conflict with other privacy or compliance-related skills.	3 / 5
	Total	10 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/gdpr-data-handling/SKILL.md
Commit: 57c135b

Reviewed: 4 days ago

Table of Contents

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.