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

53%

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%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 content is rich with concrete, executable Bash fragments and well-organized sections, but it is heavily verbose with redundant enumeration of knowledge Claude already has, lacks a validation-checkpointed workflow (capped at 3 for destructive operations), and is monolithic with no progressive disclosure to bundle files.

Suggestions

Trim sections that restate well-known Bash knowledge (quoting, printf-vs-echo, [[ ]] vs [ ]) and de-duplicate patterns repeated across Approach, Performance, and Advanced Techniques.

Add explicit validation checkpoints to the Instructions workflow, e.g. 'Run shellcheck && bats test/; only proceed when green' between core logic and release.

Move the tool catalogs, Modern Bash 5.x version-feature tables, and References into separate bundle files (e.g. references/tools.md, references/modern-bash.md) and link to them from SKILL.md, and replace the empty Example section with a complete worked defensive script.

Dimension	Reasoning	Score
Conciseness	The ~314-line body extensively enumerates Bash best practices Claude already knows (quote expansions, prefer printf over echo, set -Eeuo pipefail, [[ ]] vs [ ]) across many padded sections, with redundant repetition (e.g. mapfile/readarray and version checks appear in multiple sections), placing it noticeably below the 'mostly efficient' anchor at 3.	2 / 5
Actionability	It provides many concrete, executable fragments ('set -Eeuo pipefail', SCRIPT_DIR detection, 'readarray -d "" files < <(find . -print0)', trap patterns), but the 'Example' section is just a quoted user request with no worked script, so it stops short of fully copy-paste-ready complete examples.	4 / 5
Workflow Clarity	The Instructions section lists a 4-step sequence (define -> strict mode -> core logic -> tests/lint) but has no explicit validation checkpoints or feedback loops, and because the skill covers destructive/batch operations (rm -rf, file ops) the rubric caps workflow clarity at 3.	3 / 5
Progressive Disclosure	The body is well-sectioned with clear headers and a clearly-labeled References section, but it is monolithic with no bundle files; substantial reference-style material (tool catalogs, per-version Bash 5.x feature lists) that could live in separate files is inlined into SKILL.md.	3 / 5
	Total	12 / 20 Passed

Description

56%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 scopes a Bash-defensive-scripting niche with natural trigger terms, but it relies on role language ('Master of', 'Expert in') rather than concrete actions and omits an explicit 'Use when' trigger clause, capping completeness at 3.

Suggestions

Replace role phrasing ('Master of', 'Expert in') with concrete verbs, e.g. 'Write, review, and harden defensive Bash scripts for production automation, CI/CD pipelines, and system utilities.'

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

Include common synonyms/extensions users say, such as 'bash scripts' and '.sh files', to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('defensive Bash scripting') and three application contexts ('production automation, CI/CD pipelines, and system utilities') but uses role phrasing ('Master of', 'Expert in') rather than discrete concrete actions (e.g. write, review, harden), so it sits below the '1-2 concrete actions' anchor at 3.	2 / 5
Completeness	It gives a clear 'what' (defensive Bash scripting for production/CI/CD/utilities, safe/portable/testable scripts) but no explicit 'when' / 'Use when...' trigger clause, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	It includes natural terms users say ('Bash scripting', 'shell scripts', 'CI/CD pipelines', 'production automation') with good coverage; only a few common variations like 'bash scripts' or '.sh files' are missing, fitting the 'good coverage, a few natural terms missing' anchor.	4 / 5
Distinctiveness Conflict Risk	The Bash-specific 'defensive' scripting niche framed around production automation and CI/CD is mostly distinct with only minor overlap risk against a general POSIX/shell scripting skill.	4 / 5
	Total	13 / 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/agentic-awesome-skills
Path: skills/bash-pro/SKILL.md
Commit: b1aebac

Reviewed: ~19 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.