Give Windows coding agents Linux-style shell commands with Fauxnix
Install Fauxnix so agents on Windows can issue familiar Linux-style shell commands that are translated deterministically to native PowerShell.
npx skills add agentskillexchange/skills --skill give-windows-coding-agents-linux-style-shell-commands-with-fauxnix
npm install -g fauxnix-cli, run fauxnix install --claude, --codex, --opencode, --kimi, or --qwen for the target client, then run fauxnix doctor to verify encoding, config, and MCP round-trip.Use Fauxnix when a coding agent is running on Windows but keeps reaching for Bash and GNU-style commands such as `ls`, `grep`, `find`, `cat`, `wc`, or process controls. The operator installs the Fauxnix CLI or MCP server, connects it to Claude Code, Codex, OpenCode, Kimi Code, Qwen Code, or another MCP client, runs `fauxnix doctor`, and lets the agent call the `bash` tool while Fauxnix translates the supported command subset to native PowerShell with Linux-like output and errors.
What this skill actually does
Invoke this instead of manually translating commands when the user wants agent sessions on Windows to stay productive without WSL, a VM, or repeated prompt corrections. The scope boundary is deterministic Bash-to-PowerShell command execution for agent workflows. It is not a general terminal emulator, arbitrary shell sandbox, or PowerShell training guide.
Inputs and prerequisites: Windows, PowerShell 5.1+, Node.js 18+, npm, MCP-compatible agent client.
Setup notes: Install with npm install -g fauxnix-cli , run fauxnix install –claude , –codex , –opencode , –kimi , or –qwen for the target client, then run fauxnix doctor to verify encoding, config, and MCP round-trip.
Source and verification boundary: use https://github.com/20000419/fauxnix as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a MCP workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.