Stats
Actions
Tags
From toolkit
Creates bash shell scripts using conventions like portable shebang, set -euo pipefail, variable casing rules, and colored status outputs.
How this skill is triggered — by the user, by Claude, or both
Slash command
/toolkit:shell-script-developmentThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create shell scripts following consistent conventions.
Create shell scripts following consistent conventions.
#!/usr/bin/env bash
set -e -o pipefail
# Colors
green='\033[0;32m'
red='\033[0;31m'
yellow='\033[1;33m'
blue='\033[0;34m'
nc='\033[0m'
# Script logic here
echo -e "${green}✔${nc} completed successfully"
| Element | Convention |
|---|---|
| Shebang | #!/usr/bin/env bash |
| Safety | set -e -o pipefail |
| Local variables | Lowercase (model, dir, count) |
| Environment variables | Uppercase (PATH, HOME, USER) |
| Color variables | Lowercase (green, red, nc) |
| Status words | Lowercase (error, warning, note) |
echo -e "${green}✔${nc} task completed" # success
echo -e "${red}error${nc}: something failed" # error
echo -e "${yellow}warning${nc}: something to note" # warning
echo -e "${blue}info${nc}: informational message" # info
After creating or modifying shell scripts, inform the user:
Make executable. Run
chmod +x script.shbefore use.
npx claudepluginhub dwmkerr/claude-toolkit --plugin toolkitProvides best practices for Bash/shell scripts: shebang with safety options, variable quoting and defaults, conditionals, loops, arrays. Use when writing or modifying scripts.
Generates production-ready Bash/shell scripts (.sh) for automation, CLI tools, text processing with grep/awk/sed, ops helpers, cron jobs, or CI utilities from requirements.
Enforces modern best practices for shell scripts: portable shebangs, strict mode, quoted variables, error traps, exit codes, and secure coding. Use when writing Bash or POSIX sh scripts.