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

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/crabbox/SKILL.md

Quality

Content

77%

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

The body is highly actionable and well-sequenced with concrete commands and validation checkpoints, but it is verbose with repeated policy statements and monolithic with no progressive disclosure into reference files.

Suggestions

Consolidate the repeated provider-selection policy into one stated contract and reference it instead of restating 'preserve the resolved provider' across many sections.

Split the long Observability Flags reference and provider-specific command catalogs into reference files under references/ and link to them from SKILL.md.

Move the macOS/Windows, AWS, and Blacksmith provider sections into separate reference files so SKILL.md stays a concise overview with one-level-deep links.

Dimension	Reasoning	Score
Conciseness	The body is operational and avoids explaining concepts Claude already knows, but it is ~860 lines with significant repetition of the provider-selection policy ('preserve the resolved provider', 'do not switch providers unless the user explicitly requests') that could be tightened.	2 / 3
Actionability	It provides extensive copy-paste-ready commands with exact flags, env vars, and JSON summary fields (e.g. the AWS changed-gate `crabbox run --idle-timeout 90m ...` block and the live-provider debug template).	3 / 3
Workflow Clarity	Multi-step flows are explicitly sequenced with validation checkpoints, e.g. the numbered E2E verification flow (reproduce -> patch -> one Crabbox E2E command -> record proof) and 'If Crabbox Fails' triage with verify-cleanup steps.	3 / 3
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ are absent) and the skill is a single monolithic ~860-line file; sections are well-organized with headers, but reference-style content (Observability Flags, provider-specific sections) that could be split out is all inline.	2 / 3
	Total	10 / 12 Passed

Description

57%

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 is specific and distinctive, naming concrete platforms, the delegated backend, and a reporting requirement, but it omits an explicit 'Use when' trigger clause and leans on the generic term 'validation'.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to validate or run tests via Crabbox, or mentions Testbox/cbx/tbx lease ids.'

Replace or supplement the abstract 'validation' with concrete operations (e.g. 'run remote tests, manage leases, inspect sync/logs, clean up boxes').

Include natural user phrasings such as 'test in Crabbox' or 'Crabbox lease' as trigger terms.

Dimension	Reasoning	Score
Specificity	Names the tool, the target platforms (Linux, macOS, Windows, WSL2), the delegated Blacksmith Testbox path, and a concrete reporting action ('Report the actual provider and id'), but the core verb 'validation' is somewhat abstract rather than enumerating distinct operations.	2 / 3
Completeness	It clearly states what the skill does, but there is no explicit 'Use when...' trigger clause, so the 'when' is only implied; per the rubric this caps completeness at 2.	2 / 3
Trigger Term Quality	It surfaces the natural product name 'Crabbox' and 'Blacksmith Testbox' that a user would say, but 'validation' is generic and common phrasings like 'test in Crabbox' are not represented.	2 / 3
Distinctiveness Conflict Risk	The 'Crabbox wrapper' niche with provider/id reporting and delegated Testbox proof is highly specific and unlikely to fire for unrelated skills.	3 / 3
	Total	9 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Commit: 45c34fe

Reviewed: 2 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.