Script Portability & Shell Hardening / Acrazie

Improve selected scripts across the approved target OS/shell/runner matrix while preserving required behavior, error propagation and filesystem boundaries. Keeping an existing compatible helper can be the correct outcome; modernization is not the goal.

Project loading boundary

Published-library defaults remain model-invocable within the requested task. An explicit project kit or stricter current instruction takes precedence: propose this skill from available metadata and wait for the user's explicit command before reading its instructions. Apply the same gate to each dependency before reading or dispatching its instructions; one invocation does not activate a chain. Use $skill-name in Codex or /skill-name in Claude Code. These gates are not filesystem access controls or proof of live host behavior. Global homonyms may remain a blocker. Do not read or delegate an unactivated skill as a bypass. Loading grants no editing, installation, network, spawning or shipping permission. Ordinary library defaults retain scoped implicit handoffs; no new mandatory Interview dependency is introduced. Keep this specialist's bounded clarification.