BC doc-reasoning-analyst-pro
文档推理分析师专业版是在免费版基础上的全功能升级，专为商业、法律及高风险文档工作流设计。不仅提供核心推理分析能力，更解锁多版本对比分析、结构改进建议、决策准备报告三大高级功能，帮助法务团队、管理层和采购人员在高风险决策中获得全方位支持。Use when 需要数据分析、报表生成、统计洞察、数据可视化时使用。不适用于实时流数据处理。 功能涵盖: doc, reasoning, analyst。
文档推理分析师专业版是在免费版基础上的全功能升级，专为商业、法律及高风险文档工作流设计。不仅提供核心推理分析能力，更解锁多版本对比分析、结构改进建议、决策准备报告三大高级功能，帮助法务团队、管理层和采购人员在高风险决策中获得全方位支持。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: 2. 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 8, column 1: description: "文档推理分析师专业版是在免费版基础上的全功能升级，专为商业、法律及高风险文档工作流设计。不仅提供核心推理分析能力，更解锁多版本对比… 核心能力：核心逻辑提取、风险与薄弱点检测（7大维度）、文档摘要与重写、多版本差异对比分析、文档结构优化方案、决策就绪报告生成（含风险矩阵与建议行动）。内置… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-long-hermesdescription is 196 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 "tools" - note
frontmatter-keyunknown frontmatter key "edition"
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. 96 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2345 tokens
- 100Running it twice. No mutating operations
- low 19 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 196: enough signal without eating the budget
- +4Structure: 55 headings
- +3Step-by-step instructions: 96 items
- +4Has examples (16 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.