# Cross Platform Safety

> Ensure commands and paths are safe across Windows + WSL + Docker (PowerShell vs bash, path translation, permissions). Use when instructions touch shell, filesystem, Docker, or OS-specific behavior.

- Skill: `janjaszczak/cross-platform-safety` (Agent Skill)
- Install (CLI): `npx skillmds@latest add janjaszczak/cross-platform-safety`
- Raw SKILL.md: https://api.skillmd.com/api/skills/janjaszczak/cross-platform-safety/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: janjaszczak (https://skillmd.com/u/janjaszczak)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/janjaszczak/cross-platform-safety

---


# cross-platform-safety

## Activation gate (anti-noise)
Activate if any of:
- The user mentions Windows/WSL/PowerShell/Docker explicitly.
- You must provide shell commands that could differ by OS.
- Paths/permissions/volumes/networking are involved.

## Procedure
1. Determine execution context:
   - Where the command will run (Windows host? WSL? container?).
2. Provide OS-specific variants ONLY if needed:
   - Prefer a single canonical path + “Windows note” if small delta.
3. Guardrails:
   - Avoid reserved PowerShell variables and quoting pitfalls.
   - Avoid whitespace path breakage; use explicit quoting.
4. Validate critical commands with “dry read” steps (e.g., `pwd`, `whoami`, `ls`).

## Output
- “Run in: <context>” + exact command(s) + 1–2 quick verification commands.