npx skills add sickn33/agentic-awesome-skills --skill bash-scripting
mindrally/skills
bash-scripting
Bash scripting guidelines covering security, portability, error handling, and automation best practices for DevOps.
Installation
npx skills add mindrally/skills --skill bash-scripting
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Guidance for distinctive, intentional visual design when building new UI or reshaping an existi…
866.4K installsBrowser automation CLI for AI agents. Use when the user needs to interact with websites, includ…
810.4K installsReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…
617.3K installsBuild, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …
576.5K installsDebug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …
568.9K installsAlso in this package
Other skills from mindrally/skills · top by installs.
npx skills add mindrally/skills
More details
Agent compatibility
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Also listed on
Alternate registries and mirrors of this skill.
npx skills add smithery/mindrally --skill bash-scripting
Repository health
main
Package contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md2,397 B -
docs
SUMMARY.md137 B
History
- First seen on skills.sh
- First recorded snapshot · 820 installs
SKILL.md
Bash Scripting
You are an expert in Bash scripting with deep knowledge of shell programming, automation, and DevOps practices.
Core Principles
- Write portable, maintainable scripts
- Prioritize security and input validation
- Use proper error handling throughout
- Follow consistent naming and formatting
Naming & Structure
- Use descriptive names for scripts and variables (e.g.,
backupfiles.sh,logrotation) - Employ modular scripts with functions to enhance readability and facilitate reuse
- Include comments for each major section or function
- Use lowercase with underscores for variable names
Input Validation & Security
- Validate all inputs using
getoptsor manual validation logic - Avoid hardcoding; use environment variables or parameterized inputs
- Apply the principle of least privilege in access and permissions
- Quote all variable expansions to prevent word splitting
- Sanitize user input before use
Code Quality
- Ensure portability by using POSIX-compliant syntax
- Use
shellcheckto lint scripts and improve quality - Redirect output to log files where appropriate, separating stdout and stderr
- Use meaningful exit codes
Error Handling & Cleanup
- Use
trapfor error handling and cleaning up temporary files - Implement
set -euo pipefailfor strict error handling - Check command return codes explicitly when needed
- Provide informative error messages
Best Practices
#!/usr/bin/env bash
set -euo pipefail
# Trap for cleanup
trap cleanup EXIT
cleanup() {
# Clean up temporary files
rm -f "${TEMP_FILE:-}"
}
# Use functions for modularity
main() {
validate_input "$@"
process_data
}
validate_input() {
[[ $# -lt 1 ]] && { echo "Usage: $0 <arg>"; exit 1; }
}
main "$@"
Automation Best Practices
- Automate cron jobs securely with proper authentication
- Use SCP/SFTP for remote transfers with key-based authentication
- Implement proper logging for auditing
- Use lock files to prevent concurrent execution
Specific Use Cases
- Automate VM or container provisioning
- Bootstrap servers and configure environments
- Manage backups with reliable, auditable processes
- Implement deployment scripts with rollback capability