BusyBox on Windows Skill for Explicit PowerShell Commands
Inspect an installed Windows BusyBox and use an explicit executable path so shell aliases do not change the result.
中文Install in Claude Code
Use your Windows machine and a previously verified BusyBox executable. The example lists synthetic files only.
- Get the complete `cli-tool/components/skills/utilities/busybox-on-windows` directory from the pinned GitHub commit.
- Copy it into the target project's `.claude/skills/`. Check `.claude/skills/busybox-on-windows/SKILL.md`, start Claude Code at the project root, and call `/busybox-on-windows`.
Example task
Place alpha.txt and beta.txt in a temporary directory. Run the installed busybox.exe with ls -1 and compare the filenames.What to check
Both sample files appear, and the command resolves to the explicit BusyBox executable.
Original SKILL.md on GitHub · Updated
Frequently asked question
Will typing ls alone in PowerShell invoke BusyBox?
Check command resolution. An explicit BusyBox path and ls applet avoid PowerShell aliases.