CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/bash-pro/SKILL.md
SKILL.md
Quality
Evals
Security

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 body is rich with concrete, executable Bash patterns and is well-organized by section headers, but it functions as a monolithic reference dump: much of it restates knowledge Claude already has, repeats itself across sections, and keeps everything inline instead of splitting into bundled reference files. The core workflow lacks explicit validation and feedback loops despite covering destructive operations.

Suggestions

Split reference material (Essential Tools, CI/CD Integration, Dependency Management, Advanced Techniques) into separate bundle files under references/ and keep SKILL.md as a lean overview — this would also cut the token cost of the many bullets that restate Bash fundamentals Claude already knows.

Add explicit validation checkpoints and fix-retry loops to the Instructions workflow (e.g., "run shellcheck, fix findings, re-run until clean") since the skill covers destructive operations like rm -rf.

De-duplicate repeated guidance (mapfile/readarray, Bash version checks, and "--" option-separator usage each appear in multiple sections) into a single authoritative section.

DimensionReasoningScore

Conciseness

Many bullets restate Bash knowledge Claude already has ("cmd1 && cmd2 run cmd2 only if cmd1 succeeds", "${filename%.sh} remove extension", "Quote all variable expansions", "$() instead of backticks"), and content is duplicated across sections (mapfile, version checks, and "--" usage each appear 2-3 times), making the 330-line body noticeably verbose despite its terse bullet format.

2 / 5

Actionability

Abundant concrete, copy-pasteable patterns ("set -Eeuo pipefail; shopt -s inherit_errexit", "tmpdir=$(mktemp -d) || exit 1; trap 'rm -rf -- \"$tmpdir\"' EXIT", "readarray -d '' files < <(find . -print0)", plus a complete runnable example script), though a sizeable fraction of bullets remain abstract directives like "Configure log file rotation" and "Track execution time".

4 / 5

Workflow Clarity

The Instructions section provides a rough 4-step sequence (define inputs → strict mode → core logic → tests/lint) but includes no validation checkpoints or fix-retry feedback loops; since the skill governs destructive operations (rm -rf, cleanup traps), the missing validation loop caps workflow clarity at 3.

3 / 5

Progressive Disclosure

No bundle files exist, and ~330 lines of tool catalogs, CI/CD integration details, dependency management, and advanced techniques are all inlined in one monolithic SKILL.md; the numerous clear section headers and well-labeled external reference links provide some structure, but content that clearly belongs in separate reference files is inline.

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 identifies its Bash scripting niche with good natural trigger keywords, but it reads as a persona statement ("Master of", "Expert in") rather than a list of concrete capabilities, and it completely lacks any "Use when..." trigger guidance. Adding explicit actions and a trigger clause would move it into the top tier.

Suggestions

Add an explicit trigger clause such as "Use when writing, reviewing, or hardening Bash scripts for automation, CI/CD, or ops tasks" — its absence currently caps completeness at 3.

Replace persona claims ("Master of", "Expert in") with concrete third-person actions, e.g., "Writes, reviews, and hardens Bash scripts..." to lift specificity.

Include common user phrasings like ".sh files" or "shell script" as trigger synonyms to round out keyword coverage.

DimensionReasoningScore

Specificity

The description names its domains ("defensive Bash scripting", "production automation, CI/CD pipelines, and system utilities") but contains no concrete action verbs — "Master of" and "Expert in" are persona/buzzword claims rather than capabilities, matching the anchor for domain-named but generic actions.

2 / 5

Completeness

The 'what' is reasonably clear (defensive, safe, portable, testable Bash scripting) but the 'when' is entirely absent — there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Good natural keyword coverage: "Bash scripting", "CI/CD pipelines", "automation", "system utilities", "shell scripts" are phrases users would actually say, though common variants like ".sh" or plain "shell" are missing, keeping it below the comprehensive-synonym anchor.

4 / 5

Distinctiveness Conflict Risk

"defensive Bash scripting" and "shell scripts" form a clear, distinct niche, but the broad "production automation" and "CI/CD pipelines" scope creates minor overlap risk with generic CI/CD or automation skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

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.