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

59%

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

57%Weight 40%Scale 1-5

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

The body is highly actionable with extensive executable Bash patterns, but it is over-long and redundant across safety/security sections, and its core workflow lacks explicit validation checkpoints. With no bundle files, progressive disclosure rests on section headers alone rather than offloading detail to referenced files.

Suggestions

Consolidate the four overlapping safety/security sections into one to remove redundancy and trim token cost.

Add an explicit validate→fix→retry loop to the 'Instructions' workflow (e.g. run ShellCheck, fix findings, re-run, then bats tests) so destructive/batch work has checkpoints.

Move the 'Essential Tools', 'Modern Bash Features (5.x)', and 'References' material into separate reference files linked from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	At ~300 lines the body is noticeably verbose with heavy redundancy — safety material recurs across 'Safety', 'Safety & Security Patterns', 'Security Scanning & Hardening', and 'Common Pitfalls', and 'Focus Areas' overlaps 'Approach' — so much of the listing could be consolidated.	2 / 5
Actionability	It is packed with copy-paste-ready, executable snippets (e.g. `set -Eeuo pipefail`, `trap 'rm -rf "$tmpdir"' EXIT`, `readarray -d '' files < <(find . -print0)`) covering the common defensive-scripting cases.	5 / 5
Workflow Clarity	The 'Instructions' section lists a 4-step sequence but lacks validation checkpoints/feedback loops, and because the skill covers destructive/batch operations (rm -rf, file ops) the missing validate→fix→retry loop caps workflow clarity at 3.	3 / 5
Progressive Disclosure	There is clear section structure and an external 'References & Further Reading' block, but for a file this size much that could live in separate files ('Essential Tools', 'Modern Bash Features (5.x)', 'Dependency Management') is inlined with no bundle files provided.	3 / 5
	Total	13 / 20 Passed

Description

61%Weight 40%Scale 1-5

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 clearly identifies the Bash defensive-scripting niche with good natural trigger terms, but it lacks an explicit 'Use when...' trigger clause and leans on quality adjectives rather than concrete actions. Completeness is capped at 3 because the when-to-use guidance lives in the body, not the description.

Suggestions

Add an explicit trigger clause to the description, e.g. 'Use when writing or reviewing Bash/shell scripts for automation, CI/CD, or ops tasks.'

Replace quality adjectives ('safe, portable, and testable') with concrete verbs the skill performs (write, review, harden, lint, test).

Include common file-extension triggers such as '.sh' to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('defensive Bash scripting') and several application contexts ('production automation, CI/CD pipelines, and system utilities') but the only 'actions' are generic 'scripting' plus quality adjectives ('safe, portable, and testable'), not concrete verbs like write/review/harden.	3 / 5
Completeness	The 'what' is clear (defensive Bash scripting for automation/CI/CD/utilities), but there is no 'Use when...' clause or equivalent explicit trigger guidance in the description itself, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	It includes natural terms a user would say — 'Bash scripting', 'CI/CD pipelines', 'production automation', 'shell scripts' — giving good coverage, though a few common variants like '.sh' or the bare phrase 'bash script' are absent.	4 / 5
Distinctiveness Conflict Risk	The Bash/shell-scripting niche is clearly demarcated and unlikely to trigger for unrelated skills, with only minor overlap risk against general CI/CD or automation skills.	4 / 5
	Total	14 / 20 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: 1f67c44

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