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

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/bash-pro/SKILL.md

Quality

Content

50%

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

The content is highly actionable with many executable snippets, but it is far too verbose — restating standard Bash knowledge Claude already has — and presents everything inline as a monolithic document with abstract workflow steps and no validation checkpoints.

Suggestions

Trim restatements of well-known Bash basics (quoting, strict mode, printf-vs-echo) and keep only non-obvious, expert-level guidance to improve conciseness.

Make the Instructions workflow concrete with explicit validation steps (e.g. run ShellCheck, run Bats tests, only proceed on green).

Move large reference blocks (Essential Tools, Advanced Techniques, References) into separate bundle files referenced one level deep from SKILL.md.

Dimension	Reasoning	Score
Conciseness	The body is a ~290-line kitchen-sink reference that restates Bash knowledge Claude already has (quoting expansions, set -Eeuo pipefail, printf over echo), violating the guideline to penalize explanations of concepts Claude already knows.	1 / 3
Actionability	It provides many concrete, copy-paste-ready snippets such as `SCRIPT_DIR="$(cd -- "$(dirname -- "${BASH_SOURCE[0]}")" && pwd -P)"`, `readarray -d '' files < <(find . -print0)`, and a full `log_info()` function, matching the executable-guidance anchor.	3 / 3
Workflow Clarity	The Instructions section lists four sequenced steps but they are abstract ("Define script inputs, outputs, and failure modes") with no explicit validation checkpoint or feedback loop, so it sits at the score-2 anchor.	2 / 3
Progressive Disclosure	No bundle files exist and the body is a monolithic wall of sectioned bullets that could be split into reference files (Essential Tools, Advanced Techniques, Modern Bash Features), matching the score-2 example of inline content that belongs in separate files.	2 / 3
	Total	8 / 12 Passed

Description

72%

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 is distinctive and uses natural trigger terms, but it relies on persona framing ("Master of", "Expert in") instead of concrete actions and lacks an explicit "Use when" trigger clause, capping completeness at 2.

Suggestions

Rewrite as concrete third-person actions: e.g. "Write, review, and harden Bash shell scripts for automation, CI/CD, and system utilities."

Add an explicit trigger clause: "Use when writing or reviewing Bash/shell scripts, CI/CD pipelines, or production automation tasks."

Dimension	Reasoning	Score
Specificity	The description names a clear domain ("defensive Bash scripting for production automation, CI/CD pipelines, and system utilities") but frames it as expertise ("Master of", "Expert in") rather than enumerating concrete actions, so it is not comprehensive like the score-3 anchor.	2 / 3
Completeness	It states what the skill covers but contains no "Use when..." clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	Natural user-facing terms are well covered: "Bash scripting", "CI/CD pipelines", "system utilities", and "shell scripts" are exactly what a user would say when needing this skill.	3 / 3
Distinctiveness Conflict Risk	Defensive Bash/shell scripting for production automation is a distinct niche unlikely to trigger for unrelated skills; it is clearly distinguishable.	3 / 3
	Total	10 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Path: skills/bash-pro/SKILL.md
Commit: a3068b7

Reviewed: about 6 hours 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.