SKILLEMALL.ai
GitHub ↗ RU Sign in

BD crabbox-quickstart

First contact with Crabbox: run your repository's tests inside a disposable Docker or Podman container on your own machine, no account and no cloud spend, then stop the box. Use when someone asks what Crabbox is or how to try it, wants a throwaway sandbox for a repo with no crabbox.yaml yet, or is about to run crabbox init here; hand off to the crabbox skill for config that already exists, leased remote machines, jobs, secrets, or artifacts.

openclaw/crabbox Agent Skills author: openclaw MIT 1 file body ≈ 1 463 tokens Open the sourcegithub.com↗ analyzed 32 h ago

First contact with Crabbox: run your repository's tests inside a disposable Docker or Podman container on your own machine, no account and no cloud spend…

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

ProcedureDockerSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
B
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
85
Run on models
none yet
Process rating
D
48/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

The same skill appears in 1 more place: crabbox

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 · 0

    ✓ No critical or high findings

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

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 48/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. 4 mutating operations with no state check
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
    • 100Steps. 11 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1463 tokens
    • low 11 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)
    • +3Output format is not stated: the model decides each time
    • +2Single-language instructions
    • +3Description length 445: enough signal without eating the budget
    • +4Structure: 12 headings
    • +3Step-by-step instructions: 11 items
    • +4Has examples (8 code blocks)
    • +1License stated

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