bash-defensive-patterns
Master defensive Bash programming techniques for production-grade scripts. Use when writing robust shell scripts, CI/CD pipelines, or system utilities requiring fault tolerance and safety.
81
Quality
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./docs/v19.7/configuration/agent/skills_external/antigravity-awesome-skills-main/skills/bash-defensive-patterns/SKILL.mdQuality
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid description with good completeness and trigger term coverage. It clearly states both purpose and usage conditions. The main weakness is lack of specific concrete actions - it describes the approach ('defensive', 'fault tolerance') but not the specific techniques (error handling, input validation, signal trapping).
Suggestions
Add specific concrete actions like 'set strict mode, trap errors, validate inputs, handle signals' to improve specificity
Consider adding more distinctive triggers like 'set -euo pipefail', 'error handling', or 'shellcheck' to reduce potential overlap with general shell scripting skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain ('Bash programming', 'shell scripts', 'CI/CD pipelines') and mentions 'defensive techniques' and 'fault tolerance', but doesn't list specific concrete actions like 'set error traps', 'validate inputs', or 'handle signals'. | 2 / 3 |
Completeness | Clearly answers both what ('Master defensive Bash programming techniques for production-grade scripts') and when ('Use when writing robust shell scripts, CI/CD pipelines, or system utilities requiring fault tolerance and safety') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'Bash', 'shell scripts', 'CI/CD pipelines', 'system utilities', 'robust', 'fault tolerance', 'safety'. These are terms users naturally use when seeking help with production shell scripting. | 3 / 3 |
Distinctiveness Conflict Risk | While 'defensive Bash' and 'fault tolerance' provide some distinction, this could overlap with general Bash/shell scripting skills or CI/CD skills. The 'defensive' and 'production-grade' qualifiers help but aren't strongly unique triggers. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill demonstrates good structure and appropriate brevity, correctly delegating detailed patterns to a separate playbook. However, the main content lacks concrete, executable examples of defensive patterns - even a single `set -euo pipefail` snippet would significantly improve actionability. The workflow could benefit from explicit validation steps given the potentially destructive nature of shell scripts.
Suggestions
Add a minimal executable example showing core defensive patterns (e.g., strict mode header with `set -euo pipefail`, a basic trap, and variable quoting)
Include a validation checkpoint in the workflow, such as 'Run with `bash -n script.sh` to syntax-check before execution'
Add one concrete input validation example showing how to safely handle user-provided arguments
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of what Bash is or basic programming concepts. Every section serves a purpose and the instructions are appropriately brief, delegating details to the referenced playbook. | 3 / 3 |
Actionability | Instructions are clear but abstract - 'Enable strict mode', 'Validate inputs', 'Add logging' lack concrete code examples. No executable snippets showing actual defensive patterns like `set -euo pipefail` or trap syntax are provided inline. | 2 / 3 |
Workflow Clarity | The 4-step workflow provides a clear sequence but lacks validation checkpoints or feedback loops. For scripts involving potentially destructive operations, there's no explicit verify-before-proceeding guidance beyond the brief Safety section. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview and clear one-level-deep reference to the implementation playbook. The 'Use this skill when' and 'Do not use' sections provide good scoping, and detailed content is appropriately delegated. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- duclm1x1/Dive-Ai
- Commit
20ba150
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.