scanning-for-gdpr-compliance
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill scanning-for-gdpr-complianceThis skill enables Claude to scan applications and data systems for GDPR compliance issues. It identifies potential violations related to data protection, privacy rights, consent management, and other regulatory requirements. Use this skill when the user asks to "scan for GDPR compliance", check "GDPR compliance", or audit for "data privacy". The skill leverages the `gdpr-compliance-scanner` plugin to perform a comprehensive assessment and generate a detailed report.
Validation
81%| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 13 / 16 Passed | |
Implementation
20%This skill content is overly descriptive and lacks actionable, executable guidance. It explains concepts and workflows at a high level but never provides the concrete plugin invocation syntax, parameters, or output schemas that Claude would need to actually perform the task. The content reads more like marketing copy than technical instruction.
Suggestions
Add concrete plugin invocation syntax showing exact command/function calls with parameters (e.g., `gdpr-compliance-scanner.scan(target='./app', scope=['data-collection', 'consent'])`)
Include an example of the actual report output format (JSON schema or sample output) so Claude knows what to expect and how to interpret results
Remove the 'Overview', 'How It Works', and 'When to Use This Skill' sections - this information is redundant with the skill description and wastes tokens
Add error handling guidance: what errors might occur, how to diagnose them, and recovery steps
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Highly verbose with unnecessary explanations Claude already knows (what GDPR is, why compliance matters). The 'How It Works' section describes obvious steps, and 'When to Use This Skill' repeats information from the description. Much of this content adds no actionable value. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance provided. The skill describes what will happen abstractly ('activate the plugin', 'generate a report') but never shows actual plugin invocation syntax, parameters, or expected output formats. | 1 / 3 |
Workflow Clarity | Steps are listed in sequence but lack validation checkpoints or error handling. No guidance on what to do if the scan fails, how to interpret specific error codes, or how to verify the report is complete and accurate. | 2 / 3 |
Progressive Disclosure | Content is organized into sections but everything is inline in one file. The 'Integration' section hints at connections to other tools but provides no references. For a skill of this length, the structure is adequate but could benefit from linking to detailed plugin documentation or example reports. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
90%This is a well-structured skill description that excels in completeness and trigger term quality with an explicit 'Use this skill when...' clause containing natural user phrases. The main weakness is that the capabilities listed are somewhat categorical (data protection, privacy rights) rather than listing specific concrete actions the skill performs. The description effectively distinguishes itself through its GDPR-specific focus.
Suggestions
Replace categorical terms like 'data protection, privacy rights, consent management' with specific concrete actions such as 'validate consent forms, check data retention policies, verify right-to-erasure compliance, audit data processing agreements'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (GDPR compliance) and lists some actions (scan, identify violations, generate report), but the specific capabilities like 'data protection, privacy rights, consent management' are categories rather than concrete actions like 'check consent forms' or 'audit data retention policies'. | 2 / 3 |
Completeness | Clearly answers both what (scan applications and data systems for GDPR compliance issues, identify violations, generate detailed report) and when (explicit 'Use this skill when...' clause with specific trigger phrases). | 3 / 3 |
Trigger Term Quality | Includes good natural trigger terms users would say: 'scan for GDPR compliance', 'check GDPR compliance', 'audit for data privacy'. These are realistic phrases users would naturally use when needing this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Has a clear niche focused specifically on GDPR compliance scanning with distinct triggers like 'GDPR compliance' and 'data privacy audit'. Unlikely to conflict with general security or document processing skills due to the specific regulatory focus. | 3 / 3 |
Total | 11 / 12 Passed |
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.