SKILLEMALL.ai
GitHub ↗ RU Sign in

BC erpclaw-buying

Procure-to-pay cycle -- suppliers, material requests, RFQs, supplier quotations, purchase orders, purchase receipts, purchase invoices, debit notes, landed costs

modbender/skill-library-mcp Hermes author: modbender MIT 6 files body ≈ 3 588 tokens Open the sourcegithub.com↗ analyzed 3 d ago

Procure-to-pay cycle -- suppliers, material requests, RFQs, supplier quotations, purchase orders, purchase receipts, purchase invoices, debit notes, landed…

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

ProcedureSales and CRMFinancetype and topics are labelled automatically from the skill text
Runs in: OpenClaw Hermes Agent
JSON
Technical rating
B
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
70
Run on models
none yet
Process rating
C
60/100
Has gaps
Inputs and preconditions w 11
0
Progress reporting w 2
0
When it triggers w 12
20
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. For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
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: 6. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-long-hermes description is 161 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • warning description-no-when neither description nor a "## When to Use" section says when to use the skill
  • note frontmatter-key unknown frontmatter key "homepage"
  • note frontmatter-key unknown frontmatter key "source"
  • note frontmatter-key unknown frontmatter key "tier"
  • note frontmatter-key unknown frontmatter key "requires"
  • note frontmatter-key unknown frontmatter key "database"

Process rating: all ten parameters 60/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 29 mutating operations with no state check
  • 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 85Steps. 25 steps, 1 vague phrases
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3588 tokens
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

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)
  • +2Single-language instructions
  • +3Description length 161: enough signal without eating the budget
  • +4Structure: 30 headings
  • +3Step-by-step instructions: 25 items
  • +3Output format is stated explicitly
  • +4Has examples (5 code blocks)
  • +3All 1 scripts are documented
  • +1License stated

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