SKILLEMALL.ai
GitHub ↗ RU Sign in

BC scrollcraft

Premium scroll-driven landing pages; scroll = timeline.

NousResearch/hermes-agent Hermes author: NousResearch MIT 21 files · 1 script body ≈ 2 878 tokens Open the sourcegithub.com↗ analyzed 15 h ago

Premium scroll-driven landing pages; scroll = timeline.

As a process C 61/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, running it twice

GeneratorPlaywrightMarketingtype and topics are labelled automatically from the skill text
Runs in: Hermes Agent
JSON
Technical rating
B
88/100
safety, quality, tests
Safety 60%
99
Quality 40%
72
Run on models
none yet
Process rating
C
61/100
Has gaps
Inputs and preconditions w 11
0
When it triggers w 12
20
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.
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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Exfiltration read-dotenv scripts/doctor.mjs:139
    Reads a .env file (quoted — discussed, not commanded)
    "Only needed to GENERATE imagery. Building from your own photos and footage needs no key and no spend. Copy .env.example to .env to set one.");
    quoted

Files scanned: 21. 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

Process rating: all ten parameters 61/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 3 mutating operations with no state check
  • 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 60Consistency. The Hermes dialect needs category and tags
  • 100Steps. 23 steps
  • 100Failures and branches. 2 branches, has a failure section
  • 100Execution cost. Instruction body is 2878 tokens
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 11 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (8 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 55: 120–800 characters recommended
  • -2localhost URLs: will not work for another user
  • -31 of 7 scripts are never mentioned in SKILL.md
  • +2Single-language instructions
  • +4Structure: 12 headings
  • +3Step-by-step instructions: 23 items
  • +3Output format is stated explicitly
  • +4Has examples (4 code blocks)
  • +4Reference files are cited in the instructions (8 of 8)
  • +1License stated

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