CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nex-hipaa-small-practice

Builds a HIPAA compliance file for a small US practice: risk analysis, policies, BAAs, workforce training log and breach response plan. Use when: Conduct a HIPAA security risk analysis with impact scoring; Generate privacy and security policies for small medical offices; Create breach response workflows and notification templates.

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/nex-compliance/skills/nex-hipaa-small-practice/SKILL.md

The canonical home for this skill is nex-hipaa-small-practice in NexaiGuy/nex-ai-skills

SKILL.md
Quality
Evals
Security

Quality

Content

36%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 body reads as a marketing landing page for the skill rather than operational instructions: it describes deliverables and disclaims certification but provides no methodology, templates, or workflow steps, and confirms the actual package materials are absent from the folder. Structure and brevity are reasonable, but actionability and workflow clarity are weak because Claude executing this skill would have nothing concrete to work from.

Suggestions

Replace the descriptive 'What it does' bullets with an explicit sequenced workflow: gather asset inventory → score threats by likelihood/impact → draft each policy → assemble BAAs → breach decision flow, with validation checkpoints (e.g., verify every 45 CFR 164.504(e) clause is present in each BAA).

Ship the actual artifacts as bundle files (risk-analysis template, policy set text, BAA template, breach notification letter) and reference them one level deep from the body, e.g. '**BAA template**: See [templates/baa.md](templates/baa.md)'.

Remove the promotional footer, creator catalog link, and FAQ section; they add tokens without improving execution, and the FAQ duplicates 'What it does'.

DimensionReasoningScore

Conciseness

The body is short and free of explanations of concepts Claude already knows, but includes tokens that earn no place: promotional material ('Free skill by Nex AI... More skills, including the paid catalog: https://...'), an Example section, and an FAQ ('Does this include a security risk assessment?') that mostly restates 'What it does'. Anchor 3 (mostly efficient, some unnecessary content that could be tightened) fits; not 4 because the promo links and FAQ are clearly trimmable, not minor.

3 / 5

Actionability

Quotes: 'Runs the Security Rule risk analysis across administrative, physical and technical safeguards, scored and documented' and 'Generates the core policy set' — these describe outputs rather than instruct. Only minimal concrete grounding exists ('the required 45 CFR 164.504(e) clauses', '60-day notification workflow, including the HHS reporting thresholds'), and the body explicitly states 'Scripts, extension source, and templates from the original package are not in this folder', so there is nothing executable to act on. Not 1 because a few concrete regulatory anchors are given; not 3 because no steps, templates, scoring criteria, or policy content are provided.

2 / 5

Workflow Clarity

The closest thing to a workflow is the 'What it does' bullet list (risk analysis → policy set → BAAs → breach workflow), which is a rough outline of activities with many gaps, poorly defined steps, and no validation checkpoints — matching anchor 2. Not 3 because even implicit checkpoints are absent and the deliverable list is not an actionable sequence; not 1 because the component ordering and the breach/notification decision flow are at least coherently conveyed.

2 / 5

Progressive Disclosure

Sections are well organized (What it does / Use cases / Known limitations / Example / Questions) and the body is short, but there are no bundle files at all — the body admits 'Scripts, extension source, and templates from the original package are not in this folder' — so the templates and reference material this skill clearly needs have nowhere to live. Anchor 3 (some structure, but organization incomplete) fits; the simple-skill exception does not apply because a multi-artifact compliance skill genuinely needs external reference files.

3 / 5

Total

10

/

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.

The description is strong: third-person voice, a concrete 'what' enumerating the deliverables, and an explicit 'Use when:' clause with three natural trigger scenarios. Trigger keyword coverage is good but omits a few natural synonyms (PHI, BAA, HIPAA compliance/audit), keeping trigger_term_quality at 4 rather than 5.

DimensionReasoningScore

Specificity

Quotes: 'Builds a HIPAA compliance file for a small US practice: risk analysis, policies, BAAs, workforce training log and breach response plan' and 'risk analysis with impact scoring', 'notification templates'. Multiple specific concrete deliverables are named, comprehensively covering the skill's stated capabilities. Not 4 because coverage matches the full scope (risk analysis, policies, BAAs, training log, breach plan) with no meaningful gaps.

5 / 5

Completeness

Quotes: a clear 'what' ('Builds a HIPAA compliance file for a small US practice: risk analysis, policies, BAAs, workforce training log and breach response plan') followed by an explicit 'Use when:' clause with three concrete trigger phrases. Both what and when are explicitly and concretely answered. Not 4 because the 'when' is already explicit with concrete trigger phrases, not merely implicit or generic.

5 / 5

Trigger Term Quality

Quotes: 'Use when: Conduct a HIPAA security risk analysis with impact scoring; Generate privacy and security policies for small medical offices; Create breach response workflows and notification templates.' Good natural keyword coverage (HIPAA, risk analysis, policies, medical offices, breach response), but common user phrases like 'HIPAA compliance', 'PHI', 'OCR audit', and 'BAA' are missing from the trigger clause. Not 5 because synonyms and variations a user would naturally say are incompletely covered; not 3 because the terms present are natural and well-targeted rather than generic.

4 / 5

Distinctiveness Conflict Risk

Quotes: 'HIPAA compliance file for a small US practice', 'HIPAA security risk analysis', 'privacy and security policies for small medical offices'. A clear niche (US HIPAA compliance for small practices) with distinct domain-specific triggers; minimal risk of firing for unrelated skills. Not 4 because the triggers are domain-unique terms unlikely to overlap with any neighboring skill.

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

NexaiGuy/nex-ai-skills

Path

plugins/nex-compliance/skills/nex-hipaa-small-practice/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.