CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

auditing-safe-harbor-checklist

Verify OpenMed de-identified output against all 18 HIPAA Safe Harbor identifier categories and report residual re-identification risk. Use when the user must confirm a note meets HIPAA Safe Harbor (45 CFR 164.514(b)(2)), needs a coverage checklist mapping detected entities to the 18 categories, wants to flag gaps like ages over 89, rare geography, fax vs phone, or biometrics, or asks whether masking was complete. Maps OpenMed CANONICAL_LABELS to the 18 HIPAA classes and uses extract_pii / deidentify to check coverage. Pairs with OpenMed deidentifying-clinical-text and auditing-deidentification-runs.

72

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%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.

An excellent, highly actionable skill body: executable quick-start code, a sequenced workflow with validation and human sign-off, and textbook progressive disclosure to a single real reference file. Minor deductions for repeated transformation-rule content and an only-implied error-recovery loop.

Suggestions

State the recovery loop explicitly in the workflow (e.g., 'if residual_risk is non-zero, re-run deidentify with strict_no_leak or adjust the profile via configuring-privacy-policies, then re-audit') instead of only pointing at the related skills.

Consolidate the ages>89 / ZIP / date transformation rules into one place (the workflow step or the edge-cases section) and reference the other, removing the duplicated cautions to save tokens.

Trim the 'Pairs with' / sibling-skill detail repeated between the description and the body's 'Hand-off' section, keeping the deeper routing in the body only.

DimensionReasoningScore

Conciseness

Dense and efficient overall with no basic-concept padding, but the ages>89 / ZIP / date transformation rules are stated substantively twice — in Workflow step 3 and again in 'Edge cases & gotchas' ('OpenMed will not cap automatically') — duplication that could be trimmed.

4 / 5

Actionability

The Quick start is fully executable, copy-paste-ready Python with a worked example note, and the workflow uses concrete API calls ('openmed.deidentify(note, policy="hipaa_safe_harbor")', 'Run audit=True and read residual_risk') plus exact module paths.

5 / 5

Workflow Clarity

A clear 5-step sequence with an explicit validation checkpoint ('Non-zero projected leakage → review') and mandatory human sign-off, but the recovery path on a failed review is only implied via pointers ('strict_no_leak', 'configuring-privacy-policies') rather than a stated fix-and-rerun loop.

4 / 5

Progressive Disclosure

The 18-category mapping table is correctly split out to references/safe-harbor-identifiers.md (a real, verified file), signaled clearly ('Read it when you need the authoritative cross-walk') and one level deep, with a lean overview body that keeps only key cautions inline.

5 / 5

Total

18

/

20

Passed

Description

92%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 strong, highly specific description with an explicit 'Use when' trigger clause and concrete scenario phrases. Its only weakness is slight verbosity and a few missing natural synonyms (e.g., 'PHI', 'compliance') that keeps trigger coverage just short of comprehensive.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Verify OpenMed de-identified output against all 18 HIPAA Safe Harbor identifier categories', 'report residual re-identification risk', 'mapping detected entities to the 18 categories', 'flag gaps like ages over 89, rare geography, fax vs phone' — with comprehensive coverage; not the minor-gap level of anchor 4.

5 / 5

Completeness

Explicitly answers both: 'what' is stated up front (verify against the 18 categories, report residual risk) and 'when' via 'Use when the user must confirm a note meets HIPAA Safe Harbor (45 CFR 164.514(b)(2)) … or asks whether masking was complete' with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('HIPAA Safe Harbor', 'coverage checklist', 'masking was complete', 're-identification risk', 'ages over 89'), but common synonyms a user might say — 'PHI', 'compliance check', 'de-id audit' — are absent, fitting 'a few natural terms missing' rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

Clear niche — auditing OpenMed output against 45 CFR 164.514(b)(2) — and it explicitly scopes sibling skills ('Pairs with OpenMed deidentifying-clinical-text and auditing-deidentification-runs'), minimizing overlap risk.

5 / 5

Total

19

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

maziyarpanahi/openmed

Path

skills/auditing-safe-harbor-checklist/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.