CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

crabbox

Use the Crabbox wrapper for validation across Linux, macOS, Windows, and WSL2, including delegated Blacksmith Testbox proof. Report the actual provider and id.

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/crabbox/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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 exceptionally actionable — concrete, executable commands with exact flags, output fields, and error-recovery paths — and the workflows are well sequenced with validation checkpoints. However, it is heavily redundant (the provider-override rule and the env-var strings repeat many times) and monolithic, with hundreds of lines of per-provider reference material inlined that belongs in separate bundle files.

Suggestions

Split the per-backend command catalogs (AWS, Blacksmith Testbox, macOS/Windows targets, desktop/WebVNC) and the observability flag reference into references/*.md files, leaving SKILL.md as a concise overview with one-level-deep pointers.

Deduplicate the provider-override policy into a single authoritative statement in the Provider Selection Contract section and remove the restatements scattered through First Checks, Observability, Brokered AWS, and Failure Triage.

Replace the five verbatim repeats of the NODE_OPTIONS/OPENCLAW_* env-var string with one named template (e.g. defined once and referenced as 'the standard test env') to cut significant tokens.

DimensionReasoningScore

Conciseness

The provider-override policy ('override only when the user explicitly names a backend', 'preserve the resolved provider') is restated more than a dozen times across sections, and the identical NODE_OPTIONS/OPENCLAW_* env-var string is duplicated verbatim in five command blocks. There is no explaining of concepts Claude already knows, which keeps it above a 1, but the repetition is heavy padding for an ~860-line body.

2 / 5

Actionability

Guidance is fully executable throughout: complete shell invocations with flags ('crabbox config show', 'crabbox run --idle-timeout 90m --ttl 240m --timing-json --shell -- ...'), exact JSON summary fields (provider, leaseId, syncDelegated, commandPhases), precise flag semantics, and copy-paste-ready debug and handoff-repair templates covering the common cases.

5 / 5

Workflow Clarity

The document is well sequenced (First Checks, backend gates, observability, E2E lanes, reuse, desktop, failure triage) with a numbered E2E flow and validation checkpoints plus feedback loops (crabbox doctor, one retry with --debug --timing-json, lease cleanup verification, rerun only the failing shard). It falls short of 5 because the overall operational order across the topic sections is implicit rather than one coherent sequence, and checkpoints are scattered.

4 / 5

Progressive Disclosure

There are no bundle files at all (references/, scripts/, assets/ are absent) and the entire per-backend command catalogs, observability flag reference, E2E verification patterns, and failure triage are inlined in one ~860-line SKILL.md. This is content that clearly belongs in separate reference files; the clear section headers keep it above a 1.

2 / 5

Total

13

/

20

Passed

Description

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

The description names a specific tool and platforms with a couple of concrete actions, but it is incomplete: it lacks any 'when to use' trigger guidance and misses common natural keywords like 'testing' or 'CI'. Distinctiveness is good thanks to the unique product names.

Suggestions

Add a 'Use when...' clause with concrete triggers, e.g. 'Use when the user asks to test or validate OpenClaw changes on Linux, macOS, Windows, or WSL2, mentions Crabbox or Blacksmith Testbox, or asks for remote/CI proof.'

Include natural user phrasings as trigger terms — 'run tests', 'testing', 'CI proof', 'cross-platform validation' — not just 'validation'.

Briefly enumerate the main capabilities (environment lifecycle, sync, logs/results, cache inspection, lease cleanup) so the 'what' is comprehensive rather than naming only validation.

DimensionReasoningScore

Specificity

Names the domain ('Crabbox wrapper for validation across Linux, macOS, Windows, and WSL2') and a couple of concrete actions ('delegated Blacksmith Testbox proof', 'Report the actual provider and id'), but omits the other actions the skill actually covers (environment lifecycle, sync, logs, cleanup), so coverage is not comprehensive.

3 / 5

Completeness

The 'what' is clear (wrapper-based validation across four platforms plus delegated proof and provider reporting), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3.

3 / 5

Trigger Term Quality

Includes some relevant keywords ('validation', 'Linux', 'macOS', 'Windows', 'WSL2', 'Blacksmith Testbox') but misses natural variations users would say such as 'testing', 'run tests', 'CI', or 'cross-platform'.

3 / 5

Distinctiveness Conflict Risk

The distinctive product names 'Crabbox' and 'Blacksmith Testbox' create a clear niche with minimal conflict risk, but the broad term 'validation' leaves minor overlap risk with generic testing skills, and no explicit triggers are given as in the score-5 anchor.

4 / 5

Total

13

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (860 lines); consider splitting into references/ and linking

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

14

/

16

Passed

Repository

openclaw/clawsweeper

Path

.agents/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.