SKILLEMALL.ai
GitHub ↗ RU Sign in

BF shop

Shop catalog search, checkout, order tracking, returns.

NousResearch/hermes-agent Hermes author: NousResearch MIT 5 files body ≈ 4 040 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Shop catalog search, checkout, order tracking, returns.

As a process F 41/100 · Will not run — References files that are not bundled: url

IntegrationShopifyCommercetype and topics are labelled automatically from the skill text
Runs in: Hermes Agent
JSON
Technical rating
B
86/100
safety, quality, tests
Safety 60%
98
Quality 40%
67
Run on models
none yet
Process rating
F
41/100
Will not run
References files that are not bundled: url
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
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 · 2

✓ No critical or high findings

Medium and low: 2
  • low Secrets in code secret-high-entropy-token references/catalog-mcp.md:122
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    { "has_next_page": true, "total_count": 649, "cursor": "eyJv…5fQ" }
    quoted
  • low Secrets in code secret-high-entropy-token references/catalog-mcp.md:133
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "pagination": { "limit": 8, "cursor": "eyJv…5fQ" }
    quoted

Files scanned: 5. 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: url
  • note frontmatter-key unknown frontmatter key "prerequisites"

Process rating: all ten parameters 41/100

Will not run. References files that are not bundled: url
  • 0Tools and files. 1 referenced file(s) missing: url
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 15 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 60Consistency. The Hermes dialect needs category and tags
  • 70Execution cost. Instruction body is 4040 tokens
  • 100Steps. 49 steps
  • 100Failures and branches. 2 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 12 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 55: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +4Structure: 18 headings
  • +3Step-by-step instructions: 49 items
  • +4Has examples (7 code blocks)
  • +4Reference files are cited in the instructions (4 of 4)
  • +1License stated

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