How to use a Win32 build of BusyBox to run many of the standard UNIX command line tools on Windows.
73
61%
Does it follow best practices?
Impact
93%
1.55xAverage score across 3 eval scenarios
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/busybox-on-windows/SKILL.mdThe canonical home for this skill is busybox-on-windows in sickn33/agentic-awesome-skills
BusyBox command usage and path handling
busybox.exe prefix on all commands
100%
100%
No bare Unix commands
100%
100%
Absolute path after cd
100%
100%
Demonstrates absolute path syntax
75%
83%
busybox.exe --list invoked
100%
100%
Correct .exe suffix
100%
100%
Multiple distinct commands
100%
100%
Windows context
100%
100%
CWD change demonstrated
100%
100%
Text-processing via busybox.exe
100%
100%
BusyBox download and setup
Existence check
100%
100%
CPU info retrieval
0%
100%
OS version retrieval
0%
100%
Four architecture variants
50%
50%
frippery.org source
100%
100%
ProgressPreference suppressed
0%
100%
Output named busybox.exe
100%
100%
cmd.exe compatibility
0%
0%
Architecture-aware selection
100%
100%
Windows targeting
100%
100%
BusyBox CI/CD pipeline integration
Conditional download
100%
100%
PowerShell used for setup
100%
100%
cmd.exe compatibility
20%
100%
frippery.org download source
0%
100%
ProgressPreference suppressed
0%
100%
Output saved as busybox.exe
0%
100%
busybox.exe prefix on build commands
0%
71%
Absolute path after directory change
0%
100%
At least two Unix operations via busybox.exe
0%
100%
Windows build agent context
100%
100%
57c135b
Table of Contents
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.