CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

hipaa-audit

Audit applications and infrastructure handling Protected Health Information against HIPAA — Security Rule (administrative, physical, technical safeguards), Privacy Rule, Breach Notification Rule, plus HITECH. Covers ePHI scoping, the 18 HIPAA identifiers, Business Associate Agreement (BAA) chain-of-liability, minimum-necessary standard, and breach notification timing. Use when the user mentions 'HIPAA,' 'HIPAA Security Rule,' 'HIPAA Privacy Rule,' 'PHI,' 'ePHI,' 'protected health information,' 'BAA,' 'business associate agreement,' 'covered entity,' 'business associate,' 'minimum necessary,' 'HIPAA breach,' 'HITECH,' 'healthcare compliance,' 'medical data,' 'patient data,' or audits any system that creates, receives, maintains, or transmits PHI.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The operational core is excellent: concrete commands, code-level finding examples, a rigorous verdict/refutation protocol, and a working validator pipeline make this highly actionable with clear validation checkpoints. The main cost is token weight — a few hundred lines of regulatory reference material Claude largely already knows sits inline alongside the audit-specific content that earns its place.

Suggestions

Compress the regulatory background Claude already knows — the 18-item identifier list, the §164.308/§164.310 subsection enumerations, and the Privacy Rule/HITECH explanation paragraphs — to one-line pointers, keeping only the audit-specific hooks ('Engineering audit input', grep patterns).

Move the ~90-line report template out of SKILL.md into a references file (e.g. references/report-template.md), leaving a short inline summary of the sections it must contain.

State the end-to-end audit sequence explicitly near the top (establish scope and entity type → ePHI inventory → rule-by-rule examination → candidate findings → refutation pass → record and validate → render report) so the workflow order is not inferred from section order.

DimensionReasoningScore

Conciseness

Sizable stretches restate regulatory background Claude already knows — the full 18-item identifier list, "Covered entity (CE) — health plans, healthcare clearinghouses...", "HITECH (2009) strengthened HIPAA in several ways... (was previously CE-only)", and "The Security Rule says 'protect it'; the Privacy Rule says..." — while the operational core (grep patterns, verdict protocol, fingerprints) is dense and earns its tokens. This matches anchor 3 (mostly efficient but could be tightened) rather than 4, because the known-concept explanation exceeds 'minor instances'; it is not 2, since no section is padded fluff and most enumerations carry audit-specific hooks.

3 / 5

Actionability

Fully executable, copy-paste-ready guidance throughout: a complete AWS CLI check ("aws rds describe-db-instances --query 'DBInstances[].[DBInstanceIdentifier,StorageEncrypted,KmsKeyId]' --output text"), validator commands ("node references/validate-findings.mjs findings.json"), concrete code ("analytics.track(\"appointment_booked\", { email, diagnosis })"), grep patterns ("SELECT \*.*patient"), fingerprint examples, and an ext-fields table. Specific examples cover the common cases via the 'Common audit findings' list, exactly the 5 anchor; 4 would require missing key details, and none are evident.

5 / 5

Workflow Clarity

The record/validate/report tail is explicitly sequenced with feedback loops ("Validate it and fix every error") and a pre-confirmation refutation pass ("run the refutation pass in references/verification.md before anything is confirmed"), plus checklists for scope, privacy, and breach readiness. However, the end-to-end audit order (scope → examine → verify → record → report) must be inferred from section order rather than stated as an explicit sequence — the 'minor gaps' of anchor 4, short of anchor 5's fully explicit numbered workflow.

4 / 5

Progressive Disclosure

Bundle structure is strong: six real, one-level-deep reference files (findings-format.md, verification.md, severity-calibration.md, findings.schema.json, validate-findings.mjs, to-sarif.mjs), each clearly signaled at its point of need in the body. But substantial reference-style content is inlined in SKILL.md — the 18-identifier enumeration, the §164.308/§164.310 subsection lists, and the ~90-line report template — which anchor 4 treats as minor organization gaps rather than anchor 5's 'content appropriately split'.

4 / 5

Total

16

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A model trigger-rich description: it explicitly states what the skill does and when to use it, covers synonyms and a behavioral trigger comprehensively, and is dense with specifics rather than padding. All four dimensions sit at their top anchors.

DimensionReasoningScore

Specificity

"Audit applications and infrastructure handling Protected Health Information against HIPAA — Security Rule (administrative, physical, technical safeguards), Privacy Rule, Breach Notification Rule, plus HITECH" names the domain and enumerates concrete capabilities ("ePHI scoping, the 18 HIPAA identifiers, ... chain-of-liability, minimum-necessary standard, and breach notification timing") with no coverage gaps across the domain. This matches anchor 5; 4 would require a missing capability, and none is evident.

5 / 5

Completeness

Explicitly answers what ("Audit applications and infrastructure handling Protected Health Information against HIPAA...") and when (an explicit "Use when the user mentions [17 concrete trigger phrases] or audits any system that..." clause). This is exactly anchor 5's structure; 4 would require the 'when' to be less explicit or missing concrete phrases.

5 / 5

Trigger Term Quality

Seventeen quoted natural trigger terms with synonyms covered ("'PHI,' 'ePHI,' 'protected health information'"; "'BAA,' 'business associate agreement'"; "'covered entity,' 'business associate'") plus a behavioral trigger ("or audits any system that creates, receives, maintains, or transmits PHI") give comprehensive natural-term coverage. Anchor 5 fits; 4 ('a few natural terms missing') does not, as no common variation is absent.

5 / 5

Distinctiveness Conflict Risk

A clear HIPAA/healthcare-compliance audit niche with HIPAA-specific triggers ('HIPAA,' 'HITECH,' 'BAA,' 'covered entity'); overlap risk is confined to adjacent privacy skills, and terms like 'healthcare compliance' and 'patient data' stay anchored to the HIPAA frame. Minimal conflict risk matches anchor 5 rather than 4's 'minor overlap risk with closely related skills'.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository

briiirussell/cybersecurity-skills

Path

skills/hipaa-audit/SKILL.md

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.