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.
45
47%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/bash-defensive-patterns/SKILL.mdQuality
Discovery
75%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description has a solid structure with an explicit 'Use when' clause and a distinctive niche focus on defensive Bash programming. However, it lacks specific concrete actions (e.g., error trapping, input validation, strict mode) and could benefit from more natural trigger terms that users would actually type when seeking this kind of help.
Suggestions
Add specific concrete actions such as 'set error traps, validate inputs, use strict mode (set -euo pipefail), handle signals' to improve specificity.
Include additional natural trigger terms users might say, such as 'error handling', 'bash best practices', 'script safety', 'shellcheck', or 'bash debugging'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain ('defensive Bash programming') and mentions some contexts ('production-grade scripts', 'CI/CD pipelines', 'system utilities') but does not list specific concrete actions like 'set error traps', 'validate inputs', 'handle signals', or 'use strict mode'. | 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 an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'Bash', 'shell scripts', 'CI/CD pipelines', 'fault tolerance', and 'safety', but misses common natural terms users might say such as 'error handling', 'set -e', 'trap', 'shellcheck', 'bash best practices', or 'script debugging'. | 2 / 3 |
Distinctiveness Conflict Risk | The focus on 'defensive Bash programming' with 'fault tolerance and safety' is a clear niche that is unlikely to conflict with general scripting skills, Python skills, or other shell-adjacent skills. The combination of Bash + defensive/production-grade is quite distinctive. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
20%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a thin table of contents with no substantive instructional content. It describes what to do at a very high level but provides zero concrete code examples, patterns, or executable guidance for defensive Bash programming. The referenced playbook file does not exist in the bundle, leaving the skill hollow and non-functional.
Suggestions
Add concrete, executable code examples for core patterns: `set -euo pipefail`, trap handlers, input validation with parameter expansion, and safe file operations.
Replace the vague 4-step instructions with specific, copy-paste-ready templates showing a complete defensive script skeleton.
Either include the referenced `resources/implementation-playbook.md` in the bundle or inline the essential patterns directly in the SKILL.md.
Remove the verbose 'Use this skill when' / 'Do not use this skill when' / 'Limitations' boilerplate and use that token budget for actual technical content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with sections that add little value — 'Use this skill when' and 'Do not use this skill when' lists are overly verbose and largely obvious. The 'Limitations' section restates generic advice Claude already knows. The actual instructional content (4 steps) is extremely thin relative to the total token count. | 1 / 3 |
Actionability | The instructions are vague abstractions ('Enable strict mode and safe defaults', 'Validate inputs, quote variables') with zero concrete code, commands, or examples. There is no executable guidance — no `set -euo pipefail`, no trap examples, no quoting patterns, nothing copy-paste ready. | 1 / 3 |
Workflow Clarity | There is a 4-step sequence listed, which provides some ordering, but the steps are too abstract to be actionable and there are no validation checkpoints or feedback loops. For a skill involving destructive operations and production scripts, the lack of explicit validation steps is a significant gap. | 2 / 3 |
Progressive Disclosure | The skill references `resources/implementation-playbook.md` for detailed content, which is a reasonable one-level-deep reference. However, no bundle files were provided, meaning the referenced file doesn't exist, and the SKILL.md itself contains almost no substantive content — it's essentially an empty shell pointing to a missing resource. | 2 / 3 |
Total | 6 / 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
45bad85
- 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.