BC accounting-finance-tool-free
面向个人投资者与初级剖析师的财务剖析技能包，包含估值建模、财务比率剖析、. 面向需要accounting finance tool相关能力的开发场景,提供标准化流程和配置参考。财务分析入门工具为个人投资者和财务专业学生提供一套完整的财务分析基础能力。涵盖估值建模、财务比率分析、风险评估三大核心领域，通过结构化的分析框架帮助用户快速理解企业财务状况.
面向个人投资者与初级剖析师的财务剖析技能包，包含估值建模、财务比率剖析、.
As a process C 53/100 · Has gaps — 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.
For the model run — optional
- 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: Missing closing "quote at line 9, column 190: …为个人投资者和财务专业学生提供一套完整的财务分析基础能力。涵盖估值建模、财务比率分析、风险评估三大核心领域，通过结构化的分析框架帮助用户快速理解企业财务状况. ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-long-hermesdescription is 175 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 "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "edition" - note
frontmatter-keyunknown frontmatter key "tools" - note
frontmatter-keyunknown frontmatter key "pricing_tier"
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. 25 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1684 tokens
- 100Running it twice. No mutating operations
- low 13 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 175: enough signal without eating the budget
- +4Structure: 31 headings
- +3Step-by-step instructions: 25 items
- +4Has examples (4 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 54.
External checks
ClawHub: clean
This is a finance-analysis Markdown skill with disclosed local read/write/exec capabilities and no artifact evidence of hidden, destructive, or exfiltrating behavior.
LLM: benign (high) · VirusTotal: · 22 Aug 2026