CtrlK
BlogDocsLog inGet started
Tessl Logo

healthcare-phi-compliance

Protected Health Information (PHI) and Personally Identifiable Information (PII) compliance patterns for healthcare applications. Covers data classification, access control, audit trails, encryption, and common leak vectors. Use when code touches PHI or PII in a healthcare system, or when auditing access control, audit trails, or leak vectors.

70

Quality

85%

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/healthcare-phi-compliance

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, actionable body with executable code examples and a useful deployment checklist. Adding an explicit validation feedback loop and slightly tightening the enumerated lists would push conciseness and workflow clarity to 5.

Suggestions

Add an explicit validate-fix-retry feedback loop (e.g., after applying RLS policies, run the isolation test and re-apply fixes until 0 leaked rows) to lift workflow clarity to 5.

Tighten the enumerated PHI/PII and leak-vector lists into more compact form to improve token efficiency.

Consider splitting the bulk deployment checklist or extended examples into a reference file to improve progressive disclosure for the longer body.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete code blocks and no over-explanation of familiar concepts; a few enumerated lists (PHI/PII examples, leak vectors) could be tightened slightly.

4 / 5

Actionability

Fully executable SQL and TypeScript examples (RLS policies, audit interface, schema tagging, safe-vs-unsafe logging) are copy-paste ready and cover the common cases.

5 / 5

Workflow Clarity

Clear three-layer model, 'When to Use' section, deployment checklist, and a test-included example ('Expected: 0 rows'); lacks an explicit validate-fix-retry feedback loop, which would lift it to 5.

4 / 5

Progressive Disclosure

Well-organized single-file structure with clear section headers and self-contained content; no bundle references to navigate, and minor organization gaps keep it just below 5.

4 / 5

Total

17

/

20

Passed

Description

87%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, third-person description that clearly defines the skill's healthcare compliance scope and provides explicit usage triggers. Minor gaps in action specificity and synonym coverage keep specificity and trigger quality at 4 rather than 5.

DimensionReasoningScore

Specificity

Lists several concrete capabilities ('data classification, access control, audit trails, encryption, and common leak vectors') but 'compliance patterns' is slightly abstract, leaving minor coverage gaps versus a fully comprehensive action list.

4 / 5

Completeness

Explicitly answers both what (PHI/PII compliance patterns covering specific domains) and when ('Use when code touches PHI or PII in a healthcare system, or when auditing...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural terms present ('code touches PHI or PII', 'auditing access control, audit trails, or leak vectors') with good user-facing phrasing, though a few common synonyms like HIPAA or 'patient data' are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear healthcare PHI/PII niche with distinct triggers, making overlap with other skills minimal.

5 / 5

Total

18

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.