SKILLEMALL.ai
RU Sign in

BF comps-analysis

Build comparable-company valuation workbooks in Excel.

NousResearch/hermes-agent Hermes author: NousResearch MIT 1 file body ≈ 7 296 tokens Open the sourcegithub.com↗ analyzed 20 h ago

Build comparable-company valuation workbooks in Excel.

As a process F 55/100 · Will not run — References files that are not bundled: examples/comps_example.xlsx

AnalyzerExcelData and analyticstype and topics are labelled automatically from the skill text
Runs in: Hermes Agent
JSON
Technical rating
B
82/100
safety, quality, tests
Safety 60%
100
Quality 40%
55
Run on models
none yet
Process rating
F
55/100
Will not run
References files that are not bundled: examples/comps_example.xlsx
Tools and files w 18
0
Progress reporting w 2
0
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  3. The text references files that are not there: add them or drop the references.
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: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when neither description nor a "## When to Use" section says when to use the skill
  • warning body-long SKILL.md body ≈ 7296 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: examples/comps_example.xlsx

Process rating: all ten parameters 55/100

Will not run. References files that are not bundled: examples/comps_example.xlsx
  • 0Tools and files. 1 referenced file(s) missing: examples/comps_example.xlsx
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 6 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 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
  • 70Execution cost. Instruction body is 7296 tokens
  • 85Steps. 218 steps, 3 vague phrases
  • 100Failures and branches. 3 branches, has a failure section
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 22 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 54: 120–800 characters recommended
  • -220 emoji in the instructions: noise for the model
  • +2Single-language instructions
  • +4Structure: 53 headings
  • +3Step-by-step instructions: 218 items
  • +3Output format is stated explicitly
  • +4Has examples (8 code blocks)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 55.