checking-hipaa-compliance
This skill enables Claude to automatically check for HIPAA (Health Insurance Portability and Accountability Act) compliance issues in codebases, infrastructure configurations, and documentation. It leverages the hipaa-compliance-checker plugin to identify potential violations related to data privacy, security, and access controls. Use this skill when the user explicitly requests to "check HIPAA compliance", "scan for HIPAA violations", "assess HIPAA readiness", or similar phrases related to HIPAA audits and security best practices. It is useful for projects handling protected health information (PHI) and requiring adherence to HIPAA regulations.
86
48%
Does it follow best practices?
Impact
93%
1.13xAverage score across 9 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./backups/skills-migration-20251108-070147/plugins/security/hipaa-compliance-checker/skills/hipaa-compliance-checker/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels in completeness and distinctiveness, with strong trigger term coverage. Its main weakness is that the specific capabilities could be more granular—listing concrete checks performed (e.g., encryption verification, audit log checks, access control validation) rather than broad categories like 'data privacy, security, and access controls'. Minor note: the description uses 'This skill enables Claude to' which is acceptable third-person but slightly indirect.
Suggestions
Add more concrete specific actions like 'verify encryption of PHI at rest and in transit, check audit logging configurations, validate role-based access controls, scan for hardcoded credentials' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (HIPAA compliance) and some actions ('check for HIPAA compliance issues in codebases, infrastructure configurations, and documentation', 'identify potential violations related to data privacy, security, and access controls'), but doesn't list multiple concrete specific actions like 'scan encryption settings, verify access control lists, check audit logging configurations'. | 2 / 3 |
Completeness | Clearly answers both 'what' (checks for HIPAA compliance issues in codebases, infrastructure configurations, and documentation; identifies violations related to data privacy, security, and access controls) and 'when' (explicit 'Use this skill when...' clause with specific trigger phrases and context about PHI-handling projects). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'check HIPAA compliance', 'scan for HIPAA violations', 'assess HIPAA readiness', 'HIPAA audits', 'security best practices', 'protected health information (PHI)', 'HIPAA regulations'. These are terms users would naturally use when requesting this type of analysis. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche around HIPAA compliance specifically. The trigger terms are domain-specific (HIPAA, PHI, HIPAA violations) and unlikely to conflict with general security scanning or other compliance skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is essentially a marketing description rather than an actionable skill. It lacks any concrete commands, plugin invocation syntax, code examples, or executable guidance. The content is heavily padded with obvious advice and restated context that Claude already knows, while failing to provide the specific technical details needed to actually perform HIPAA compliance checks.
Suggestions
Add the actual plugin invocation syntax/command with concrete parameters (e.g., how to call hipaa-compliance-checker, what arguments it accepts, what file paths to target)
Replace the abstract examples with concrete input/output pairs showing actual plugin commands and sample report output format
Remove the 'Overview', 'When to Use', 'Best Practices', and 'Integration' sections entirely — they add no actionable information and waste tokens
Add validation/error handling steps: what to do when the plugin reports issues, how to interpret severity levels, and how to verify fixes
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and padded with information Claude already knows. The 'Overview' restates the description, 'When to Use' repeats the trigger phrases from the description, 'Best Practices' states obvious advice like 'review reports' and 'prioritize remediation', and the 'Integration' section is vague filler. Nearly every section explains concepts rather than providing actionable instructions. | 1 / 3 |
Actionability | There is no concrete, executable guidance anywhere. No actual commands, no plugin invocation syntax, no code examples, no configuration snippets. The examples describe what the skill 'will do' in abstract terms ('activate the plugin', 'scan the codebase') without showing how. There's nothing copy-paste ready or specific enough for Claude to act on. | 1 / 3 |
Workflow Clarity | The 'How It Works' section lists abstract steps ('Analyze Request', 'Initiate Plugin') without any concrete commands, validation checkpoints, or error recovery. The examples repeat the same vague pattern. There is no indication of what to do if the plugin fails, how to interpret results, or how to validate findings. | 1 / 3 |
Progressive Disclosure | The content is organized into logical sections with clear headers, which provides some structure. However, there are no references to external files, no bundle files to support deeper content, and inline content that could be trimmed is instead padded out. The organization exists but doesn't serve progressive disclosure since there's no depth to disclose. | 2 / 3 |
Total | 5 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Commit
13d35b8
- 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.