BD global-ai-governance
全球 AI 治理版图速查手册——从宏观视角梳理 AI 世界治理格局：世界人工智能合作组织（WAICO，2026-07 上海成立、29 创始国、全球首个 AI 政府间国际组织）、联合国体系（全球数字契约、AI 独立国际科学小组首份报告 2026-07-01、联大能力建设决议、UNESCO）、中国 AI 治理倡议谱系（2023 全球人工智能治理倡议到 2026 人工智能合作发展行动计划）、国际 AI 安全机制（AI 安全峰会系列、各国 AI Safety Institute、国际 AI 安全报告）、主要经济体 AI 战略（美欧英日韩印）、全球南方能力建设与数字鸿沟、治理机制化转型趋势。附零依赖本地工具一键速查国际组织、倡议事件、地区战略与时间线。面向政策研究者、出海战略与行业观察者，企业 AI 治理（ai-governance-playbook）的宏观延伸。
全球 AI 治理版图速查手册——从宏观视角梳理 AI 世界治理格局：世界人工智能合作组织（WAICO，2026-07 上海成立、29 创始国、全球首个 AI 政府间国际组织）、联合国体系（全球数字契约、AI 独立国际科学小组首份报告 2026-07-01、联大能力建设决议、UNESCO）、中国 AI…
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 382 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 611 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 382: 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.