Portable Tools

**Judgement:** This skill is a solid, practical methodology for making scripts and tools genuinely portable across machines. It’s conceptually strong, example-driven, and directly applicable to real-world development workflows, especially for CLI tooling and skills that others will run on different setups. **Strengths** - Focuses on *assumption hygiene*: "never assume your device is the only device" and explicitly lists what can vary (paths, account names, services, data formats, environment). - Provides concrete patterns: explicit over implicit queries, validate-before-use, fallback chains, and highly actionable error messages. - Includes a disciplined debugging approach (exact data, before/after proof, cross-device thinking) and practical checklists for discovery, implementation, testing, and documentation. - Real-world OAuth/keychain example grounds the methodology and shows before/after improvements. **Risks / Limitations** - This is guidance and methodology, not an automated framework; effectiveness depends entirely on the developer correctly applying the patterns. - Examples are heavily biased toward macOS, shell, `security`, and `jq`; developers on Windows or non-Unix environments must translate patterns themselves. - Does not deeply address more complex portability axes (e.g., containerization, network variance, different auth backends) beyond naming/config differences. **Recommended Scenarios** - Building or refactoring scripts that read config, credentials, or tokens and will be shared across teammates or machines. - Designing Clawhub skills meant for public use, where you want to avoid “works on my machine” incidents. - Adding a portability review step to code reviews and sprint/test plans, especially in devops, tooling, and infrastructure teams. - Training less-experienced developers to think in terms of explicitness, validation, and failure handling when working with system state and configuration.