scanning-for-data-privacy-issues
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill scanning-for-data-privacy-issuesThis skill enables Claude to automatically scan code and configuration files for potential data privacy vulnerabilities using the data-privacy-scanner plugin. It identifies sensitive data exposure, compliance violations, and other privacy-related risks. Use this skill when the user requests to "scan for data privacy issues", "check privacy compliance", "find PII leaks", "identify GDPR violations", or needs a "privacy audit" of their codebase. The skill is most effective when used on projects involving personal data, financial information, or health records.
Validation
69%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 11 / 16 Passed | |
Implementation
20%This skill content is overly descriptive and lacks actionable guidance. It explains what the data-privacy-scanner plugin conceptually does but never shows how to actually use it - no commands, no code examples, no output formats. The content reads more like marketing copy than executable instructions for Claude.
Suggestions
Add concrete command syntax or API calls showing exactly how to invoke the data-privacy-scanner plugin (e.g., `mcp__data_privacy_scanner__scan(path="./src", rules=["gdpr", "pii"])`)
Include an example of actual plugin output/report format so Claude knows what to expect and how to interpret results
Remove the 'How It Works', 'When to Use This Skill', and 'Integration' sections - this context is already in the skill description and wastes tokens
Add validation steps: what to do if the scan fails, how to verify the plugin is available, how to handle partial results
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Verbose and padded with unnecessary explanations. Sections like 'How It Works', 'When to Use This Skill', and 'Integration' explain concepts Claude already knows or repeat information from the description. The examples describe what will happen rather than showing concrete usage. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance provided. The skill describes what the plugin does abstractly but never shows how to actually invoke it - no command syntax, no API calls, no configuration examples. | 1 / 3 |
Workflow Clarity | Steps are listed in a logical sequence (initiate, analyze, report), but there are no validation checkpoints, no error handling guidance, and no concrete details about what the plugin commands or outputs look like. | 2 / 3 |
Progressive Disclosure | Content is organized into sections with headers, but it's a monolithic document with no references to external files. The 'Integration' section hints at advanced usage but provides no links or concrete guidance. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
100%This is a well-crafted skill description that excels across all dimensions. It provides specific capabilities, includes natural trigger terms users would actually say, explicitly states both what the skill does and when to use it, and carves out a distinct niche in data privacy scanning that won't conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'scan code and configuration files', 'identifies sensitive data exposure', 'compliance violations', and 'privacy-related risks'. Also specifies the tool used (data-privacy-scanner plugin). | 3 / 3 |
Completeness | Clearly answers both what (scan code for privacy vulnerabilities, identify sensitive data exposure, compliance violations) AND when (explicit 'Use this skill when...' clause with specific trigger phrases, plus context about project types). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'scan for data privacy issues', 'check privacy compliance', 'find PII leaks', 'identify GDPR violations', 'privacy audit'. These are realistic phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on data privacy scanning with distinct triggers like 'PII leaks', 'GDPR violations', 'privacy audit'. Unlikely to conflict with general security or code analysis skills due to the specific privacy focus. | 3 / 3 |
Total | 12 / 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.