busybox-on-windows

How to use a Win32 build of BusyBox to run many of the standard UNIX command line tools on Windows.

Quality

52%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Critical

Do not install without reviewing

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agent/skills/busybox-on-windows/SKILL.md

Quality

Content

72%

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

A practical, actionable skill that provides concrete commands for setting up BusyBox on Windows. Its main weaknesses are minor redundancy (duplicate --list entry, unnecessary definition of BusyBox) and the lack of a verification step after downloading the binary to confirm it works correctly.

Suggestions

Add a verification step after download, e.g., 'Verify installation: busybox.exe --list' to confirm the correct binary was downloaded and runs.

Remove the duplicate 'busybox.exe --list' entry (listed under both 'Help' and 'Available UNIX commands') and drop the opening sentence defining BusyBox since Claude already knows what it is.

Dimension	Reasoning	Score
Conciseness	Mostly efficient but has some redundancy — 'busybox.exe --list' is listed twice (for 'Help' and 'Available UNIX commands'), and the introductory sentence explaining what BusyBox is is unnecessary context for Claude. The download variants and conditional logic are appropriately detailed though.	2 / 3
Actionability	Provides fully executable PowerShell commands for CPU detection, OS version checking, downloading the correct binary, and using BusyBox. All commands are copy-paste ready with specific URLs and flags.	3 / 3
Workflow Clarity	The setup workflow is sequenced (check for binary → detect CPU → detect OS → download), but there's no validation step after download (e.g., verify the binary runs with 'busybox.exe --list') and no error handling guidance if the download fails or the wrong architecture is selected.	2 / 3
Progressive Disclosure	For a simple, single-purpose skill under 50 lines with no need for external references, the content is well-organized with clear sections (setup conditional, download options, usage, documentation links). No bundle files are needed.	3 / 3
	Total	10 / 12 Passed

Description

32%

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 identifies a specific tool (BusyBox Win32) and its general purpose but lacks concrete actions, explicit trigger guidance, and natural keyword variations. It reads more like a topic heading than a skill description that would help Claude reliably select it from a large pool of skills.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to run UNIX/Linux commands on Windows without WSL, or mentions BusyBox, or wants lightweight shell utilities on Windows.'

List specific concrete actions or tools, e.g., 'Run commands like grep, sed, awk, find, tar, and other coreutils on Windows using a single BusyBox executable.'

Include common keyword variations users might say, such as 'Linux commands on Windows', 'bash alternatives', 'coreutils', 'shell utilities', 'busybox.exe'.

Dimension	Reasoning	Score
Specificity	It names the domain (BusyBox on Windows, UNIX command line tools) and a general action ('run many of the standard UNIX command line tools'), but does not list specific concrete actions like which tools or what tasks can be accomplished.	2 / 3
Completeness	It partially answers 'what' (use BusyBox to run UNIX tools on Windows) but has no explicit 'when' clause or trigger guidance. The rubric states a missing 'Use when...' clause should cap completeness at 2, and the 'what' is also vague, so this scores a 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'BusyBox', 'Win32', 'UNIX command line tools', and 'Windows', which are terms a user might use. However, it misses common variations like 'Linux commands on Windows', 'bash on Windows', 'coreutils', 'ls', 'grep', 'sed', or 'shell utilities'.	2 / 3
Distinctiveness Conflict Risk	BusyBox Win32 is a fairly specific niche, which helps distinctiveness. However, it could overlap with skills about WSL, Cygwin, Git Bash, or general 'running Linux commands on Windows' skills since the description doesn't clearly delineate its scope.	2 / 3
	Total	7 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: Dokhacgiakhoa/antigravity-ide
Commit: c4a059b

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