skills.rest
LuisSambrano
LuisSambranoCOMMUNITY
Explore all skills by this author →
𝕏@luissambrano_uxGitHub

posix-pro

Write strict POSIX sh scripts for portability across Unix-like systems.

7|2|Updated Jan 28, 2026
Search Tags:#automation#shell scripting#posix#portability#unix#bash alternatives
One-click install
npx skills add https://github.com/LuisSambrano/antigravity-config --skill posix-pro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: posix-pro
Source: https://github.com/LuisSambrano/antigravity-config/tree/main/skills/4-automation/posix-pro
Command: npx skills add https://github.com/LuisSambrano/antigravity-config --skill posix-pro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures your shell scripts are highly portable and function reliably across a wide range of Unix-like systems by adhering strictly to POSIX standards.

Core Features & Use Cases

  • Maximum Portability: Develop shell scripts that run on any POSIX-compliant shell (dash, ash, sh, bash --posix).
  • Cross-Platform Compatibility: Ensure scripts work on Linux, BSD, Solaris, AIX, and macOS.
  • Use Case: You need to create a deployment script that must run on a minimal Docker image (like Alpine) and a legacy server, without relying on bash-specific features.

Quick Start

Use the posix-pro skill to create a portable shell script that checks if a file exists and is readable.

Frequently Asked Questions about posix-pro

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write portable POSIX sh scripts that run on any Unix system?▼

Cross-platform shell scripting ensures your scripts function reliably across Linux, BSD, Solaris, AIX, and macOS by adhering strictly to POSIX standards and avoiding non-portable constructs that break on minimal or legacy systems.

How do I safely parse arguments in a POSIX-compliant shell script?▼

Safe argument parsing in a POSIX-compliant shell script requires avoiding bash-specific arrays or features, instead relying on strict POSIX constraints and portable error handling to process inputs safely across all Unix-like systems.

Does my deployment script need bash to run on Alpine Linux and legacy servers?▼

Your deployment script does not need bash if you use POSIX sh scripting, which runs on any POSIX-compliant shell like dash or ash, ensuring maximum portability across minimal Docker images and legacy servers without bash dependencies.

What is the best way to handle file operations without relying on bash-specific features?▼

Using POSIX sh scripting instead of bash alternatives provides maximum portability across Unix-like systems by strictly adhering to POSIX constraints, ensuring scripts execute reliably on any POSIX-compliant shell including dash, ash, and sh.

Why does my shell script fail on different Unix-like operating systems?▼

Shell scripts often fail across Unix-like operating systems due to reliance on bash-specific features; using strict POSIX sh scripting with portable error handling ensures cross-platform compatibility across Linux, BSD, Solaris, and AIX.

Related Skills

Explore More Software Engineering Skills→
scruffydanscruffydan

shell-security

Provide POSIX shell security guidance for safe quoting and input handling.

Community
Basic
JingyueCongJingyueCong

posix-shell-pro

Review shell scripts for POSIX compliance and portability improvements.

Community
Advanced
masermediagroup-stackmasermediagroup-stack
1

shell-scripting

Write portable POSIX sh and Bash scripts with error handling and testing.

Community
Advanced
sawrussawrus
17

bash-pro

Enforce defensive Bash scripting safety and portability with ShellCheck, shfmt, and Bats.

Community
Advanced