gdpr-compliance-scanner
Gdpr Compliance Scanner - Auto-activating skill for Security Advanced. Triggers on: gdpr compliance scanner, gdpr compliance scanner Part of the Security Advanced skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill gdpr-compliance-scannerOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder that provides almost no useful information for skill selection. It lacks any explanation of what the scanner actually does, what it checks for, or when it should be triggered. The repeated trigger term and boilerplate category mention offer no value for distinguishing this skill from others.
Suggestions
Add specific capabilities: describe what the scanner checks (e.g., 'Scans code and configurations for GDPR compliance issues including data retention policies, consent mechanisms, PII handling, and data subject rights implementation').
Add a 'Use when...' clause with natural trigger terms like 'GDPR audit', 'privacy compliance', 'data protection check', 'personal data handling', 'EU privacy regulations'.
Remove the redundant duplicate trigger term and replace with varied natural language users would actually say when needing GDPR compliance assistance.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - it only names the skill and mentions it's 'auto-activating' without explaining what it actually does (scan for GDPR violations, check data handling, audit privacy policies, etc.). | 1 / 3 |
Completeness | Neither 'what' nor 'when' is adequately answered. There's no explanation of capabilities and no 'Use when...' clause or equivalent guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are the skill name itself repeated twice ('gdpr compliance scanner'). Missing natural user terms like 'privacy audit', 'data protection', 'GDPR check', 'personal data', 'compliance review'. | 1 / 3 |
Distinctiveness Conflict Risk | The GDPR focus provides some specificity within security/compliance domain, but 'Security Advanced skill category' is vague and could overlap with other security or compliance scanning tools. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is a placeholder template with no actual GDPR compliance scanning content. It contains only generic boilerplate text that could apply to any skill, with no specific tools, scanning procedures, compliance checks, or actionable guidance for GDPR compliance work.
Suggestions
Add concrete scanning steps: specify tools (e.g., data discovery scripts, PII detection patterns), commands to run, and what outputs to expect
Include specific GDPR compliance checks: data inventory, consent tracking, data subject rights, breach notification requirements with executable validation code
Provide example workflows for common scenarios: scanning a codebase for PII exposure, auditing data retention policies, generating compliance reports
Add references to GDPR articles and link to detailed documentation for specific compliance areas (Article 17 right to erasure, Article 30 records of processing, etc.)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about GDPR compliance scanning. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, tools, or specific steps are provided. The skill describes what it does abstractly ('provides step-by-step guidance') without actually providing any guidance, examples, or executable instructions. | 1 / 3 |
Workflow Clarity | No workflow is defined. For a compliance scanner skill, there should be clear steps for scanning, identifying violations, generating reports, and remediation - none of which are present. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed documentation, no links to GDPR-specific resources, and no organization beyond generic section headers. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 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.