bash-pro

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

Quality

18%

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 ./docs/v19.7/configuration/agent/skills_external/antigravity-awesome-skills-main/skills/bash-pro/SKILL.md

Quality

Discovery

22%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description relies heavily on self-promotional language ('Master of', 'Expert in') rather than describing concrete capabilities. It fails to provide any guidance on when Claude should select this skill and lacks specific actionable verbs describing what the skill actually does.

Suggestions

Replace vague claims with specific actions: 'Write defensive Bash scripts with error handling, create CI/CD pipeline scripts, build portable shell utilities, debug shell scripts'

Add explicit trigger guidance: 'Use when the user asks about Bash scripts, .sh files, shell automation, cron jobs, or CI/CD shell commands'

Remove first-person promotional language ('Master of', 'Expert in') and use third-person action verbs instead

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	Partially addresses 'what' at a high level but completely lacks any 'when' guidance. No 'Use when...' clause or explicit trigger conditions are provided.	1 / 3
Trigger Term Quality	Contains some relevant keywords users might say ('Bash', 'CI/CD', 'shell scripts', 'automation') but missing common variations like 'bash script', '.sh files', 'cron jobs', 'deploy scripts', or specific commands.	2 / 3
Distinctiveness Conflict Risk	Bash/shell scripting is somewhat specific, but 'automation' and 'CI/CD' are broad terms that could overlap with many other skills (Python automation, deployment tools, etc.).	2 / 3
	Total	6 / 12 Passed

Implementation

14%

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

This skill reads like a comprehensive Bash reference manual rather than a focused skill document. It contains valuable information but violates token efficiency by explaining concepts Claude already knows, lacks a clear actionable workflow, and dumps all content inline rather than using progressive disclosure. The core guidance is buried under extensive reference material.

Suggestions

Reduce content by 70-80% by removing explanations of standard Bash concepts (strict mode, arrays, parameter expansion) and keeping only project-specific patterns or non-obvious guidance

Create a clear 5-7 step workflow in Instructions with explicit validation checkpoints (e.g., 'Run ShellCheck before proceeding')

Extract reference sections (Tools, Modern Features, Advanced Techniques, References) into separate linked files like BASH_REFERENCE.md

Add a concrete example showing a complete mini-script being written following the workflow, demonstrating the patterns in context

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose at ~400+ lines, containing extensive explanations of concepts Claude already knows (what strict mode does, how arrays work, basic Bash syntax). Lists like 'Modern Bash Features' and 'Common Pitfalls' explain standard Bash knowledge rather than project-specific guidance.	1 / 3
Actionability	Contains many concrete code snippets and commands that are executable, but they're scattered throughout as isolated examples rather than integrated workflows. The 'Instructions' section is vague (4 abstract steps), while actionable content is buried in lengthy reference sections.	2 / 3
Workflow Clarity	The 4-step 'Instructions' section is too abstract ('Apply strict mode and safe argument parsing'). No clear sequenced workflow with validation checkpoints for writing a script. The 'Quality Checklist' at the end is useful but disconnected from any process flow.	1 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files. All content is inline including extensive tool documentation, reference material, and external links that should be in separate reference files. The skill tries to be a complete Bash manual rather than an overview with pointers.	1 / 3
	Total	5 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	10 / 11 Passed

Repository: duclm1x1/Dive-Ai
Commit: 20ba150

Reviewed: 27 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.