CtrlK
BlogDocsLog inGet started
Tessl Logo

hipaa-compliance

HIPAA-specific entrypoint for healthcare privacy and security work. Use when a task is explicitly framed around HIPAA, PHI handling, covered entities, BAAs, breach posture, or US healthcare compliance requirements.

70

Quality

87%

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

The canonical home for this skill is tdg-personal/hipaa-compliance

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The content is a well-organized, concise routing skill with a clear workflow and clean deferral to sibling skills. Its only gap is actionability: as an overlay it offers decision gates rather than executable commands or code, which is appropriate for its role but scores lower on the concrete-execution anchor.

Suggestions

Since this is an instruction-only routing skill, add a brief concrete output expectation (e.g., 'Produce a HIPAA exposure checklist before proceeding') to make the guidance more directly actionable.

Optionally include one short redaction/example payload pattern in the guardrails to show the opaque-ID preference concretely rather than only stating it.

DimensionReasoningScore

Conciseness

The body is lean, assumes Claude's domain knowledge (no explanation of what HIPAA or PHI is), and every section earns its place as routing or guardrail guidance without padding.

3 / 3

Actionability

It gives a concrete decision-gate checklist ('Is this data PHI?', 'Is this actor a covered entity...') and named escalation targets, but provides no executable code/commands; guidance is decision-oriented rather than copy-paste ready.

2 / 3

Workflow Clarity

The 'How It Works' section gives a clear numbered sequence (start with healthcare-phi-compliance -> apply HIPAA decision gates -> escalate to healthcare-reviewer) with explicit escalation criteria as checkpoints.

3 / 3

Progressive Disclosure

It is a thin overview that defers implementation detail to clearly named sibling skills (healthcare-phi-compliance, healthcare-reviewer) via a Related Skills section, one level deep and well-signaled, with no nested reference chains.

3 / 3

Total

11

/

12

Passed

Description

90%

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

The description is well-constructed with explicit trigger guidance and strong, natural keywords that map to real user phrasing. Its main weakness is specificity: it frames the skill as an entrypoint/overlay rather than naming concrete actions it performs.

Suggestions

Add one or two concrete verbs describing what the skill does (e.g., 'Routes HIPAA-framed tasks to the right compliance skill and applies HIPAA decision gates') to lift specificity from routing language to action language.

Consider naming the decision gates (PHI classification, BAA requirement, minimum-necessary, auditability) briefly in the description so the capability set is explicit.

DimensionReasoningScore

Specificity

It names the HIPAA domain and several concrete subtopics ('PHI handling, covered entities, BAAs, breach posture') but lists no discrete actions the skill performs; it is a routing overlay rather than a set of operations.

2 / 3

Completeness

It states what the skill is ('HIPAA-specific entrypoint for healthcare privacy and security work') and an explicit 'Use when...' clause listing concrete triggers, satisfying both what and when.

3 / 3

Trigger Term Quality

It surfaces the exact natural trigger phrases a user would say ('HIPAA', 'PHI handling', 'covered entities', 'BAAs', 'breach posture', 'US healthcare compliance'), giving strong keyword coverage.

3 / 3

Distinctiveness Conflict Risk

The HIPAA-scoped framing and healthcare-specific triggers carve a clear niche distinct from general security or PHI skills, making false activation unlikely.

3 / 3

Total

11

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
affaan-m/ECC
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.