BC audit-toolkit-pro
审计验证工具箱专业版是企业级审计验证的完整解决方案。在免费版基础上解锁批量审计自动化、实时监控告警、多标准交叉合规分析、审计历史趋势分析、自定义审计模板、加密认证签发六大高级功能，帮助组织建立持续化、自动化、可追溯的审计验证体系。Use。Use when 需要安全检测、合规审计、质量检查、加密防护时使用。不适用于安全评估未授权目标。 功能涵盖: audit, toolkit。
审计验证工具箱专业版是企业级审计验证的完整解决方案。在免费版基础上解锁批量审计自动化、实时监控告警、多标准交叉合规分析、审计历史趋势分析、自定义审计模板、加密认证签发六大高级功能，帮助组织建立持续化、自动化、可追溯的审计验证体系。Use。Use when…
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- 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: 3. 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: All mapping items must start at the same column at line 10, column 1: description: "审计验证工具箱专业版是企业级审计验证的完整解决方案。在免费版基础上解锁批量审计自动化、实时监控告警、多标准交叉合规分析、审计历史趋… when 需要安全检测、合规审计、质量检查、加密防护时使用。不适用于安全评估未授权目标. ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-long-hermesdescription is 189 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "edition" - note
frontmatter-keyunknown frontmatter key "tools"
Process rating: all ten parameters 53/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
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 72 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3080 tokens
- 100Running it twice. No mutating operations
- low 17 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)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +3Description length 189: enough signal without eating the budget
- +4Structure: 57 headings
- +3Step-by-step instructions: 72 items
- +4Has examples (16 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.