hipaa-audit-helper
Hipaa Audit Helper - Auto-activating skill for Security Advanced. Triggers on: hipaa audit helper, hipaa audit helper Part of the Security Advanced skill category.
32
0%
Does it follow best practices?
Impact
89%
0.91xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/04-security-advanced/hipaa-audit-helper/SKILL.mdQuality
Discovery
0%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 description is essentially a placeholder that provides no meaningful information about the skill's capabilities, use cases, or triggers. It merely restates the skill name and category without any concrete actions, natural trigger terms, or explicit guidance on when to use it. This would be nearly useless for Claude to select appropriately from a pool of available skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates HIPAA compliance checklists, reviews security controls against HIPAA requirements, identifies PHI handling gaps, and produces audit-ready documentation.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user mentions HIPAA compliance, healthcare security audits, PHI protection, protected health information, HIPAA risk assessment, or compliance review.'
Remove the redundant duplicate trigger term ('hipaa audit helper' listed twice) and replace with varied natural language terms users would actually use when requesting this type of help.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only states the skill name and category ('Security Advanced') without describing what the skill actually does—no verbs like 'analyze', 'generate', 'check', or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause or equivalent guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'hipaa audit helper' repeated twice. These are not natural keywords a user would say; a user is more likely to say 'HIPAA compliance', 'audit checklist', 'PHI', 'security assessment', 'compliance review', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is too vague to be distinctive. 'Security Advanced' category and 'hipaa audit helper' name provide minimal differentiation. Without specific capabilities described, it could easily conflict with any other security or compliance-related skill. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty placeholder with no substantive content. It contains only generic boilerplate that repeats the skill name without providing any actual HIPAA audit guidance, compliance checklists, specific controls (e.g., the HIPAA Security Rule safeguards), or actionable procedures. It fails on every dimension of the rubric.
Suggestions
Add concrete HIPAA audit content: list the specific safeguards (Administrative, Physical, Technical) from the HIPAA Security Rule with actionable checklist items for each.
Provide executable examples such as scripts for scanning configurations, generating audit reports, or validating compliance evidence against specific HIPAA controls (e.g., 164.312 access controls).
Define a clear multi-step audit workflow with validation checkpoints, e.g., 1) Scope assessment, 2) Evidence collection, 3) Gap analysis, 4) Remediation tracking, 5) Report generation.
Replace the generic trigger/capability boilerplate with domain-specific content—reference frameworks like NIST SP 800-66 and link to supporting files for detailed control mappings.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'hipaa audit helper' excessively, and provides zero domain-specific information about HIPAA auditing, compliance checks, or security procedures. | 1 / 3 |
Actionability | There are no concrete steps, commands, code examples, checklists, or specific HIPAA controls referenced. The skill describes what it claims to do in abstract terms but provides absolutely no executable or actionable guidance. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, no validation checkpoints. For a compliance audit skill—where structured checklists and verification steps are critical—this is a complete miss. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to supporting files, no links to HIPAA control frameworks, no structured navigation. There are no bundle files to support it either. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- 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.