busybox-on-windows
How to use a Win32 build of BusyBox to run many of the standard UNIX command line tools on Windows.
61
52%
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
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 clear domain (BusyBox on Windows) but is too general in describing capabilities and entirely lacks explicit trigger guidance ('Use when...'). It would benefit from listing specific tools/actions and adding clear trigger conditions to help Claude distinguish this skill from other Windows-UNIX interoperability skills.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about running UNIX/Linux commands on Windows without WSL, or mentions BusyBox, or needs lightweight coreutils on Windows.'
List specific concrete actions or tools, e.g., 'Provides guidance on installing and using BusyBox for Windows to run tools like grep, sed, awk, find, tar, and other coreutils without requiring WSL or Cygwin.'
Add distinguishing terms to differentiate from WSL/Cygwin/Git Bash skills, e.g., 'lightweight alternative to WSL' or 'standalone Win32 binary'.
| 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 capabilities like which tools or what tasks can be accomplished. | 2 / 3 |
Completeness | The description addresses 'what' (using BusyBox to run UNIX tools on Windows) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' itself is also somewhat vague, warranting a score of 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', 'grep', 'sed', 'awk', or 'coreutils'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Win32 build of BusyBox' is fairly distinctive and narrows the niche, but 'UNIX command line tools on Windows' could overlap with skills about WSL, Cygwin, Git Bash, or other similar tools. | 2 / 3 |
Total | 7 / 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 practical, actionable skill for setting up BusyBox on Windows with concrete, executable commands and appropriate architecture-specific download options. Its main weaknesses are some boilerplate padding (the generic 'When to Use' and 'Limitations' sections), a duplicated command listing, and the lack of a post-download verification step to confirm the binary works correctly.
Suggestions
Add a verification step after download, e.g., 'Verify installation: `./busybox.exe --help` should print usage information'
Remove the boilerplate 'When to Use' and 'Limitations' sections which add no skill-specific value, and deduplicate the --list entry
| 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 opening sentence explaining what BusyBox is is unnecessary context 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 examples are concrete. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (detect architecture → download → use), but there's no validation checkpoint after download (e.g., verify the binary exists and runs with `busybox.exe --help`). For a workflow involving downloading and executing an external binary, a verification step is important. | 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 |
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
e40fdb8
- 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.