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.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/bash-defensive-patterns/SKILL.md

Quality

Content

57%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise and sensibly structured for a simple instruction-only skill, but it lacks concrete executable guidance and references a playbook file that is absent from the bundle.

Suggestions

Add at least one concrete defensive snippet, e.g. `set -euo pipefail; trap 'err' ERR`, and an input-validation example, to lift actionability.

Add an explicit validation/verify checkpoint to the workflow (e.g. 'run with `bash -n` and a dry-run before executing for real').

Either create resources/implementation-playbook.md or remove/delay the reference so progressive disclosure points at a real file.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding or explanation of concepts Claude already knows; the only minor redundancy is that 'resources/implementation-playbook.md' is referenced twice with near-identical wording, keeping it just below anchor 5.	4 / 5
Actionability	The numbered steps are high-level directives ('Enable strict mode and safe defaults', 'Validate inputs, quote variables') with no concrete commands or code (e.g. no `set -euo pipefail`, `trap`, or quoting examples); as an instruction-only skill this is partially excusable, but the guidance is more abstract than the specific, executable steps anchor 4 requires.	3 / 5
Workflow Clarity	The four numbered steps give a clear sequence (confirm environment, strict mode, validate/quote, logging/traps/tests), but there are no explicit validation or verification checkpoints and step 4 ('add basic tests') is vague, matching anchor 3 (sequence present but checkpoints implicit).	3 / 5
Progressive Disclosure	The body is a concise overview with a one-level-deep, well-signaled reference to 'resources/implementation-playbook.md', but that referenced file does not exist (no resources/ or bundle directory is present), so the navigation target is broken, which caps the score at anchor 3 rather than rewarding the otherwise good structure.	3 / 5
	Total	13 / 20 Passed

Description

70%Weight 40%Scale 1-5

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 is well-formed: third-person/imperative voice, explicit 'Use when' trigger, and a clear niche. Its main weakness is specificity, listing contexts rather than concrete defensive techniques.

Suggestions

Replace context lists with concrete actions, e.g. 'set strict mode (set -euo pipefail), trap errors, quote variables, validate inputs'.

Add common synonyms/users-phrases like 'bash scripting' or 'shell automation' to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('defensive Bash programming') and a few areas (robust shell scripts, CI/CD pipelines, system utilities), but these are contexts rather than concrete actions like quoting, errexit, or traps, so it stops at anchor 3 and falls short of the comprehensive action list needed for 4.	3 / 5
Completeness	It states what the skill does ('Master defensive Bash programming techniques for production-grade scripts') and explicitly when to use it ('Use when writing robust shell scripts, CI/CD pipelines, or system utilities'), satisfying both; the 'when' is concrete but not as exhaustive as the anchor-5 example.	4 / 5
Trigger Term Quality	Natural trigger terms users would say ('shell scripts', 'CI/CD pipelines', 'system utilities', 'fault tolerance') give good coverage, though common synonyms like 'bash scripting' or 'shell automation' are missing, keeping it at anchor 4 rather than 5.	4 / 5
Distinctiveness Conflict Risk	The 'defensive/production Bash' framing is a fairly distinct niche, though 'shell scripts' is broad enough to overlap with general bash or scripting skills, matching anchor 4 (mostly distinct, minor overlap).	4 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Path: skills/bash-defensive-patterns/SKILL.md
Commit: 1f67c44

Reviewed: about 16 hours ago

Table of Contents

Discovery Implementation Validation

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.