bash-pro
Build Safer Production Bash Scripts
Shell automation often fails through unsafe expansion, weak error handling, and portability gaps. This skill guides defensive Bash design, testing, documentation, and review.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "bash-pro" from https://skillstore.io/skills/sickn33-bash-pro.md and its manifest at https://skillstore.io/api/skills/sickn33-bash-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 "bash-pro". Review a backup script that accepts a destination directory and removes old archives.
Expected outcome:
- High priority: validate the destination against an approved base directory before deletion.
- Add dry-run behavior, restrictive permissions, quoted paths, and cleanup traps.
- Test empty paths, spaces, symbolic links, interrupted runs, and retention boundaries.
Using "bash-pro". Plan quality checks for a Bash command-line utility.
Expected outcome:
The plan covers formatting, static analysis, unit tests, platform checks, help validation, failure cases, and release gates.
Using "bash-pro". Modernize a legacy Bash 3 script for Bash 5.2.
Expected outcome:
The review identifies version-dependent features, migration steps, compatibility checks, regression tests, and a controlled rollout plan.
Security Audit
SafeAll 136 static detections are false positives caused by Markdown code formatting, defensive examples, or reference links. The skill contains no executable files or prompt injection.
Risk Factors
⚙️ External commands (50)
🌐 Network access (13)
📁 Filesystem access (3)
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-bash-pro/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-bash-pro?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-bash-pro?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-bash-pro/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-bash-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). bash-pro security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-bash-pro/audits/5BibTeX citation
@techreport{sickn33-sickn33-bash-pro-2026,
author = {sickn33},
title = {bash-pro security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-bash-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: "bash-pro security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-08-14"
url: "https://skillstore.io/skills/sickn33-bash-pro/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-bash-pro:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Harden Deployment Automation
Review deployment scripts for quoting, cleanup, error propagation, idempotency, and safe handling of operator input.
Build Tested Command-Line Tools
Create maintainable Bash utilities with argument parsing, help output, structured logs, and automated tests.
Standardize CI Shell Checks
Define ShellCheck, shfmt, and Bats checks across supported Bash versions and operating systems.
Try These Prompts
Create a Bash script that [task]. Define inputs, outputs, failure behavior, and a dry-run option. Explain required commands.
Review this Bash script for quoting, input validation, cleanup, pipeline failures, and portability. Rank issues and propose focused corrections: [script]
Create a test strategy for [script]. Include Bats cases, ShellCheck and shfmt checks, supported Bash versions, and CI failure criteria.
Design production Bash automation for [workflow]. Include threat boundaries, idempotency, rollback, observability, dependency checks, concurrency controls, tests, and release validation.
Best Practices
- State inputs, permissions, destructive effects, and target platforms before generating or revising a script.
- Run ShellCheck, formatting checks, and focused tests in an isolated environment before production use.
- Request dry-run behavior and explicit confirmation for deletion, privilege changes, or broad file operations.
Avoid
- Do not execute generated scripts without reviewing paths, variables, dependencies, and command arguments.
- Do not pass untrusted text through eval or construct commands with unsafe string concatenation.
- Do not assume Linux and macOS commands share identical options or output formats.