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

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./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 reads more like a resume headline than a functional skill description. It relies on self-aggrandizing language ('Master of', 'Expert in') rather than concrete actions, lacks any explicit trigger guidance for when Claude should select this skill, and fails to enumerate specific capabilities that would differentiate it from other coding or DevOps skills.

Suggestions

Replace vague claims like 'Master of' and 'Expert in' with specific actions: e.g., 'Writes defensive Bash scripts with error handling, generates CI/CD pipeline configurations, creates portable shell utilities with proper quoting and exit code management.'

Add an explicit 'Use when...' clause with natural trigger terms: e.g., 'Use when the user asks for Bash scripts, shell scripting, .sh files, CI/CD pipeline automation, cron jobs, or system utility scripts.'

Use third-person active voice describing what the skill does rather than what it claims to be (e.g., 'Generates safe, portable Bash scripts...' instead of 'Master of defensive Bash scripting...').

Dimension	Reasoning	Score
Specificity	The description uses vague, self-congratulatory language like 'Master of' and 'Expert in' without listing any concrete actions. Terms like 'defensive Bash scripting', 'production automation', and 'system utilities' are abstract domains, not specific capabilities like 'write error-handling wrappers' or 'generate CI/CD pipeline scripts'.	1 / 3
Completeness	The description vaguely addresses 'what' (Bash scripting for automation/CI/CD) but never answers 'when' Claude should use this skill. There is no 'Use when...' clause or equivalent explicit trigger guidance, and the 'what' itself is too abstract to be useful.	1 / 3
Trigger Term Quality	Contains some relevant keywords users might say such as 'Bash', 'CI/CD pipelines', 'shell scripts', and 'automation'. However, it misses common variations like 'sh', '.sh files', 'cron jobs', 'deploy scripts', 'makefile', or specific actions users would request.	2 / 3
Distinctiveness Conflict Risk	The mention of 'Bash scripting' and 'CI/CD pipelines' provides some specificity, but 'production automation' and 'system utilities' are broad enough to overlap with general coding skills, DevOps skills, or infrastructure-related 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, actionable skill document. It covers an enormous breadth of topics—from basic parameter expansion to CI/CD integration to security scanning—but lacks depth in any single area, with no complete executable examples or clear multi-step workflows. The extreme verbosity (300+ lines of bullet points) wastes token budget on knowledge Claude already possesses, while the flat structure makes it difficult to navigate.

Suggestions

Reduce content by 60-70% by removing topics Claude already knows (basic Bash syntax, parameter expansion, brace expansion, conditional execution) and focusing only on non-obvious defensive patterns and project-specific conventions.

Add 2-3 complete, executable script templates (e.g., a production-ready CLI script skeleton with strict mode, argument parsing, logging, and cleanup) instead of scattered one-liner snippets.

Create a clear multi-step workflow with validation checkpoints for the script development process, e.g.: write → shellcheck → test with bats → validate on target platforms → deploy, with explicit feedback loops on failure.

Split the monolithic content into bundle files (e.g., TOOLS.md, ADVANCED_TECHNIQUES.md, SECURITY.md, CI_CD.md) and keep SKILL.md as a concise overview with signposted references to each.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at 300+ lines with extensive lists of bullet points covering topics Claude already knows well (basic Bash syntax, parameter expansion, brace expansion, conditional execution). Many sections read like a Bash textbook rather than adding novel, non-obvious guidance. The references, tool lists, and feature catalogs massively inflate token usage without proportional value.	1 / 3
Actionability	Contains many concrete code snippets and specific commands (e.g., strict mode settings, find patterns, mktemp usage), but most are isolated one-liners rather than complete executable examples. There are no full script templates or copy-paste-ready workflows showing how the pieces fit together. The guidance is more of a reference catalog than step-by-step executable instructions.	2 / 3
Workflow Clarity	The 'Instructions' section lists only 4 vague steps ('Define script inputs', 'Apply strict mode', 'Implement core logic', 'Add tests') without any concrete sequencing, validation checkpoints, or feedback loops. For a skill involving destructive operations (file manipulation, system automation), there are no explicit validate-then-proceed workflows. The quality checklist at the end is a post-hoc list, not an integrated workflow.	1 / 3
Progressive Disclosure	All content is crammed into a single monolithic file with no bundle files or references to supporting documents. Sections like 'Essential Tools', 'Advanced Techniques', 'Modern Bash Features', 'References & Further Reading' could easily be split into separate files. The result is an overwhelming wall of bullet points with no layered navigation structure.	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
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: 8854d4e

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