BC dcf-model
Build discounted cash flow valuation workbooks in Excel.
Build discounted cash flow valuation workbooks in Excel.
As a process C 63/100 · Has gaps — weak spots: execution cost, progress reporting
GeneratorExcelData and analyticsFinanceWriting and documentstype and topics are labelled automatically from the skill text
Runs in: Hermes Agent
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whenneither description nor a "## When to Use" section says when to use the skill - warning
body-longSKILL.md body ≈ 12154 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 63/100
- 0Progress reporting. Says nothing while it works
- 40Execution cost. Instruction body is 12154 tokens: crowds the task out of the window
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
- 60Steps. 353 steps, 9 vague phrases
- 60Result and completion. Output format stated, no completion criterion
- 60Consistency. The Hermes dialect needs category and tags
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Failures and branches. 3 branches, has a failure section
- 100Running it twice. Mutating operations check current state
- low 18 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (5 tags): a typed call is more reliable
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 56: 120–800 characters recommended
- -5TODO / placeholder text left in the skill
- -31 of 1 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +4Structure: 70 headings
- +3Step-by-step instructions: 353 items
- +3Output format is stated explicitly
- +4Has examples (34 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 55.