How to use a Win32 build of BusyBox to run many of the standard UNIX command line tools on Windows.
71
Quality
60%
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 ./.agent/skills/busybox-on-windows/SKILL.mdBusyBox is a single binary that implements many common Unix tools.
Use this skill only on Windows. If you are on UNIX, then stop here.
Run the following steps only if you cannot find a busybox.exe file in the same directory as this document is.
These are PowerShell commands, if you have a classic cmd.exe terminal, then you must use powershell -Command "..." to run them.
Get-CimInstance -ClassName Win32_Processor | Select-Object Name, NumberOfCores, MaxClockSpeedGet-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion" | Select-Object ProductName, DisplayVersion, CurrentBuild$ProgressPreference = 'SilentlyContinue'; Invoke-WebRequest -Uri https://frippery.org/files/busybox/busybox.exe -OutFile busybox.exe$ProgressPreference = 'SilentlyContinue'; Invoke-WebRequest -Uri https://frippery.org/files/busybox/busybox64.exe -OutFile busybox.exe$ProgressPreference = 'SilentlyContinue'; Invoke-WebRequest -Uri https://frippery.org/files/busybox/busybox64u.exe -OutFile busybox.exe$ProgressPreference = 'SilentlyContinue'; Invoke-WebRequest -Uri https://frippery.org/files/busybox/busybox64a.exe -OutFile busybox.exeUseful commands:
busybox.exe --listbusybox.exe --listUsage: Prefix the UNIX command with busybox.exe, for example: busybox.exe ls -1
If you need to run a UNIX command under another CWD, then use the absolute path to busybox.exe.
Documentation: https://frippery.org/busybox/ Original BusyBox: https://busybox.net/
3395991
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.