BD gdpr-export-compliance
GDPR 出海合规实操手册——面向中国企业出海欧洲，覆盖 GDPR 适用范围与域外管辖判定、六项合法处理基础与健康数据特殊类别（明确同意等）、数据主体权利响应（访问/删除/可携/反对及时限）、DPIA 数据保护影响评估、跨境传输机制（充分性认定/SCC 标准合同条款/BCR 约束性公司规则/例外情形）、违规罚款与数据泄露通报（72 小时/两档罚款上限 2000 万欧或 4%）、GDPR 与中国个保法对照与落地清单，附零依赖本地工具一键判定适用范围、推荐合法基础、速查权利与罚款。面向出海企业法务、合规与数据负责人，与医械数据出海合规互补。
GDPR 出海合规实操手册——面向中国企业出海欧洲，覆盖 GDPR 适用范围与域外管辖判定、六项合法处理基础与健康数据特殊类别（明确同意等）、数据主体权利响应（访问/删除/可携/反对及时限）、DPIA 数据保护影响评估、跨境传输机制（充分性认定/SCC 标准合同条款/BCR…
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: 18. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 271 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 562 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 271: 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 (8 of 8)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.