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.
86
Quality
81%
Does it follow best practices?
Impact
96%
1.09xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
89%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 well-structured description with an explicit 'Use when' clause and good trigger term coverage for developers seeking robust shell scripting guidance. The main weakness is the lack of specific concrete actions - it describes qualities (defensive, fault-tolerant, safe) rather than listing specific techniques like error handling, input validation, or signal trapping.
Suggestions
Add specific concrete actions to improve specificity, e.g., 'Covers error handling with set -euo pipefail, input validation, signal trapping, safe temporary file handling, and atomic operations.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain ('Bash programming', 'shell scripts', 'CI/CD pipelines', 'system utilities') and mentions 'defensive' techniques with qualities like 'fault tolerance and safety', but doesn't list specific concrete actions like 'validate inputs, handle errors, trap 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 'Use when' clause. | 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', 'production-grade'. These are terms developers naturally use when seeking help with reliable scripting. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focusing specifically on 'defensive' and 'production-grade' Bash scripting with emphasis on 'fault tolerance and safety'. This distinguishes it from general Bash/scripting skills or basic shell tutorials. | 3 / 3 |
Total | 11 / 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 is well-structured and appropriately concise, correctly deferring detailed patterns to an external playbook. However, it lacks inline executable examples (like the actual strict mode snippet `set -euo pipefail`) that would make it immediately actionable. The workflow could benefit from explicit validation steps for the defensive patterns it teaches.
Suggestions
Add a minimal inline code example showing strict mode setup (e.g., `set -euo pipefail`) so the skill is immediately actionable without requiring the external playbook
Include a concrete validation checkpoint in the workflow, such as 'Run shellcheck on your script before execution'
Add one brief input validation example (e.g., checking if a required argument exists) to demonstrate the defensive pattern inline
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of concepts Claude already knows (like what Bash is or why defensive programming matters). Every section serves a purpose without padding. | 3 / 3 |
Actionability | Instructions are present but abstract ('Enable strict mode', 'Validate inputs') without concrete code examples. The skill defers all executable patterns to an external playbook rather than providing copy-paste ready snippets inline. | 2 / 3 |
Workflow Clarity | The 4-step workflow provides a clear sequence, but lacks explicit validation checkpoints or feedback loops. For scripts involving destructive operations, there's no 'validate -> fix -> retry' pattern shown. | 2 / 3 |
Progressive Disclosure | Clean structure with a concise overview and clear one-level-deep reference to the implementation playbook. The 'Use/Do not use' sections help with discovery, and the external resource is well-signaled. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
9c177eb
- 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.