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.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-crafted quickstart: executable commands at every step, an explicit loop with validation checkpoints and error recovery, and clean sectioning. The only real gap is the absence of any reference bundle for advanced detail, which leaves progressive disclosure at the good-but-not-excellent level.

Suggestions

Move the deeper error/diagnostic detail (exit-code table, failure-digest behavior) into a short references/diagnostics.md and link to it, which would lift progressive disclosure without losing the lean quickstart.

Tighten the opening paragraph and timing prose since the command examples already demonstrate the behavior, recovering a few tokens.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes competence ("The box is bare", "Commands after `--` are literal argv") with little padding, but a few prose passages like the opening paragraph restate behavior that the command examples already convey and could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready commands for every stage (install, doctor, run, warmup, install deps, sync-plan, stop, list) with the `<slug>` placeholder clearly explained by `warmup`, covering the common cases end to end.	5 / 5
Workflow Clarity	The loop is explicitly sequenced (`lease -> sync -> run -> read output -> stop`), each step is expanded, and there are explicit validation/recovery checkpoints: `doctor` readiness, an exit-code error table (2/6/7/4), a failure digest with `next:` commands, and dedicated stop/list cleanup.	5 / 5
Progressive Disclosure	The single-file quickstart is organized into clear, well-labeled sections and appropriately hands off advanced concerns to the full `crabbox` skill, but no one-level-deep reference files exist (references/, scripts/, assets/ are empty), so the navigation signal that the 5 anchor requires is absent.	4 / 5
	Total	18 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that crisply states both capability and trigger conditions and cleanly partitions responsibility from the full crabbox skill. Minor room to surface a few more natural trigger keywords and broaden the action list beyond the run-tests case.

Suggestions

Add a couple of natural user phrases (e.g. "run my tests in a throwaway Docker/Podman container") as explicit trigger terms to lift trigger-term coverage.

Consider naming one or two additional concrete actions (e.g. warm/reuse a box, capture test results) so the capability list reads as more comprehensive rather than single-purpose.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — "run your repository's tests inside a disposable Docker or Podman container on your own machine... then stop the box" — with specific runtime and hosting constraints, though coverage centers on the single run-tests use case rather than a broad action set.	4 / 5
Completeness	It explicitly answers both what ("run your repository's tests inside a disposable Docker or Podman container... then stop the box") and when ("Use when someone asks what Crabbox is or how to try it, wants a throwaway sandbox...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases are present ("asks what Crabbox is", "how to try it", "throwaway sandbox", "crabbox init"), giving good keyword coverage, but a few likely user phrases like "run tests in Docker" are only implicit rather than surfaced as triggers.	4 / 5
Distinctiveness Conflict Risk	The niche is sharply defined (local-container, no config, first contact) and it explicitly distinguishes itself from the sibling skill via "hand off to the crabbox skill for config that already exists, leased remote machines, jobs, secrets, or artifacts," minimizing misfires.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: openclaw/crabbox
Path: skills/crabbox-quickstart/SKILL.md
Commit: 0c2d43a

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.