SKILLEMALL.ai

BF skillcraft

Create, design, and package Clawdbot skills. Use when asked to "make/build/craft a skill for X", or when extracting ad-hoc functionality ("turn my script/agent instructions/library into a skill"). Applies Clawdbot-specific integration concerns (tool calling, memory, message routing etc.) to build reusable skills that compose.

sundial-org/awesome-openclaw-skills Agent Skills author: sundial-org 5 files body ≈ 5 051 tokens Open the sourcegithub.com analyzed 2 d ago

Create, design, and package Clawdbot skills.

As a process F 49/100 · Will not run — References files that are not bundled: scripts/helper.sh

GeneratorAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
73
Run on models
none yet
Process rating
F
49/100
Will not run
References files that are not bundled: scripts/helper.sh
Tools and files w 18
0
When it triggers w 12
20
Result and completion w 14
40
the three weakest of ten parameters · all ten

How to improve

  1. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  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: 5. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 5051 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: scripts/helper.sh

Process rating: all ten parameters 49/100

Will not run. References files that are not bundled: scripts/helper.sh
  • 0Tools and files. 1 referenced file(s) missing: scripts/helper.sh
  • 20When it triggers. No condition that starts the skill
  • 40Result and completion. Does not say what the result is
  • 60Steps. 108 steps, 4 vague phrases
  • 65Failures and branches. 3 branches
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Execution cost. Instruction body is 5051 tokens
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • low The response is described with custom markup (18 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

  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 2 example trigger phrases
  • +3Description length 327: enough signal without eating the budget
  • +4Structure: 28 headings
  • +3Step-by-step instructions: 108 items
  • +4Has examples (9 code blocks)

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