CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

crabbox

Detect and use Crabbox for repository tests and validation on remote runners. Use when crabbox.yaml or .crabbox.yaml exists, the crabbox CLI is available, or work needs remote compute, a clean or reusable environment, target-platform coverage, or auditable execution evidence.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

The body is an exceptionally actionable command reference with concrete, executable examples for every Crabbox surface and a solid failure-triage section. Its weaknesses are redundancy (the Useful Commands catalog re-lists commands already demonstrated) and the absence of any progressive disclosure: a ~490-line monolith whose provider deep-dives and command catalogs should live in separate reference files.

Suggestions

Split the Hyper-V provider subsection and the 'Useful Commands' catalog into separate reference files (e.g. references/providers-hyperv.md, references/command-reference.md) and link them from short overview sections, so SKILL.md works as a lean index rather than a 490-line monolith.

Remove or drastically trim the 'Useful Commands' section: most entries duplicate commands already shown with context in their home sections, so keeping only commands not demonstrated elsewhere would cut ~30 lines of redundant tokens.

Add a brief top-level workflow (detect config -> verify CLI with doctor -> authenticate -> choose remote surface -> run with preflight/timing -> triage via results/logs -> stop lease) so the overall sequence and its validation gates are explicit rather than implied by section order.

DimensionReasoningScore

Conciseness

The body is command-dense with no conceptual padding, but the 40-line 'Useful Commands' catalog duplicates roughly two dozen commands already shown with context (warmup/status/run, job list, pool ready, history/events/logs/results, webvnc, artifacts collect/publish), 'Detect Crabbox' and 'Source Of Truth' overlap on config inspection and doctor, and the Hyper-V section is a dense prose wall. This is more than the 'minor instances' of the level-4 anchor, fitting 'mostly efficient but could be tightened'.

3 / 5

Actionability

Nearly every section gives copy-paste-ready commands with real flags covering the common cases, e.g. 'crabbox run --fresh-pr example-org/my-app#123 --script ./scripts/e2e-smoke.sh' and the warmup -> status --wait -> run -> stop lane. Placeholders like <lease> and <broker-url> are used consistently and appropriately. This matches the fully executable, common-case-covering top anchor.

5 / 5

Workflow Clarity

Per-lane sequences are explicit and ordered (login -> whoami -> doctor; warmup -> status --wait -> run -> stop), validation checkpoints exist ('crabbox doctor', '--preflight', 'job run --dry-run', '--require-artifact'), and the 'Failure Triage' section supplies error-recovery feedback loops. It falls short of a 5 because there is no top-level ordered workflow tying detect -> auth -> choose-surface -> run together, and some checkpoints remain implicit rather than stated as gates.

4 / 5

Progressive Disclosure

Section headers are clear and logically ordered, but this is a ~490-line single file with no bundle: the provider-specific Hyper-V deep-dive and the 'Useful Commands' catalog are exactly the content that belongs in separate reference files. The one external pointer ('See docs/providers/hyperv.md') is a bare inline mention of a file not present in the skill bundle rather than a well-signaled navigable reference. This fits 'some structure but content that should be separate is inline', above the minimal-structure level 2.

3 / 5

Total

15

/

20

Passed

Description

82%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 with an explicit Use-when clause and concrete file/CLI triggers that make it highly discoverable and distinct. Its main limitation is that the capability statement is compressed to 'detect and use... for repository tests and validation', underselling the breadth of surfaces the skill actually covers.

DimensionReasoningScore

Specificity

Names the domain ('repository tests and validation on remote runners') and 1-2 concrete actions ('Detect and use Crabbox'), matching the anchor for domain plus limited actions. It does not list the several distinct capabilities the body covers (warm leases, fresh PR checkouts, UI proof, artifacts), so it is not comprehensive enough for a 4.

3 / 5

Completeness

It explicitly answers both questions: the 'what' is 'Detect and use Crabbox for repository tests and validation on remote runners' and the 'when' is a concrete 'Use when...' clause listing file-existence, CLI-availability, and capability triggers. This matches the top anchor's structure of clear what plus explicit when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good trigger coverage: config filename variants ('crabbox.yaml or .crabbox.yaml'), the CLI name, 'remote compute', and 'remote runners' are phrases a user or repo state would naturally surface. It falls short of comprehensive because 'target-platform coverage' and 'auditable execution evidence' are jargon rather than natural user synonyms, and terms like 'CI' or 'cloud' are missing.

4 / 5

Distinctiveness Conflict Risk

The unique tool name plus precise triggers (config file existence, CLI availability) establish a clear niche with minimal overlap risk. Generic capability phrases like 'remote compute' add slight breadth, but the primary triggers would not plausibly fire a different skill.

5 / 5

Total

17

/

20

Passed

Validation

100%

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/SKILL.md

Reviewed

Table of Contents

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.