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

55%

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

35%

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

The skill is reasonably concise and lays out a clear scope and sequence, but it lacks executable guidance and its sole reference points to a missing file, weakening both actionability and progressive disclosure.

Suggestions

Add concrete, executable examples directly in SKILL.md (e.g., `set -euo pipefail`, a `trap` for cleanup, a quoting example) instead of only abstract directives.

Provide the missing 'resources/implementation-playbook.md' bundle file or remove the broken reference, so progressive disclosure points at real content.

Add explicit validation/verification checkpoints (e.g., 'run `bash -n script.sh` to syntax-check, then run on test input before production') to the workflow for destructive/batch operations.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with no basic-concept over-explanation, but the intro sentence is padded with marketing language ('Comprehensive guidance...', 'ensure reliability') and the 'Use when' bullets overlap, fitting the 'mostly efficient but could be tightened' anchor.	2 / 3
Actionability	The instructions are abstract directives ('Enable strict mode', 'Validate inputs, quote variables', 'Add logging, error traps') with no concrete executable code or commands, and all actionable detail is deferred to a referenced file that is not present in the bundle, matching the 'vague or abstract; no concrete code' anchor.	1 / 3
Workflow Clarity	A four-step sequence is present (confirm environment -> strict mode -> validate/safe -> logging/traps/tests) but there are no explicit validation checkpoints or feedback loops, which caps clarity at 2 for skills involving destructive/batch operations.	2 / 3
Progressive Disclosure	The SKILL.md is appropriately short as an overview and references one external file, but the referenced 'resources/implementation-playbook.md' does not exist in the bundle and there is no 'resources/' directory, so the reference is broken and structure is incomplete.	2 / 3
	Total	7 / 12 Passed

Description

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 is well-structured with third-person voice and explicit what/when guidance, scoring well on completeness and distinctiveness. It could improve by enumerating more concrete actions and broadening trigger-term coverage.

Suggestions

List multiple specific concrete actions (e.g., 'add error traps, enable strict mode, validate inputs') rather than relying on the domain name alone to lift specificity to 3.

Add common natural trigger terms users would say ('bash scripts', 'writing safe shell scripts', 'scripting error handling') alongside the more technical phrasing.

Dimension	Reasoning	Score
Specificity	It names the domain (defensive Bash) and several concrete contexts ('robust shell scripts, CI/CD pipelines, or system utilities') but does not list multiple distinct concrete actions, matching the 'names domain and some actions, but not comprehensive' anchor.	2 / 3
Completeness	It clearly answers both what ('Master defensive Bash programming techniques for production-grade scripts') and when with an explicit 'Use when' clause, matching the top anchor.	3 / 3
Trigger Term Quality	It includes natural terms users would say ('shell scripts', 'CI/CD pipelines', 'system utilities') but leans technical ('defensive Bash programming', 'fault tolerance') and misses common variations like 'bash scripts' or 'writing safe scripts', fitting the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	Defensive Bash for production scripts is a clear niche with distinct triggers and is unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	10 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: rmyndharis/antigravity-skills
Path: skills/bash-defensive-patterns/SKILL.md
Commit: e63f7dd

Reviewed: about 4 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.