bash-pro

Master of defensive Bash scripting for production automation, CI/CD pipelines, and system utilities. Expert in safe, portable, and testable shell scripts.

Overall
score

33%

Review — 19%

Does it follow best practices?

Validation — 13 / 16 Passed

Validation for skill structure

Install with Tessl CLI

npx tessl i github:sickn33/antigravity-awesome-skills --skill bash-pro

Activation

22%

This description relies heavily on self-promotional language ('Master of', 'Expert in') rather than concrete capabilities. It fails to specify what actions the skill performs and provides no guidance on when Claude should use it. The description would benefit from listing specific actions and adding explicit trigger conditions.

Suggestions

Replace vague expertise claims with specific actions (e.g., 'Write defensive Bash scripts with error handling, create CI/CD pipeline scripts, build portable shell utilities').

Add a 'Use when...' clause with explicit triggers (e.g., 'Use when the user asks for shell scripts, .sh files, Bash automation, or CI/CD pipeline configuration').

Include natural trigger terms users would say: 'bash', 'shell script', '.sh', 'cron', 'automation script', 'pipeline script'.

Dimension	Reasoning	Score
Specificity	Uses vague, abstract language like 'Master of' and 'Expert in' without listing concrete actions. No specific capabilities are described - only broad domains like 'production automation' and 'CI/CD pipelines'.	1 / 3
Completeness	Describes a vague 'what' (Bash scripting expertise) but completely lacks any 'when' guidance. No 'Use when...' clause or explicit triggers for when Claude should select this skill.	1 / 3
Trigger Term Quality	Contains some relevant keywords users might say ('Bash scripting', 'CI/CD pipelines', 'shell scripts') but missing common variations like 'bash script', '.sh files', 'shell commands', 'cron jobs', or specific tools.	2 / 3
Distinctiveness Conflict Risk	Somewhat specific to Bash/shell scripting domain, but 'CI/CD pipelines' and 'system utilities' could overlap with other DevOps or automation skills. The broad framing increases conflict risk.	2 / 3
	Total	6 / 12 Passed

Implementation

15%

This skill is a comprehensive but overwhelming reference document that violates token efficiency principles by including extensive content Claude already knows. It lacks a clear workflow structure, mixing high-level guidance with exhaustive reference material in a single file. The content would benefit significantly from restructuring into a concise overview with progressive disclosure to separate reference files.

Suggestions

Reduce the main skill to under 100 lines focusing on the unique defensive patterns and workflow, moving tool references, advanced techniques, and CI/CD details to separate linked files (e.g., TOOLS.md, ADVANCED.md, CI-CD.md)

Replace the abstract 4-step Instructions with a concrete workflow including validation checkpoints: write script → run ShellCheck → test with Bats → verify on target platforms

Remove explanations of basic Bash concepts Claude already knows (what strict mode does, what ShellCheck is) and focus only on project-specific patterns and non-obvious gotchas

Add a concrete example showing a complete mini-script that demonstrates the defensive patterns in action, rather than scattered isolated snippets

Dimension	Reasoning	Score
Conciseness	Extremely verbose at 300+ lines with extensive explanations of concepts Claude already knows (what strict mode does, basic Bash features, standard tool descriptions). Lists every possible consideration rather than focusing on what's truly unique or non-obvious.	1 / 3
Actionability	Contains many concrete code snippets and commands that are executable, but they're scattered throughout as isolated examples rather than integrated into coherent workflows. The 'Instructions' section is vague (4 abstract steps) while the detailed patterns are buried in long lists.	2 / 3
Workflow Clarity	The 4-step 'Instructions' section is too abstract to be actionable. No clear validation checkpoints or feedback loops for the script development process. The content is organized as reference lists rather than a coherent workflow with explicit verification steps.	1 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files for detailed content. Everything is inline - tool documentation, advanced techniques, CI/CD configs, security patterns - when much of this should be split into separate reference files with clear navigation.	1 / 3
	Total	5 / 12 Passed

Validation

81%

Warnings & errors only

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
description_trigger_hint	Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...')	Warning
metadata_version	'metadata.version' is missing	Warning
license_field	'license' field is missing	Warning

	Total	13 / 16 Passed

Reviewed

20 days ago

Table of Contents

Activation 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.