BD AI Company CLO
AI公司首席法务官技能包。合同治理、知识产权保护、AI专项法务（算法审计/AIGC合规/数据供应链）。覆盖GDPR/CCPA跨境数据合规，新增AI伦理委员会架构、合规分级目标、数据保护双线接口、AIGC内容合规审查链。
As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
medium Broad scope
meta-agent-memory-dumpHEARTBEAT.mdAgent memory / workspace files bundled with the skill (4) — likely a workspace dump with personal data or tokensHEARTBEAT.md, IDENTITY.md, SOUL.md, USER.md
-
low Risky intent
intent-offensive-securitySOUL.md:384Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| 漏洞管理 | 15% | 无扫描/已知CVE | 自动化扫描+SLAs达标 | 全覆盖+MTTD<1h+bug bounty |
Files scanned: 12. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 48, column 13: - code: CLO_001 message: Contract review requires human approval ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "triggers" - note
frontmatter-keyunknown frontmatter key "interface"
Process rating: all ten parameters 49/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
- 40Consistency. Frontmatter name (AI Company CLO) differs from the folder (ai-company-clo-2-0-0)
- 100Tools and files. No external tools needed
- 100Steps. 34 steps
- 100Execution cost. Instruction body is 1193 tokens
- 100Running it twice. No mutating operations
- 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 109: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Structure: 36 headings
- +3Step-by-step instructions: 34 items
- +4Has examples (3 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 52.