SKILLEMALL.ai

BF archify

Validated interactive HTML diagrams, upstream-maintained.

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

Validated interactive HTML diagrams, upstream-maintained.

As a process F 41/100 · Will not run — References files that are not bundled: scripts/check-update.mjs

AnalyzerGitHubSoftware developmentWriting and documentstype 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%
56
Run on models
none yet
Process rating
F
41/100
Will not run
References files that are not bundled: scripts/check-update.mjs
Tools and files w 18
0
Result and completion w 14
0
Progress reporting w 2
0
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 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 missing-ref reference to a missing file: scripts/check-update.mjs

Process rating: all ten parameters 41/100

Will not run. References files that are not bundled: scripts/check-update.mjs
  • 0Tools and files. 1 referenced file(s) missing: scripts/check-update.mjs
  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 60Consistency. The Hermes dialect needs category and tags
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 75Steps. 3 steps
  • 100Execution cost. Instruction body is 500 tokens
  • 100Running it twice. No mutating operations

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 57: 120–800 characters recommended
  • +4Structure: 2 headings, hard to scan
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +2Single-language instructions
  • +3Step-by-step instructions: 3 items
  • +1License stated

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