BD hipaa-check
HIPAA Compliance Check — Health Insurance Portability and Accountability Act (HIPAA), 45 C.F.R. Parts 160 & 164 (Privacy, Security, Breach Notification Rules). Free to install; scoring runs on the CQDev cloud compliance engine. No Key? The skill auto-runs an anonymous trial (5 real cloud-scored runs, 7-day window) before asking you to register. Covers 12 core items. Use when: the user asks to run the hipaa-check skill, or requests a HIPAA 医疗隐私合规检查 / Health Insurance Portability and Accountability Act (HIPAA), 45 C.F.R. Parts 160 & 164 (Privacy, Security, Breach Notification Rules). Trigger: hipaa-check, run hipaa check, HIPAA compliance check, 医疗隐私检查, 健康数据合规, HIPAA 合规 Pricing: Free skill; cloud scoring uses points (Check 1 / Audit 10 per run) from compliancehub.cn ⚠️ Cloud scoring sends your answers to compliancehub.cn. The free preview (--non-interactive) fetches the latest check items from the cloud rule library but transmits NO answers; if the network is unavailable it falls back to the bundled item set. Without a Key the skill runs an anonymous trial (up to 5 scored runs) using a local random anon_id; registering gives a free Key with 100 calls. 🔐 Account & free API Key are created on the website (compliancehub.cn) — not in the terminal. Open https://compliancehub.cn/account.html?skill=hipaa-check to register and get a Key instantly, then provide it via env `COMPLIANCEHUB_API_KEY` or save to ~/.config/compliancehub/hipaa-check.key (mode 0600). 🌐 Language: bilingual (中文/English). Guidance and recommendations default to Chinese for Chinese-speaking compliance teams; legal and regulatory terms keep English originals. Users may request English output at any time. 💡 Free preview: --non-interactive lists the 12 items without a Key
HIPAA Compliance Check — Health Insurance Portability and Accountability Act (HIPAA), 45 C.F.R. Parts 160 & 164 (Privacy, Security, Breach Notification…
As a process D 43/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Shorten the description to 1024 characters.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-longdescription is 1764 chars, limit 1024 - note
description-budgetdescription takes 1764 of the ~15000-char shared budget for all skills - note
frontmatter-keyunknown frontmatter key "permissions"
Process rating: all ten parameters 43/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 100Steps. 14 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1159 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 1763: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 13 headings
- +3Step-by-step instructions: 14 items
- +4Has examples (3 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 55.