BD medical-data-export-compliance
医疗器械企业数据出境与出海合规实操手册——覆盖中国数据出境"3+2+4"监管体系与三条合规路径（数据出境安全评估、个人信息出境标准合同、2026-01-01 施行的个人信息出境认证）、10万/100万人数阈值与累计计算规则、医疗健康数据特殊要求（首部医疗数据强制性国标、医疗数据安全审查、大湾区标准合同）、主要目标市场数据法（欧盟 GDPR/EHDS、美国 HIPAA、新加坡 PDPA、日韩），含出海场景实操（临床试验数据/远程诊疗/云服务/员工数据）、合规落地五步流程与年度审计要求（2026-08-20 施行风险评估办法），附零依赖本地工具一键判定出境路径、计算人数阈值、输出场景清单。面向医疗器械企业国际业务、合规与数据负责人。
医疗器械企业数据出境与出海合规实操手册——覆盖中国数据出境"3+2+4"监管体系与三条合规路径（数据出境安全评估、个人信息出境标准合同、2026-01-01…
As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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: 17. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 318 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
description-no-whenneither description nor a "## When to Use" section says when to use the skill - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "display_name" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "title" - note
frontmatter-keyunknown frontmatter key "description_en"
Process rating: all ten parameters 46/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
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 100Steps. 16 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 608 tokens
- 100Running it twice. No mutating operations
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)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +3Description length 318: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 16 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (7 of 7)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.