busybox-on-windows

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

Quality

47%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./plugins/antigravity-awesome-skills/skills/busybox-on-windows/SKILL.md

The canonical home for this skill is busybox-on-windows in sickn33/agentic-awesome-skills

Quality

Content

72%Scale 1-3

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

This is a reasonably well-constructed skill that provides concrete, actionable commands for installing and using BusyBox on Windows. Its main weaknesses are some boilerplate padding (the generic 'When to Use' and 'Limitations' sections), a duplicated command listing, and a missing validation step after download. The implicit mapping between CPU detection output and which binary to download could be made explicit.

Suggestions

Remove the boilerplate 'When to Use' and 'Limitations' sections, and the redundant duplicate of 'busybox.exe --list' — these waste tokens without adding value.

Add a validation step after download, e.g., 'Verify installation: `./busybox.exe --help`' to confirm the binary works.

Explicitly map the CPU detection output to the correct download variant (e.g., 'If ARM64 → use busybox64a.exe, if x64 → use busybox64u.exe') rather than leaving Claude to infer the mapping.

Dimension	Reasoning	Score
Conciseness	Mostly efficient but has some unnecessary content: the 'When to Use' and 'Limitations' sections are boilerplate that add no value, 'busybox.exe --list' is listed twice under different labels (Help and Available UNIX commands), and the introductory sentence explaining what BusyBox is is unnecessary for Claude.	2 / 3
Actionability	Provides fully executable PowerShell commands for detecting CPU architecture, downloading the correct binary, and using BusyBox. The download URLs are specific, commands are copy-paste ready, and usage patterns are concrete with examples.	3 / 3
Workflow Clarity	The steps for downloading are clearly sequenced with a conditional check (only if busybox.exe not found), but there's no validation step after download (e.g., verify the binary runs with `busybox.exe --help`). The decision logic for which build to download based on the CPU/OS info is left implicit rather than explicitly mapped.	2 / 3
Progressive Disclosure	For a simple, single-purpose skill with no bundle files, the content is appropriately structured in a single file with clear sections. External documentation links are provided for deeper reference. No need for additional files.	3 / 3
	Total	10 / 12 Passed

Description

22%Scale 1-3

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 reads like a tutorial title rather than a skill selection guide. It identifies the domain (BusyBox on Windows) but fails to list specific capabilities, concrete actions, or explicit trigger conditions. The niche topic provides some natural distinctiveness, but the lack of specificity and missing 'Use when' clause significantly weaken its utility for skill selection.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to run UNIX utilities like grep, sed, awk, tar, or ls on Windows using BusyBox.'

List specific concrete actions and tools, e.g., 'Configures and runs BusyBox on Windows to provide grep, sed, awk, find, tar, and 100+ other UNIX utilities without WSL or Cygwin.'

Rewrite in third person active voice describing what the skill does, e.g., 'Guides setup and usage of Win32 BusyBox...' rather than 'How to use...'

Dimension	Reasoning	Score
Specificity	The description says 'run many of the standard UNIX command line tools on Windows' which is vague — it doesn't list any specific tools or concrete actions like 'use grep, sed, awk, tar' etc. The phrase 'How to use' is also weak framing.	1 / 3
Completeness	It partially addresses 'what' (use BusyBox for UNIX tools on Windows) but there is no explicit 'when' clause or trigger guidance. The description reads more like a tutorial title than a skill selection guide. Missing 'Use when...' caps this at 2 per guidelines, but the 'what' is also weak, so scoring 1.	1 / 3
Trigger Term Quality	Contains some relevant keywords like 'BusyBox', 'Win32', 'UNIX command line tools', and 'Windows' that users might mention. However, it lacks specific tool names (grep, sed, awk, ls, etc.) and common variations users would naturally say.	2 / 3
Distinctiveness Conflict Risk	BusyBox on Windows is a fairly specific niche, which helps distinctiveness. However, the vague 'UNIX command line tools' phrasing could overlap with skills about WSL, Cygwin, Git Bash, or general shell scripting on Windows.	2 / 3
	Total	6 / 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: popey/claude-code-skills
Path: plugins/antigravity-awesome-skills/skills/busybox-on-windows/SKILL.md
Commit: a5a6601

Reviewed: 20 hours 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.