BB cn-global-compliance
Global compliance checker & data localization audit tool with API-powered regulations database (出海合规检查+数据本地化审计+全球法规数据库API). Check GDPR readiness, CCPA compliance, data localization, cross-border data transfer, payment licensing, content moderation laws, AI Act requirements, and China data outbound transfer (数据出境评估) rules via real API backend. Features: (1) API-powered regulations database covering 7 markets (US/EU/UK/Japan/SEA/ME/Australia), (2) Compliance gap analysis with remediation roadmap, (3) Data outbound transfer self-assessment (数据出境自评), (4) Executable regulations.sh script for CLI access, (5) App Store review compliance checklists. ONLY skill covering Chinese product overseas expansion compliance with API backend + data localization audit. Use when: compliance check, regulatory compliance audit, GDPR readiness, cross-border data compliance, data localization audit, 出海合规, 数据出境评估, GDPR合规, 海外上架, CCPA, COPPA, AI Act compliance. Triggers: compliance checker, regulatory compliance audit, GDPR check, CCPA, data privacy, cross-border data compliance, data localization audit, international launch, 出海合规, 数据出境评估, 合规检查, 中国出海, 海外合规, 跨境数据合规, 隐私合规, app出海, compliance API, regulations API, AI Act compliance, 数据出境自评
As a process B 67/100 · Nearly there — weak spots: when it triggers, inputs and preconditions, running it twice
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: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-longdescription is 1227 chars, limit 1024
Process rating: all ten parameters 67/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 60Failures and branches. 2 branches
- 100Tools and files. No external tools needed
- 100Steps. 54 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3495 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 top-level sections: this looks like several domains in one skill
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 1227: 120–800 characters recommended
- -5TODO / placeholder text left in the skill
- -213 emoji in the instructions: noise for the model
- -41 reference files, but SKILL.md never points to them: the model will not open them
- -31 of 2 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +4Structure: 26 headings
- +3Step-by-step instructions: 54 items
- +3Output format is stated explicitly
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 45.