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

70%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agent/skills/bash-defensive-patterns/SKILL.md

Quality

Discovery

67%

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 good structure with explicit 'Use when' guidance and covers the domain adequately. However, it relies on abstract concepts ('defensive programming techniques', 'fault tolerance') rather than listing concrete actions, and could benefit from more specific trigger terms that users would naturally use when seeking this skill.

Suggestions

Replace abstract 'defensive programming techniques' with concrete actions like 'set strict mode (set -euo pipefail), validate inputs, handle errors gracefully, quote variables safely'

Add more natural trigger terms users might say: 'bash script', 'sh script', 'error handling in bash', 'shellcheck', 'script debugging', 'safe scripting'

Dimension	Reasoning	Score
Specificity	Names the domain (Bash programming, shell scripts) and mentions some contexts (CI/CD pipelines, system utilities), but 'defensive programming techniques' and 'fault tolerance and safety' are abstract rather than concrete actions like 'validate inputs, handle errors, set strict mode'.	2 / 3
Completeness	Clearly answers both what ('Master defensive Bash programming techniques') 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	Includes relevant terms like 'Bash', 'shell scripts', 'CI/CD pipelines', 'system utilities', but misses common variations users might say like 'bash script', 'sh', 'error handling', 'set -e', 'shellcheck', or 'script safety'.	2 / 3
Distinctiveness Conflict Risk	The focus on 'defensive' and 'fault tolerance' provides some distinction, but 'shell scripts' and 'CI/CD pipelines' could overlap with general scripting or CI/CD skills. The defensive/production-grade angle helps but isn't strongly unique.	2 / 3
	Total	9 / 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 content is well-structured and concise, appropriately delegating detailed patterns to a separate playbook. However, it lacks concrete executable examples in the main file and could benefit from at least one copy-paste ready code snippet (like strict mode setup) to demonstrate the patterns before directing users to detailed resources.

Suggestions

Add a minimal executable example showing strict mode setup (e.g., `set -euo pipefail`) directly in the Instructions section

Include a concrete validation checkpoint example in the workflow, such as 'Run shellcheck before execution'

Add one brief code snippet demonstrating safe variable quoting or input validation to make the skill immediately actionable

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 clear 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 guidance to the external playbook rather than providing copy-paste ready snippets in the main file.	2 / 3
Workflow Clarity	The 4-step instruction sequence provides a clear order but lacks validation checkpoints or feedback loops. For scripts involving destructive operations, there's no explicit validate-fix-retry pattern shown.	2 / 3
Progressive Disclosure	Clear overview structure with well-signaled one-level-deep references to the implementation playbook. Content is appropriately split between the overview and detailed resources.	3 / 3
	Total	10 / 12 Passed

Validation

90%

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 — 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: Dokhacgiakhoa/antigravity-ide
Commit: 332e58b

Reviewed: 17 days 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.