[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BSAWN81GKEWHRVGPJQ2SSA":3,"skill-same:01M7BSAWN81GKEWHRVGPJQ2SSA":168},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7BSAWN81GKEWHRVGPJQ2SSA","shell-script-pro",null,"Write, edit, lint, format, or review shell scripts (.sh files or extensionless scripts with a shell shebang). Use for any Bash or POSIX sh scripting task.","thimslugga\u002Fagent-plugins","thimslugga","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F285055?v=4","01M7BRYXXABGR31PBN8YW9YYD3","Adam Kaminski","01M7BRYXY1GHRY2VCK15WG8NCZ",0,"MIT","https:\u002F\u002Fgithub.com\u002Fthimslugga\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbuilder\u002Fskills\u002Fshell-script-pro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"shell-script-pro\"\ndescription: >-\n   Write, edit, lint, format, or review shell scripts (.sh files or extensionless scripts with a shell shebang). Use for any Bash or POSIX sh scripting task.\n---\n\n# Shell Script Pro\n\n## Purpose\n\nProduce shell scripts that are correct, readable, consistently styled, portable, and safe.\n\n## Overview\n\n- Google's shell script style guide conventions\n- Bash-first\n- `set -euo pipefail` for Bash executables; explicit status checks for POSIX sh\n- snake_case function names; optional library namespaces\n- explicit error handling on every failure path\n- timestamped logging\n- zero shellcheck warnings\n- shfmt formatting\n\n## Operating Rules\n\n1. No script is done until shellcheck is clean at all severities with optional checks enabled (`-S style -o all`) or every remaining finding carries an inline, reasoned suppression.\n2. Always run `shfmt` last; never commit hand formatting that contradicts it.\n3. When editing, match the file's existing style; do a full restyle only on request.\n4. Never invent a shellcheck code or shfmt flag. Cite only codes shellcheck itself printed, and verify flags with `shellcheck --list-optional`, `shfmt --help`, or the man page; use the wiki only when network is available.\n5. Prefer builtins over subprocesses; no `eval`; no aliases in scripts; no SUID\u002FSGID bits.\n6. Every script handles errors explicitly and logs with levels to stderr — no silent failures, no bare `echo` for diagnostics.\n7. Keep this file's core stable; variant-specific or lengthy guidance belongs in `references\u002F`.\n8. Use plain `snake_case` function names in standalone scripts, regardless of script size. Do not prefix functions with the script name. Bash libraries may use `library_name::function_name` to avoid collisions; POSIX libraries use an underscore prefix such as `library_name_function_name`. Avoid colon-delimited names in interactive completion functions.\n\n## Deviations from the Google Shell Style Guide\n\nThis skill follows Google's guide except where listed here. Each deviation is deliberate.\n\n| Google says | This skill does | Why |\n| --- | --- | --- |\n| Executables start with `#!\u002Fbin\u002Fbash` | `#!\u002Fusr\u002Fbin\u002Fenv bash` when macOS or an unknown target is in scope; `#!\u002Fbin\u002Fbash` for Linux-only | `\u002Fbin\u002Fbash` is bash 3.2 on macOS, and bash is often elsewhere (Homebrew, NixOS). See `references\u002Fportability.md` |\n| Bash only, no need for POSIX compatibility | A POSIX `sh` track (`references\u002Fportable-shell.md`) | Some targets (containers, BusyBox, legacy systems) only have `sh` |\n| Rewrite in another language past ~100 lines | Advisory: tell the user once, then write the best shell to the standard | Shell is sometimes the only option, so this is not a blocker |\n| Shell is for small utilities | Ships larger helpers (`init-script.sh` scaffold, `references\u002Flayered-config.md`) | They serve real tools that must stay in shell; keep them to what the script needs |\n| `set` options, `err()` helper | Adds `set -euo pipefail`, an `ERR` trap, leveled `info`\u002F`warn`\u002F`err`\u002F`debug` helpers, `shellcheck -o all` | Stricter failure handling; Google's rules still hold |\n| Prefer builtins over external commands | Scaffold's `log` uses `printf '%(...)T'` on bash 4.2+ and falls back to `date` below that | macOS ships bash 3.2 |\n| `echo` in examples | `printf '%s\\n'` for variable data | `echo` handles `-n`, `-e` and backslashes differently across shells |\n\n## Workflow\n\nThe scaffold and strict-mode instructions below apply to Bash targets. For POSIX sh, use [Portable shell decisions](references\u002Fportable-shell.md). Override the configuration template's `shell=bash` setting with `shellcheck -s sh` or the applicable project setting.\n\n1. **Classify the target.** Executable or library? Bash (default) or POSIX sh?\n   - Executables: no extension preferred (or `.sh` if a build rule renames it); `#!\u002Fusr\u002Fbin\u002Fenv bash` when macOS is in scope, `#!\u002Fbin\u002Fbash` for Linux-only scripts (see `references\u002Fportability.md`); executable bit set.\n   - Libraries: must end in `.sh`, must not be executable, must carry function header comments.\n   - POSIX sh (`#!\u002Fbin\u002Fsh`): read [Portable shell decisions](references\u002Fportable-shell.md). Record the minimum POSIX edition, shell versions, and utility implementations. Use `shellcheck -s sh` and `shfmt -ln=posix`; run `scripts\u002Fcheckbashisms`, and test with `dash` plus the deployment shells (see `references\u002Fdash-and-posh.md`). The Bash scaffold, `ERR` trap, arrays, and `local` conventions do not apply. Do not assume POSIX.1-2024 additions are available on older shells.\n   - Extensionless scripts are detected by shfmt via shebang; EditorConfig `[[bash]]` sections cover them (see `references\u002Ftools.md`).\n2. **Scaffold or open.** New script: generate from `scripts\u002Finit-script.sh` (ships the `log` core with color-on-tty + `NO_COLOR` + `QUIET`, `info`\u002F`warn`\u002F`err`\u002F`debug`, `die` (the `EXIT` trap does the cleanup), the `ERR`-trap\u002F`__on_error` pattern from `references\u002Fbash-strict-mode.md`, `require_vars`, `cleanup` trap, `check_preconditions`, `run_cmd` with `-n` dry-run, `getopts` + `usage()`). Existing script: keep its established style for the edit; apply the full standard only to new files or when a restyle was requested. If the project lacks `.shellcheckrc`\u002F`.editorconfig`, install the templates with `scripts\u002Finit-configs.sh` (copies the `.editorconfig` and `.shellcheckrc` templates into the project root, never overwrites).\n3. **Write to the standard.** Headline rules:\n   - Functions and variables: lowercase `snake_case` (functions verb-first). Constants and exported variables: `UPPER_SNAKE`, declared at the top; use `readonly`\u002F`export`, not `declare -xr`; make a runtime-set constant `readonly` immediately. Mutable script state stays lowercase. Pick names from `references\u002Ffunction-names.txt` and `references\u002Fvariable-names.txt` before inventing new ones.\n   - One job per function (Single Responsibility): if it needs \"and\" to describe or has no short verb-first name, split it. `main` only coordinates.\n   - Separate output from status: data on stdout (`printf '%s\\n'`), success\u002Ffailure via `return` (0-255). Never return a string through `return`.\n   - Scope every function variable with `local`; declare separately from a command-substitution assignment (`local x` then `x=\"$(cmd)\"`), never `local x=\"$(cmd)\"`.\n   - Expansion: quote everything; brace named variables (`\"${var}\"`); do not brace single-character specials or positionals (`\"$1\"`, `\"$?\"`, `\"$@\"`) except `${10}`+ or to avoid ambiguity.\n   - Use `[[ ]]`, `$( )`, `(( ))`; quote every expansion; use arrays for argument lists.\n   - Parse options with `getopts` plus `usage()`.\n   - Handle every failure path explicitly: no silent failures, errors to stderr, leveled timestamped logs with debug behind a flag, temp artifacts cleaned up with `trap`.\n   - End the script with a bare `main \"$@\"`. Never wrap it in `||`\u002F`&&`\u002F`if`: that suppresses `set -e` and the `ERR` trap inside `main`.\n\n   Read the matching reference when the situation applies:\n   - Always: `references\u002Fstyle-cheatsheet.md` (Google guide, condensed, including portability, error handling, logging), `references\u002Ffunction-naming.md`, `references\u002Fbash-strict-mode.md` (full strict-mode header and `ERR`-trap pattern).\n   - Script takes configuration: `references\u002Flayered-config.md` (eval-free; defaults \u003C file \u003C env \u003C args).\n   - Looking for a ready-made solution: `references\u002Fpatterns.md`.\n   - Choosing a shebang or target: `references\u002Fportability.md`.\n   - Handling untrusted input: `references\u002Fsecurity.md`.\n4. **Lint.** Run `scripts\u002Flint.sh` (shellcheck `-x -S style -o all` + `shfmt -d`). Fix every finding. A suppression is allowed only as `# shellcheck disable=SCxxxx # \u003Creason>` with a real reason; look codes up on the shellcheck wiki, never invent them. `references\u002Fbad-code-examples.md` is the gallery of patterns shellcheck catches.\n5. **Format.** Run `scripts\u002Fformat.sh` (`shfmt -i 2 -ci -bn -s -w`), honoring any `.editorconfig`. Never hand-format around shfmt's output.\n6. **Verify.** `shfmt` parsing doubles as a strict syntax check (stricter than `bash -n`). Smoke-run with representative inputs, including failure cases (missing args, missing commands, bad paths); use `bashdb` for interactive debugging when behavior is wrong. For scripts with real logic, add `bats` tests — see `references\u002Ftesting.md`.\n7. **Report** per the Output Contract.\n\n### Review mode\n\nWhen asked to review (not change) a script: run `scripts\u002Flint.sh` on it, walk the Output Contract as a checklist against the untouched file, and report findings ordered by severity (correctness\u002Fsafety first, then portability, then style), each with a `file:line` reference and the concrete fix. Do not edit the file. If the script is vendored third-party code, say so and apply the vendored-code rule from `references\u002Ftools.md` instead of the full standard.\n\n## Output Contract\n\n- Path(s) of every script created or changed.\n- shellcheck result: clean, or each remaining code listed with its justification.\n- shfmt: flags applied; any region intentionally left unformatted and why.\n- Function design: each function has one job; data on stdout, status via `return`; every function variable is `local`.\n- Naming audit: plain snake_case names in standalone scripts; optional library namespaces and private prefixes where appropriate.\n- Portability: bashisms flagged for POSIX targets; no unchecked GNU-only assumptions.\n- Error handling: every failure path handled explicitly; `cd` guarded; destructive commands guarded (`${var:?}`); traps clean up temp files.\n- Logging: leveled (INFO\u002FWARN\u002FERROR\u002FDEBUG), timestamped, stderr; stdout reserved for the script's real output; no bare `echo` diagnostics.\n- Testing: smoke-run cases covered; `bats` tests added\u002Fupdated for logic-bearing scripts (see `references\u002Ftesting.md`).\n- Short changelog: what changed and what it was tested with.\n\n## Tooling\n\n- `shellcheck -x -S style -o all \u003Cfile>` — linter and static analysis; `-x` follows `source`; severities: error, warning, info, style. Look up codes at \u003Chttps:\u002F\u002Fgithub.com\u002Fkoalaman\u002Fshellcheck\u002Fwiki> ; also \u003Chttps:\u002F\u002Fwww.shellcheck.net\u002F>.\n- `.shellcheckrc` template in `assets\u002Fshellcheckrc`: `shell=bash`, `severity=style`, `external-sources=true`, `enable=all` (strict optional checks), `SC1091` disabled with reason. Install with `scripts\u002Finit-configs.sh`.\n- `shfmt -i 2 -ci -bn -s -w \u003Cfile>` — format to the Google-like preset (2-space indent, indented case branches, binary operators start the line, simplify). `-d` shows diffs without writing (CI-friendly); `-l` lists files needing formatting; `-f .` finds shell files recursively; `-ln=bash|posix` forces the dialect.\n- `.editorconfig` — shfmt reads it; use `[*.sh]` plus `[[bash]]` for extensionless scripts. Install the template with `scripts\u002Finit-configs.sh` (source: `assets\u002Feditorconfig`).\n- `scripts\u002Fcheckbashisms` — vendored copy (devscripts `main`, GPL-2.0+; see README \"Third-party code\") of the Debian devscripts bashism checker (Perl). Run it on `#!\u002Fbin\u002Fsh` scripts to catch bash-only constructs; see `references\u002Ftools.md` for the distro packages.\n- `bashdb` — interactive bash debugger (`bashdb script.sh`).\n- `bash-language-server` — editor integration (diagnostics, completion).\n- Install commands (apt\u002Fapt-get\u002Fyum\u002Fdnf\u002Frpm-ostree\u002Fbrew\u002FGo): see `references\u002Ftools.md`.\n\n## References\n\n- Google Shell Style Guide — \u003Chttps:\u002F\u002Fgoogle.github.io\u002Fstyleguide\u002Fshellguide.html>\n- BashPitfalls — \u003Chttps:\u002F\u002Fmywiki.wooledge.org\u002FBashPitfalls> ; BashFAQ — \u003Chttps:\u002F\u002Fmywiki.wooledge.org\u002FBashFAQ>\n- TLDP Advanced Bash-Scripting Guide — \u003Chttp:\u002F\u002Ftldp.org\u002FLDP\u002Fabs\u002Fhtml\u002F>\n- pure-bash-bible — \u003Chttps:\u002F\u002Fgithub.com\u002Fdylanaraps\u002Fpure-bash-bible>\n","# Shell Script Pro\n\n## Purpose\n\nProduce shell scripts that are correct, readable, consistently styled, portable, and safe.\n\n## Overview\n\n- Google's shell script style guide conventions\n- Bash-first\n- `set -euo pipefail` for Bash executables; explicit status checks for POSIX sh\n- snake_case function names; optional library namespaces\n- explicit error handling on every failure path\n- timestamped logging\n- zero shellcheck warnings\n- shfmt formatting\n\n## Operating Rules\n\n1. No script is done until shellcheck is clean at all severities with optional checks enabled (`-S style -o all`) or every remaining finding carries an inline, reasoned suppression.\n2. Always run `shfmt` last; never commit hand formatting that contradicts it.\n3. When editing, match the file's existing style; do a full restyle only on request.\n4. Never invent a shellcheck code or shfmt flag. Cite only codes shellcheck itself printed, and verify flags with `shellcheck --list-optional`, `shfmt --help`, or the man page; use the wiki only when network is available.\n5. Prefer builtins over subprocesses; no `eval`; no aliases in scripts; no SUID\u002FSGID bits.\n6. Every script handles errors explicitly and logs with levels to stderr — no silent failures, no bare `echo` for diagnostics.\n7. Keep this file's core stable; variant-specific or lengthy guidance belongs in `references\u002F`.\n8. Use plain `snake_case` function names in standalone scripts, regardless of script size. Do not prefix functions with the script name. Bash libraries may use `library_name::function_name` to avoid collisions; POSIX libraries use an underscore prefix such as `library_name_function_name`. Avoid colon-delimited names in interactive completion functions.\n\n## Deviations from the Google Shell Style Guide\n\nThis skill follows Google's guide except where listed here. Each deviation is deliberate.\n\n| Google says | This skill does | Why |\n| --- | --- | --- |\n| Executables start with `#!\u002Fbin\u002Fbash` | `#!\u002Fusr\u002Fbin\u002Fenv bash` when macOS or an unknown target is in scope; `#!\u002Fbin\u002Fbash` for Linux-only | `\u002Fbin\u002Fbash` is bash 3.2 on macOS, and bash is often elsewhere (Homebrew, NixOS). See `references\u002Fportability.md` |\n| Bash only, no need for POSIX compatibility | A POSIX `sh` track (`references\u002Fportable-shell.md`) | Some targets (containers, BusyBox, legacy systems) only have `sh` |\n| Rewrite in another language past ~100 lines | Advisory: tell the user once, then write the best shell to the standard | Shell is sometimes the only option, so this is not a blocker |\n| Shell is for small utilities | Ships larger helpers (`init-script.sh` scaffold, `references\u002Flayered-config.md`) | They serve real tools that must stay in shell; keep them to what the script needs |\n| `set` options, `err()` helper | Adds `set -euo pipefail`, an `ERR` trap, leveled `info`\u002F`warn`\u002F`err`\u002F`debug` helpers, `shellcheck -o all` | Stricter failure handling; Google's rules still hold |\n| Prefer builtins over external commands | Scaffold's `log` uses `printf '%(...)T'` on bash 4.2+ and falls back to `date` below that | macOS ships bash 3.2 |\n| `echo` in examples | `printf '%s\\n'` for variable data | `echo` handles `-n`, `-e` and backslashes differently across shells |\n\n## Workflow\n\nThe scaffold and strict-mode instructions below apply to Bash targets. For POSIX sh, use [Portable shell decisions](references\u002Fportable-shell.md). Override the configuration template's `shell=bash` setting with `shellcheck -s sh` or the applicable project setting.\n\n1. **Classify the target.** Executable or library? Bash (default) or POSIX sh?\n   - Executables: no extension preferred (or `.sh` if a build rule renames it); `#!\u002Fusr\u002Fbin\u002Fenv bash` when macOS is in scope, `#!\u002Fbin\u002Fbash` for Linux-only scripts (see `references\u002Fportability.md`); executable bit set.\n   - Libraries: must end in `.sh`, must not be executable, must carry function header comments.\n   - POSIX sh (`#!\u002Fbin\u002Fsh`): read [Portable shell decisions](references\u002Fportable-shell.md). Record the minimum POSIX edition, shell versions, and utility implementations. Use `shellcheck -s sh` and `shfmt -ln=posix`; run `scripts\u002Fcheckbashisms`, and test with `dash` plus the deployment shells (see `references\u002Fdash-and-posh.md`). The Bash scaffold, `ERR` trap, arrays, and `local` conventions do not apply. Do not assume POSIX.1-2024 additions are available on older shells.\n   - Extensionless scripts are detected by shfmt via shebang; EditorConfig `[[bash]]` sections cover them (see `references\u002Ftools.md`).\n2. **Scaffold or open.** New script: generate from `scripts\u002Finit-script.sh` (ships the `log` core with color-on-tty + `NO_COLOR` + `QUIET`, `info`\u002F`warn`\u002F`err`\u002F`debug`, `die` (the `EXIT` trap does the cleanup), the `ERR`-trap\u002F`__on_error` pattern from `references\u002Fbash-strict-mode.md`, `require_vars`, `cleanup` trap, `check_preconditions`, `run_cmd` with `-n` dry-run, `getopts` + `usage()`). Existing script: keep its established style for the edit; apply the full standard only to new files or when a restyle was requested. If the project lacks `.shellcheckrc`\u002F`.editorconfig`, install the templates with `scripts\u002Finit-configs.sh` (copies the `.editorconfig` and `.shellcheckrc` templates into the project root, never overwrites).\n3. **Write to the standard.** Headline rules:\n   - Functions and variables: lowercase `snake_case` (functions verb-first). Constants and exported variables: `UPPER_SNAKE`, declared at the top; use `readonly`\u002F`export`, not `declare -xr`; make a runtime-set constant `readonly` immediately. Mutable script state stays lowercase. Pick names from `references\u002Ffunction-names.txt` and `references\u002Fvariable-names.txt` before inventing new ones.\n   - One job per function (Single Responsibility): if it needs \"and\" to describe or has no short verb-first name, split it. `main` only coordinates.\n   - Separate output from status: data on stdout (`printf '%s\\n'`), success\u002Ffailure via `return` (0-255). Never return a string through `return`.\n   - Scope every function variable with `local`; declare separately from a command-substitution assignment (`local x` then `x=\"$(cmd)\"`), never `local x=\"$(cmd)\"`.\n   - Expansion: quote everything; brace named variables (`\"${var}\"`); do not brace single-character specials or positionals (`\"$1\"`, `\"$?\"`, `\"$@\"`) except `${10}`+ or to avoid ambiguity.\n   - Use `[[ ]]`, `$( )`, `(( ))`; quote every expansion; use arrays for argument lists.\n   - Parse options with `getopts` plus `usage()`.\n   - Handle every failure path explicitly: no silent failures, errors to stderr, leveled timestamped logs with debug behind a flag, temp artifacts cleaned up with `trap`.\n   - End the script with a bare `main \"$@\"`. Never wrap it in `||`\u002F`&&`\u002F`if`: that suppresses `set -e` and the `ERR` trap inside `main`.\n\n   Read the matching reference when the situation applies:\n   - Always: `references\u002Fstyle-cheatsheet.md` (Google guide, condensed, including portability, error handling, logging), `references\u002Ffunction-naming.md`, `references\u002Fbash-strict-mode.md` (full strict-mode header and `ERR`-trap pattern).\n   - Script takes configuration: `references\u002Flayered-config.md` (eval-free; defaults \u003C file \u003C env \u003C args).\n   - Looking for a ready-made solution: `references\u002Fpatterns.md`.\n   - Choosing a shebang or target: `references\u002Fportability.md`.\n   - Handling untrusted input: `references\u002Fsecurity.md`.\n4. **Lint.** Run `scripts\u002Flint.sh` (shellcheck `-x -S style -o all` + `shfmt -d`). Fix every finding. A suppression is allowed only as `# shellcheck disable=SCxxxx # \u003Creason>` with a real reason; look codes up on the shellcheck wiki, never invent them. `references\u002Fbad-code-examples.md` is the gallery of patterns shellcheck catches.\n5. **Format.** Run `scripts\u002Fformat.sh` (`shfmt -i 2 -ci -bn -s -w`), honoring any `.editorconfig`. Never hand-format around shfmt's output.\n6. **Verify.** `shfmt` parsing doubles as a strict syntax check (stricter than `bash -n`). Smoke-run with representative inputs, including failure cases (missing args, missing commands, bad paths); use `bashdb` for interactive debugging when behavior is wrong. For scripts with real logic, add `bats` tests — see `references\u002Ftesting.md`.\n7. **Report** per the Output Contract.\n\n### Review mode\n\nWhen asked to review (not change) a script: run `scripts\u002Flint.sh` on it, walk the Output Contract as a checklist against the untouched file, and report findings ordered by severity (correctness\u002Fsafety first, then portability, then style), each with a `file:line` reference and the concrete fix. Do not edit the file. If the script is vendored third-party code, say so and apply the vendored-code rule from `references\u002Ftools.md` instead of the full standard.\n\n## Output Contract\n\n- Path(s) of every script created or changed.\n- shellcheck result: clean, or each remaining code listed with its justification.\n- shfmt: flags applied; any region intentionally left unformatted and why.\n- Function design: each function has one job; data on stdout, status via `return`; every function variable is `local`.\n- Naming audit: plain snake_case names in standalone scripts; optional library namespaces and private prefixes where appropriate.\n- Portability: bashisms flagged for POSIX targets; no unchecked GNU-only assumptions.\n- Error handling: every failure path handled explicitly; `cd` guarded; destructive commands guarded (`${var:?}`); traps clean up temp files.\n- Logging: leveled (INFO\u002FWARN\u002FERROR\u002FDEBUG), timestamped, stderr; stdout reserved for the script's real output; no bare `echo` diagnostics.\n- Testing: smoke-run cases covered; `bats` tests added\u002Fupdated for logic-bearing scripts (see `references\u002Ftesting.md`).\n- Short changelog: what changed and what it was tested with.\n\n## Tooling\n\n- `shellcheck -x -S style -o all \u003Cfile>` — linter and static analysis; `-x` follows `source`; severities: error, warning, info, style. Look up codes at \u003Chttps:\u002F\u002Fgithub.com\u002Fkoalaman\u002Fshellcheck\u002Fwiki> ; also \u003Chttps:\u002F\u002Fwww.shellcheck.net\u002F>.\n- `.shellcheckrc` template in `assets\u002Fshellcheckrc`: `shell=bash`, `severity=style`, `external-sources=true`, `enable=all` (strict optional checks), `SC1091` disabled with reason. Install with `scripts\u002Finit-configs.sh`.\n- `shfmt -i 2 -ci -bn -s -w \u003Cfile>` — format to the Google-like preset (2-space indent, indented case branches, binary operators start the line, simplify). `-d` shows diffs without writing (CI-friendly); `-l` lists files needing formatting; `-f .` finds shell files recursively; `-ln=bash|posix` forces the dialect.\n- `.editorconfig` — shfmt reads it; use `[*.sh]` plus `[[bash]]` for extensionless scripts. Install the template with `scripts\u002Finit-configs.sh` (source: `assets\u002Feditorconfig`).\n- `scripts\u002Fcheckbashisms` — vendored copy (devscripts `main`, GPL-2.0+; see README \"Third-party code\") of the Debian devscripts bashism checker (Perl). Run it on `#!\u002Fbin\u002Fsh` scripts to catch bash-only constructs; see `references\u002Ftools.md` for the distro packages.\n- `bashdb` — interactive bash debugger (`bashdb script.sh`).\n- `bash-language-server` — editor integration (diagnostics, completion).\n- Install commands (apt\u002Fapt-get\u002Fyum\u002Fdnf\u002Frpm-ostree\u002Fbrew\u002FGo): see `references\u002Ftools.md`.\n\n## References\n\n- Google Shell Style Guide — \u003Chttps:\u002F\u002Fgoogle.github.io\u002Fstyleguide\u002Fshellguide.html>\n- BashPitfalls — \u003Chttps:\u002F\u002Fmywiki.wooledge.org\u002FBashPitfalls> ; BashFAQ — \u003Chttps:\u002F\u002Fmywiki.wooledge.org\u002FBashFAQ>\n- TLDP Advanced Bash-Scripting Guide — \u003Chttp:\u002F\u002Ftldp.org\u002FLDP\u002Fabs\u002Fhtml\u002F>\n- pure-bash-bible — \u003Chttps:\u002F\u002Fgithub.com\u002Fdylanaraps\u002Fpure-bash-bible>\n",{"name":5,"description":7},"main","62177b0f31651c18aefb738bccb54168b8a5a982","plugins\u002Fbuilder\u002Fskills\u002Fshell-script-pro","https:\u002F\u002Fgithub.com\u002Fthimslugga\u002Fagent-plugins","https:\u002F\u002Fgithub.com\u002Fthimslugga","https:\u002F\u002Fadamkaminski.com","I am interested in Linux, macOS, Python, Golang, Rust and Networking.\r\n\r\nOpinions expressed are my own and may not be the views of my employer.","2026-11-11 02:10:30",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add thimslugga\u002Fagent-plugins --skill shell-script-pro",{"tool":38,"command":39},"bunx","bunx skills add thimslugga\u002Fagent-plugins --skill shell-script-pro",{"tool":41,"command":42},"pnpm","pnpm dlx skills add thimslugga\u002Fagent-plugins --skill shell-script-pro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthimslugga\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbuilder\u002Fskills\u002Fshell-script-pro\u002FSKILL.md",true,[46,52,58,62,66,70,74,78,82,86,90,94,98,102,106,110,114,118,122,126,130,134,138,142,146,152,156,160,164],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",132,"https:\u002F\u002Fgithub.com\u002Fthimslugga\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbuilder\u002Fskills\u002Fshell-script-pro\u002Fagents\u002Fopenai.yaml",{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"assets\u002Fbats.snippets","ASSET","资产文件",779,"https:\u002F\u002Fgithub.com\u002Fthimslugga\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbuilder\u002Fskills\u002Fshell-script-pro\u002Fassets\u002Fbats.snippets",{"path":59,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":60,"sourceHtmlUrl":61},"assets\u002Feditorconfig",1418,"https:\u002F\u002Fgithub.com\u002Fthimslugga\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbuilder\u002Fskills\u002Fshell-script-pro\u002Fassets\u002Feditorconfig",{"path":63,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":64,"sourceHtmlUrl":65},"assets\u002Fshellcheckrc",1001,"https:\u002F\u002Fgithub.com\u002Fthimslugga\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbuilder\u002Fskills\u002Fshell-script-pro\u002Fassets\u002Fshellcheckrc",{"path":67,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":68,"sourceHtmlUrl":69},"README.md",5647,"https:\u002F\u002Fgithub.com\u002Fthimslugga\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbuilder\u002Fskills\u002Fshell-script-pro\u002FREADME.md",{"path":71,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fbad-code-examples.md",7473,"https:\u002F\u002Fgithub.com\u002Fthimslugga\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbuilder\u002Fskills\u002Fshell-script-pro\u002Freferences\u002Fbad-code-examples.md",{"path":75,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fbash-strict-mode.md",6812,"https:\u002F\u002Fgithub.com\u002Fthimslugga\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbuilder\u002Fskills\u002Fshell-script-pro\u002Freferences\u002Fbash-strict-mode.md",{"path":79,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fbashism.md",13183,"https:\u002F\u002Fgithub.com\u002Fthimslugga\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbuilder\u002Fskills\u002Fshell-script-pro\u002Freferences\u002Fbashism.md",{"path":83,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fcoreutils-gotchas.md",19697,"https:\u002F\u002Fgithub.com\u002Fthimslugga\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbuilder\u002Fskills\u002Fshell-script-pro\u002Freferences\u002Fcoreutils-gotchas.md",{"path":87,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fdash-and-posh.md",1947,"https:\u002F\u002Fgithub.com\u002Fthimslugga\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbuilder\u002Fskills\u002Fshell-script-pro\u002Freferences\u002Fdash-and-posh.md",{"path":91,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Ffunction-names.txt",7106,"https:\u002F\u002Fgithub.com\u002Fthimslugga\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbuilder\u002Fskills\u002Fshell-script-pro\u002Freferences\u002Ffunction-names.txt",{"path":95,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Ffunction-naming.md",2531,"https:\u002F\u002Fgithub.com\u002Fthimslugga\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbuilder\u002Fskills\u002Fshell-script-pro\u002Freferences\u002Ffunction-naming.md",{"path":99,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Flayered-config.md",12687,"https:\u002F\u002Fgithub.com\u002Fthimslugga\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbuilder\u002Fskills\u002Fshell-script-pro\u002Freferences\u002Flayered-config.md",{"path":103,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fpatterns.md",7890,"https:\u002F\u002Fgithub.com\u002Fthimslugga\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbuilder\u002Fskills\u002Fshell-script-pro\u002Freferences\u002Fpatterns.md",{"path":107,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Fportability.md",6267,"https:\u002F\u002Fgithub.com\u002Fthimslugga\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbuilder\u002Fskills\u002Fshell-script-pro\u002Freferences\u002Fportability.md",{"path":111,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":112,"sourceHtmlUrl":113},"references\u002Fportable-shell.md",9990,"https:\u002F\u002Fgithub.com\u002Fthimslugga\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbuilder\u002Fskills\u002Fshell-script-pro\u002Freferences\u002Fportable-shell.md",{"path":115,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":116,"sourceHtmlUrl":117},"references\u002Fpure-bash-bible.md",45194,"https:\u002F\u002Fgithub.com\u002Fthimslugga\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbuilder\u002Fskills\u002Fshell-script-pro\u002Freferences\u002Fpure-bash-bible.md",{"path":119,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":120,"sourceHtmlUrl":121},"references\u002Fpure-sh-bible.md",24476,"https:\u002F\u002Fgithub.com\u002Fthimslugga\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbuilder\u002Fskills\u002Fshell-script-pro\u002Freferences\u002Fpure-sh-bible.md",{"path":123,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":124,"sourceHtmlUrl":125},"references\u002Fsecurity.md",4512,"https:\u002F\u002Fgithub.com\u002Fthimslugga\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbuilder\u002Fskills\u002Fshell-script-pro\u002Freferences\u002Fsecurity.md",{"path":127,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":128,"sourceHtmlUrl":129},"references\u002Fsh-tricks.md",23404,"https:\u002F\u002Fgithub.com\u002Fthimslugga\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbuilder\u002Fskills\u002Fshell-script-pro\u002Freferences\u002Fsh-tricks.md",{"path":131,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":132,"sourceHtmlUrl":133},"references\u002Fstyle-cheatsheet.md",13123,"https:\u002F\u002Fgithub.com\u002Fthimslugga\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbuilder\u002Fskills\u002Fshell-script-pro\u002Freferences\u002Fstyle-cheatsheet.md",{"path":135,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":136,"sourceHtmlUrl":137},"references\u002Ftesting.md",1780,"https:\u002F\u002Fgithub.com\u002Fthimslugga\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbuilder\u002Fskills\u002Fshell-script-pro\u002Freferences\u002Ftesting.md",{"path":139,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":140,"sourceHtmlUrl":141},"references\u002Ftools.md",7046,"https:\u002F\u002Fgithub.com\u002Fthimslugga\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbuilder\u002Fskills\u002Fshell-script-pro\u002Freferences\u002Ftools.md",{"path":143,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":144,"sourceHtmlUrl":145},"references\u002Fvariable-names.txt",7400,"https:\u002F\u002Fgithub.com\u002Fthimslugga\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbuilder\u002Fskills\u002Fshell-script-pro\u002Freferences\u002Fvariable-names.txt",{"path":147,"resourceType":148,"resourceTypeDesc":149,"sizeBytes":150,"sourceHtmlUrl":151},"scripts\u002Fcheckbashisms","SCRIPT","脚本",32333,"https:\u002F\u002Fgithub.com\u002Fthimslugga\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbuilder\u002Fskills\u002Fshell-script-pro\u002Fscripts\u002Fcheckbashisms",{"path":153,"resourceType":148,"resourceTypeDesc":149,"sizeBytes":154,"sourceHtmlUrl":155},"scripts\u002Fformat.sh",967,"https:\u002F\u002Fgithub.com\u002Fthimslugga\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbuilder\u002Fskills\u002Fshell-script-pro\u002Fscripts\u002Fformat.sh",{"path":157,"resourceType":148,"resourceTypeDesc":149,"sizeBytes":158,"sourceHtmlUrl":159},"scripts\u002Finit-configs.sh",1409,"https:\u002F\u002Fgithub.com\u002Fthimslugga\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbuilder\u002Fskills\u002Fshell-script-pro\u002Fscripts\u002Finit-configs.sh",{"path":161,"resourceType":148,"resourceTypeDesc":149,"sizeBytes":162,"sourceHtmlUrl":163},"scripts\u002Finit-script.sh",11754,"https:\u002F\u002Fgithub.com\u002Fthimslugga\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbuilder\u002Fskills\u002Fshell-script-pro\u002Fscripts\u002Finit-script.sh",{"path":165,"resourceType":148,"resourceTypeDesc":149,"sizeBytes":166,"sourceHtmlUrl":167},"scripts\u002Flint.sh",2185,"https:\u002F\u002Fgithub.com\u002Fthimslugga\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbuilder\u002Fskills\u002Fshell-script-pro\u002Fscripts\u002Flint.sh",[169,176,183,190,196,203],{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":175,"publishedAt":19},"01M7BSDA3CNHHP07666X3H90CB","shell-script-expert","Use when the user asks \"review this script\", \"write a bash script\", \"fix my shell script\", \"make this script safer\", \"why does this script fail\", \"convert this to a script\", or working with .sh\u002F.bash files, sh\u002Fbash syntax, shellcheck, cronjobs, and bash one-liners.","https:\u002F\u002Fgithub.com\u002Fthimslugga\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fskills\u002Fshell-script-expert\u002FSKILL.md",[],[],{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":182,"publishedAt":19},"01M7BSD6STC24Q13N4J8E0T93X","prose-synthesize","Turn unstructured notes into a structured, actionable plan. Use when given brain dumps, stream-of-consciousness, or scattered thoughts needing order.","https:\u002F\u002Fgithub.com\u002Fthimslugga\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fskills\u002Fprose-synthesize\u002FSKILL.md",[],[],{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":189,"publishedAt":19},"01M7BSD16KRRWFMM3EN1WPK8G3","prose-distill","Condense verbose text to its essence.  Use when asked to condense, tighten, shorten, reduce verbosity, or omit needless words while preserving substance.","https:\u002F\u002Fgithub.com\u002Fthimslugga\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fskills\u002Fprose-distill\u002FSKILL.md",[],[],{"skillNo":191,"name":192,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":195,"publishedAt":19},"01M7BSCYJWSP5VJK3822XRNXR2","mindcraft","https:\u002F\u002Fgithub.com\u002Fthimslugga\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fskills\u002Fmindcraft\u002FSKILL.md",[],[],{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":202,"publishedAt":19},"01M7BSCRQ1GCDCTPNZ3WA3R0JE","learn","Tutor for intellectual understanding: teach how or why something works rather than complete a task or provide an evaluative verdict.\nTrigger for explicit learning requests (teach, explain, ELI5, walkthroughs, quizzes, flashcards, definitions); terse concept prompts; confusion signals; prerequisite or sequencing questions; and conceptual questions about mechanisms, causes, or dynamics.\nDo not trigger for task completion (coding, writing, calculation, or translation), factual or news lookup, personal troubleshooting, resource recommendations, or opinion and interpretive verdicts.","https:\u002F\u002Fgithub.com\u002Fthimslugga\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fskills\u002Flearn\u002FSKILL.md",[],[],{"skillNo":204,"name":205,"nameZh":6,"description":206,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":207,"categories":208,"keywords":209,"publishedAt":19},"01M7BSCNAY02WX6BGDW06Y60D9","deployment-readiness","Use to check deployment readiness of a host.","https:\u002F\u002Fgithub.com\u002Fthimslugga\u002Fagent-plugins\u002Fblob\u002Fmain\u002Fskills\u002Fdeployment-readiness\u002FSKILL.md",[],[]]