bash-pro
Master of defensive Bash scripting for production automation, CI/CD pipelines, and system utilities. Expert in safe, portable, and testable shell scripts.
44
Quality
18%
Does it follow best practices?
Impact
87%
1.45xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/bash-pro/SKILL.mdQuality
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 concrete capabilities. It fails to specify what actions the skill performs and completely lacks trigger guidance for when Claude should select it. The description would benefit from listing specific operations and adding explicit 'Use when...' clauses.
Suggestions
Replace vague expertise claims with specific actions (e.g., 'Writes error-handling shell scripts, creates portable bash functions, builds CI/CD pipeline scripts')
Add an explicit 'Use when...' clause with trigger terms like 'bash script', 'shell script', '.sh file', 'automate with bash', 'CI pipeline script'
Remove first-person-adjacent language ('Master of', 'Expert in') and use third person action verbs describing what the skill does
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Uses vague descriptors like 'Master of' and 'Expert in' without listing concrete actions. No specific operations are mentioned - only abstract domains like 'production automation' and 'system utilities'. | 1 / 3 |
Completeness | Describes a vague 'what' (Bash scripting expertise) but completely lacks any 'when' clause or explicit trigger guidance. No 'Use when...' or equivalent instruction for Claude to know when to select this skill. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords users might say ('Bash scripting', 'CI/CD pipelines', 'shell scripts') but uses technical jargon and misses common variations like 'bash script', '.sh files', 'shell commands', or 'automation scripts'. | 2 / 3 |
Distinctiveness Conflict Risk | Mentions Bash/shell specifically which provides some distinction, but 'CI/CD pipelines' and 'system utilities' are broad enough to overlap with DevOps, infrastructure, or general scripting skills. | 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 as an exhaustive Bash reference manual rather than a focused skill document. It violates token efficiency by explaining concepts Claude already knows (parameter expansion, arrays, conditionals) and lacks clear workflows with validation steps. The content would benefit from aggressive trimming to focus on truly novel patterns and restructuring into a brief overview with links to detailed reference files.
Suggestions
Reduce content by 80%+ by removing explanations of basic Bash concepts Claude already knows (arrays, parameter expansion, conditionals, etc.) and focus only on project-specific patterns or truly advanced techniques
Restructure the 4-step Instructions into a concrete workflow with explicit validation checkpoints (e.g., 'Run ShellCheck before proceeding', 'Verify with Bats tests')
Split reference material into separate files (TESTING.md, SECURITY.md, CI-CD.md) and keep SKILL.md as a concise overview with clear navigation links
Add a concrete end-to-end example showing how to apply the skill to create a production script from scratch, demonstrating the workflow in action
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~400+ lines, covering extensive topics Claude already knows (basic Bash syntax, what arrays are, how parameter expansion works). It reads like a comprehensive Bash reference manual rather than a focused skill teaching specific techniques Claude doesn't know. | 1 / 3 |
Actionability | Contains many concrete code snippets and patterns 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 bulk of content is reference material. | 2 / 3 |
Workflow Clarity | The 4-step 'Instructions' section is too abstract to be actionable ('Apply strict mode and safe argument parsing'). No clear validation checkpoints or feedback loops for the multi-step processes involved in writing production scripts. The 'Quality Checklist' at the end is disconnected from any workflow. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content is inline despite being far too long for a SKILL.md overview. Topics like CI/CD integration, security scanning, and testing frameworks could each be separate reference documents. | 1 / 3 |
Total | 5 / 12 Passed |
Validation
90%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
- sickn33/antigravity-awesome-skills
- Commit
9c177eb
- Reviewed
Table of Contents
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.