posix-shell-pro
Write Portable POSIX Shell Scripts
Portable shell scripts often break when they rely on Bash extensions or GNU-only behavior. This skill helps Claude, Codex, and Claude Code produce strict POSIX sh with safer patterns and clear validation steps.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "posix-shell-pro" from https://skillstore.io/skills/sickn33-posix-shell-pro.md and its manifest at https://skillstore.io/api/skills/sickn33-posix-shell-pro/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "posix-shell-pro". A Bash script uses arrays, double-bracket tests, and source commands.
Expected outcome:
The skill identifies each non-POSIX construct, suggests positional parameters and case patterns, and lists validation steps for dash and ShellCheck.
Using "posix-shell-pro". A deployment script must work on Alpine, Debian, and macOS.
Expected outcome:
The skill returns a portability checklist covering shell choice, command availability, quoting, temporary files, and platform-specific flags.
Using "posix-shell-pro". A team wants CI checks for portable shell scripts.
Expected outcome:
The skill recommends a multi-shell validation flow with formatting, static analysis, bashism detection, and minimal container testing.
Security Audit
SafeReviewed SKILL.md and found a documentation-only POSIX shell guide, not executable code. Static findings are false positives from inline examples, reference links, and safe-portability guidance; no prompt injection, exfiltration intent, installer behavior, or malicious network activity was found.
Risk Factors
⚙️ External commands (50)
🌐 Network access (7)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-posix-shell-pro/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-posix-shell-pro?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-posix-shell-pro?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-posix-shell-pro/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-posix-shell-pro.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). posix-shell-pro security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-posix-shell-pro/audits/5BibTeX citation
@techreport{sickn33-sickn33-posix-shell-pro-2026,
author = {sickn33},
title = {posix-shell-pro security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-posix-shell-pro/audits/5},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "posix-shell-pro security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/sickn33-posix-shell-pro/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-posix-shell-pro:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Convert a Bash Utility
Replace Bash-specific syntax with POSIX sh patterns while keeping behavior clear and testable.
Harden Release Scripts
Review deployment or packaging scripts for quoting, error handling, cleanup, and cross-platform portability.
Support Minimal Systems
Design scripts that run on BusyBox ash, Alpine containers, and limited Unix-like environments.
Try These Prompts
Review this shell script for strict POSIX sh compatibility. List Bash-specific syntax, unsafe quoting, and simple fixes.
Convert this Bash pattern to POSIX sh. Explain the tradeoffs and include validation commands I should run afterward.
Design a POSIX sh command-line utility for this task. Include argument parsing, error handling, cleanup, and portability checks.
Create a migration plan from Bash to POSIX sh for this project. Prioritize risky constructs, tests, CI updates, and rollout steps.
Best Practices
- Ask for the target shells and operating systems before writing or changing scripts.
- Validate final scripts with POSIX-focused static analysis and at least one strict shell such as dash or ash.
- Keep examples focused on neutral sample data when demonstrating file parsing or system inspection.
Avoid
- Using the skill for Bash-only projects where Bash features are required and documented.
- Treating generated scripts as safe without reviewing paths, quoting, permissions, and inputs.
- Copying portability examples that reference local system files into production scripts without replacing them.