Name: crabbox-quickstart
Rating: 70.39999999999999 (1 reviews)
Author: openclaw

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

88%

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

The canonical home for this skill is crabbox-quickstart in openclaw/crabbox

Quality

Content

82%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 lean, command-rich quickstart with a clear operational loop, strong error-recovery guidance, and an explicit handoff to the full crabbox skill for advanced concerns. Conciseness and workflow clarity are strong but leave minor room to tighten prose and consolidate validation into a single checklist.

Suggestions

Tighten transitional prose such as 'Read this before swapping uname -a for real work' and 'Above and below, ./run-tests.sh stands for your own test command' to lift conciseness toward anchor 5.

Consolidate the readiness and recovery checkpoints (doctor, sync-plan, error-code rerun, list) into one short sequenced checklist so the workflow reads as a single validate-then-proceed path.

Consider extracting the error-code reference and sync-detail lists into a reference file linked from the body to better match a split-file progressive-disclosure structure.

Dimension	Reasoning	Score
Conciseness	Command-dense and assumes Claude's competence (no explanation of Docker, Git, or Ubuntu); a few prose lines like 'Read this before swapping uname -a for real work' could be trimmed, fitting anchor 4 rather than anchor 5's every-token-earns-its-place bar.	4 / 5
Actionability	Provides copy-paste-ready commands across install, first run, warmup, dependency install, sync-plan, results, and stop, with the <slug> placeholder explained by warmup's output, matching anchor 5's fully executable common-case coverage.	5 / 5
Workflow Clarity	States the loop (lease -> sync -> run -> read output -> stop) with checkpoints (doctor readiness, sync-plan preview, list cleanup) and an error feedback loop (read message -> rerun doctor), but checkpoints are spread across sections with no consolidated checklist, fitting anchor 4 over anchor 5.	4 / 5
Progressive Disclosure	Well-organized into clear sections with an explicit, well-signaled handoff to the full crabbox skill ('When you outgrow this page') and no nested references, but as a single >50-line file with no bundle split it fits anchor 4 rather than anchor 5's split-file overview.	4 / 5
	Total	17 / 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 clearly states a concrete capability, gives explicit natural-language trigger phrases, and draws a sharp boundary against the full crabbox skill. The only mild gap is trigger-term breadth, where a few additional synonyms would push it to fully comprehensive.

Dimension	Reasoning	Score
Specificity	Names concrete actions ('run your repository's tests inside a disposable Docker or Podman container', 'then stop the box', 'hand off') but the quickstart scope keeps the action set narrow rather than comprehensive, matching anchor 4 and falling short of anchor 5's broad coverage.	4 / 5
Completeness	Explicitly answers both what (run repo tests in a disposable container, then stop the box) and when ('Use when someone asks what Crabbox is or how to try it...') with concrete trigger phrases and a handoff boundary, matching anchor 5.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('what Crabbox is', 'how to try it', 'throwaway sandbox', 'crabbox init') with synonyms (disposable/throwaway), but a few common variations are absent, fitting anchor 4 over anchor 5's exhaustive coverage.	4 / 5
Distinctiveness Conflict Risk	Names Crabbox specifically and explicitly carves out the full crabbox skill's territory ('hand off to the crabbox skill for config that already exists, leased remote machines, jobs, secrets, or artifacts'), giving a clear niche with minimal conflict risk per anchor 5.	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: .agents/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.