busybox-on-windows
How to use a Win32 build of BusyBox to run many of the standard UNIX command line tools on Windows.
64
56%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Critical
Do not install without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/busybox-on-windows/SKILL.mdQuality
Discovery
40%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 clear and distinctive niche (BusyBox on Windows) but lacks specificity about what concrete tasks it covers and entirely omits a 'Use when...' clause. It would benefit from listing specific capabilities and adding explicit trigger conditions.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user needs to run UNIX/Linux commands on Windows, mentions BusyBox, or asks about grep/sed/awk/ls on Windows.'
List specific concrete actions or tools covered, e.g., 'Covers installing BusyBox on Windows, running commands like grep, sed, awk, find, and configuring PATH for BusyBox utilities.'
Include common user-facing trigger terms like 'Linux commands on Windows', 'bash utilities on Windows', 'command line tools Windows' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description 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 or commands that the skill covers. | 2 / 3 |
Completeness | The description answers 'what' (use BusyBox to run UNIX tools on Windows) but has no explicit 'when' clause or trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and since the 'what' is also somewhat vague, this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'BusyBox', 'Win32', 'UNIX command line tools', and 'Windows', which are useful triggers. However, it misses common variations users might say such as 'Linux commands on Windows', 'bash on Windows', 'ls/grep/sed on Windows', or specific tool names. | 2 / 3 |
Distinctiveness Conflict Risk | The description targets a very specific niche — Win32 BusyBox for running UNIX tools on Windows — which is unlikely to conflict with other skills. The combination of BusyBox + Win32 + Windows is quite distinctive. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
72%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, executable commands for setting up BusyBox on Windows. Its main weaknesses are minor redundancy (duplicate --list entries, vacuous 'When to Use' section) and the lack of a verification step after downloading the binary to confirm it works correctly.
Suggestions
Remove the duplicate '--list' entry under 'Useful commands' — Help and Available UNIX commands currently show the same command.
Add a verification step after download, e.g., 'Verify installation: `./busybox.exe --help`' to confirm the correct binary was downloaded for the architecture.
Remove or replace the 'When to Use' section, which is a tautology that adds no information.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but has some redundancy: '--list' is listed twice under 'Useful commands' (Help and Available UNIX commands are identical), and the 'When to Use' section is a vacuous tautology that adds no value. The introductory sentence explaining what BusyBox is is borderline unnecessary for Claude. | 2 / 3 |
Actionability | Provides fully executable PowerShell commands for detecting CPU type, downloading the correct binary, and using BusyBox. Commands are copy-paste ready with specific URLs and flags, and usage examples are concrete. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced for the download process with a conditional gate ('only if you cannot find busybox.exe'), but there's no validation step after download (e.g., verify the binary runs with 'busybox.exe --help') and no error handling if the download fails or the wrong architecture is chosen. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the content is well-organized with clear sections (setup steps, usage, documentation links). External references to documentation are provided as one-level-deep links. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%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
- sickn33/antigravity-awesome-skills
- Commit
e18e63c
- 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.