SKILLEMALL.ai

BD term

Fast, explicit terminal execution via OpenClaw exec (direct dispatch; you type the exact command).

modbender/skill-library-mcp Claude Code author: modbender MIT 1 file body ≈ 851 tokens Open the sourcegithub.com analyzed 3 d ago

Fast, explicit terminal execution via OpenClaw exec (direct dispatch; you type the exact command).

As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureAI and agentsSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
B
87/100
safety, quality, tests
Safety 60%
99
Quality 40%
69
Run on models
none yet
Process rating
D
49/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

    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 Dangerous commands cmd-pipe-to-shell SKILL.md:52
      Downloads and executes remote code from an unrecognised host (pipe to shell) (negated — the text forbids it)
      - no `curl ... | sh`
      negated

    Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "command-dispatch"
    • note frontmatter-key unknown frontmatter key "command-tool"
    • note frontmatter-key unknown frontmatter key "command-arg-mode"

    Process rating: all ten parameters 49/100

    • 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
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 2 mutating operations with no state check
    • 40Consistency. Frontmatter name (term) differs from the folder (agi-term-helper)
    • 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
    • 100Steps. 21 steps
    • 100Failures and branches. 1 branches, has a failure section
    • 100Execution cost. Instruction body is 851 tokens
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
    • low The response is described with custom markup (3 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 98: 120–800 characters recommended
    • +3Output format is not stated: the model decides each time
    • +4No input/output examples
    • -5TODO / placeholder text left in the skill
    • +1No license
    • +2Single-language instructions
    • +4Structure: 13 headings
    • +3Step-by-step instructions: 21 items

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