shell-scripting

Name: shell-scripting
Author: sordi-ai

17stars3forks

How to install shell-scripting?

sordi-ai/skill-everything/shell-scripting

$npx -y skills add sordi-ai/skill-everything --skill shell-scripting

Installs into the current project.

Summary

Apply when writing or reviewing Bash or POSIX shell scripts — automation, CI steps, deploy scripts, or any shell-based tooling.

Files · 1

View on GitHub

SKILL.md

1	# Sub-Skill: Bash / POSIX Scripting
2	<!-- target: tokens_target above. Run `python tools/render_readme_table.py` to update README. -->
3
4	Purpose: Prevent silent failures, portability bugs, and security holes in shell scripts by enforcing safe defaults, clean structure, and ShellCheck compliance.
5
6	---
7
8	## Rules
9
10	### Safety & Error Handling
11
12	1. Fail-fast header. Always begin every shell script with `set -euo pipefail` so that unset variables, failed commands, and pipeline errors abort execution immediately. Reference: ERR-2026-021
13
14	2. Trap cleanup. Always register a `trap 'cleanup' EXIT` function to remove temp files and release locks even when the script exits early due to an error.
15
16	3. Meaningful exit codes. Always exit with a non-zero code that reflects the failure category (e.g., `exit 1` for usage errors, `exit 2` for dependency missing); never exit with `0` on failure.
17
18	4. No eval. Never use `eval` to construct or execute dynamic commands; prefer arrays or explicit argument lists to avoid injection vulnerabilities.
19
20	### Variables & Quoting
21
22	5. Quote every variable. Always double-quote variable expansions (`"$var"`, `"$@"`) to prevent word-splitting and glob expansion on values containing spaces or special characters.
23
24	6. Declare locals. Always declare variables inside functions with `local` to prevent accidental global namespace pollution.
25
26	7. Readonly constants. Use `readonly` for values that must not change after assignment (e.g., `readonly SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"`).
27
28	### Portability & Compatibility
29
30	8. POSIX shebang. Always start scripts with `#!/usr/bin/env bash` (or `#!/bin/sh` for strict POSIX); never rely on `/bin/bash` being present at a fixed path on all target systems.
31
32	9. Portable syntax. Prefer POSIX-compatible constructs (`[ ]` over `[[ ]]`, `$(...)` over backticks) when the script must run under `/bin/sh`; use Bash-specific features only when the shebang explicitly targets Bash.
33
34	10. ShellCheck clean. Ensure every script passes `shellcheck -S warning` with zero warnings before committing; treat ShellCheck output as mandatory, not advisory.
35
36	### Structure & Maintainability
37
38	11. Use functions. Always decompose scripts longer than ~30 lines into named functions with a `main` entry point called at the bottom; avoid top-level imperative code scattered throughout the file.
39
40	12. Argument parsing with getopts. Use `getopts` for option parsing in scripts that accept flags; never parse `$1`, `$2` manually for flag-style arguments.
41
42	13. Temp file handling. Always create temporary files with `mktemp` and store the path in a variable cleaned up by the `EXIT` trap; never hard-code paths like `/tmp/myfile`.
43
44	### Logging & Idempotency
45
46	14. Structured logging. Use a `log()` helper that prefixes output with a timestamp and level (`INFO`, `WARN`, `ERROR`) and routes errors to stderr (`>&2`); never mix diagnostic output into stdout used for data.
47
48	15. Idempotent operations. Ensure scripts can be run multiple times without side effects — use guards like `[ -d "$dir" ] \|\| mkdir -p "$dir"` and `command -v tool >/dev/null 2>&1 \|\| install_tool` before acting.
49
50	16. Heredocs for multi-line strings. Prefer heredocs (`<<'EOF' ... EOF`) over concatenated `echo` calls for multi-line output or embedded config; use the quoted form (`<<'EOF'`) to suppress variable expansion when the content is literal.
51
52	---
53
54	## See also
55
56	- `skills/code-quality/SKILL.md`
57	- `skills/error-log/SKILL.md`

People who liked this also viewed

6 picks

Type

paperclip-create-agentCreate new agents in Paperclip with governance-aware hiring. Use when you need to inspect adapter configuration options, compare existing agent configs, draft a new agent prompt/config, and submit a hSkillsJul 2026157k5
subagent-driven-developmentUse when executing implementation plans with independent tasks in the current sessionSkillsJul 2026154k259k
dispatching-parallel-agentsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesSkillsJul 2026143k259k
browser-act-skill-forgeForges reusable Skill packages (SKILL.md + scripts) from website exploration via browser-act — no re-exploration later. Use when: user wants a reusable Skill for any website, needs to understand a sitSkillsJul 202685k4.6k
wizardGenerate an interactive bash wizard that walks a human through a manual procedure — third-party setup, a one-off migration, an A→B state transition — opening URLs, capturing values, confirming each stSkillsJul 202675k182k
wonda-cliUsing the Wonda CLI to generate images, videos, music, and audio from the terminal — plus LinkedIn, Reddit, and X/Twitter research and automationSkillsJul 202666k137

shell-scripting

17stars3forks

View on GitHub

How to install shell-scripting?

sordi-ai/skill-everything/shell-scripting

$npx -y skills add sordi-ai/skill-everything --skill shell-scripting

Installs into the current project.

Summary

Apply when writing or reviewing Bash or POSIX shell scripts — automation, CI steps, deploy scripts, or any shell-based tooling.

Files · 1

View on GitHub

SKILL.md

1	# Sub-Skill: Bash / POSIX Scripting
2	<!-- target: tokens_target above. Run `python tools/render_readme_table.py` to update README. -->
3
4	Purpose: Prevent silent failures, portability bugs, and security holes in shell scripts by enforcing safe defaults, clean structure, and ShellCheck compliance.
5
6	---
7
8	## Rules
9
10	### Safety & Error Handling
11
12	1. Fail-fast header. Always begin every shell script with `set -euo pipefail` so that unset variables, failed commands, and pipeline errors abort execution immediately. Reference: ERR-2026-021
13
14	2. Trap cleanup. Always register a `trap 'cleanup' EXIT` function to remove temp files and release locks even when the script exits early due to an error.
15
16	3. Meaningful exit codes. Always exit with a non-zero code that reflects the failure category (e.g., `exit 1` for usage errors, `exit 2` for dependency missing); never exit with `0` on failure.
17
18	4. No eval. Never use `eval` to construct or execute dynamic commands; prefer arrays or explicit argument lists to avoid injection vulnerabilities.
19
20	### Variables & Quoting
21
22	5. Quote every variable. Always double-quote variable expansions (`"$var"`, `"$@"`) to prevent word-splitting and glob expansion on values containing spaces or special characters.
23
24	6. Declare locals. Always declare variables inside functions with `local` to prevent accidental global namespace pollution.
25
26	7. Readonly constants. Use `readonly` for values that must not change after assignment (e.g., `readonly SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"`).
27
28	### Portability & Compatibility
29
30	8. POSIX shebang. Always start scripts with `#!/usr/bin/env bash` (or `#!/bin/sh` for strict POSIX); never rely on `/bin/bash` being present at a fixed path on all target systems.
31
32	9. Portable syntax. Prefer POSIX-compatible constructs (`[ ]` over `[[ ]]`, `$(...)` over backticks) when the script must run under `/bin/sh`; use Bash-specific features only when the shebang explicitly targets Bash.
33
34	10. ShellCheck clean. Ensure every script passes `shellcheck -S warning` with zero warnings before committing; treat ShellCheck output as mandatory, not advisory.
35
36	### Structure & Maintainability
37
38	11. Use functions. Always decompose scripts longer than ~30 lines into named functions with a `main` entry point called at the bottom; avoid top-level imperative code scattered throughout the file.
39
40	12. Argument parsing with getopts. Use `getopts` for option parsing in scripts that accept flags; never parse `$1`, `$2` manually for flag-style arguments.
41
42	13. Temp file handling. Always create temporary files with `mktemp` and store the path in a variable cleaned up by the `EXIT` trap; never hard-code paths like `/tmp/myfile`.
43
44	### Logging & Idempotency
45
46	14. Structured logging. Use a `log()` helper that prefixes output with a timestamp and level (`INFO`, `WARN`, `ERROR`) and routes errors to stderr (`>&2`); never mix diagnostic output into stdout used for data.
47
48	15. Idempotent operations. Ensure scripts can be run multiple times without side effects — use guards like `[ -d "$dir" ] \|\| mkdir -p "$dir"` and `command -v tool >/dev/null 2>&1 \|\| install_tool` before acting.
49
50	16. Heredocs for multi-line strings. Prefer heredocs (`<<'EOF' ... EOF`) over concatenated `echo` calls for multi-line output or embedded config; use the quoted form (`<<'EOF'`) to suppress variable expansion when the content is literal.
51
52	---
53
54	## See also
55
56	- `skills/code-quality/SKILL.md`
57	- `skills/error-log/SKILL.md`

People who liked this also viewed

6 picks

Type