CtrlK
BlogDocsLog inGet started
Tessl Logo

bash-pro

Master of defensive Bash scripting for production automation, CI/CD pipelines, and system utilities. Expert in safe, portable, and testable shell scripts.

67

1.45x
Quality

55%

Does it follow best practices?

Impact

87%

1.45x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/bash-pro/SKILL.md

The canonical home for this skill is bash-pro in rmyndharis/antigravity-skills

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 but is severely over-long, padding much generic knowledge Claude already has, and it inlines reference material that should be split into bundled files rather than kept in SKILL.md.

Suggestions

Trim generic best-practice bullets that restate known Bash knowledge (quoting, printf vs echo, [[ ]]) and keep only non-obvious or skill-specific guidance to improve conciseness.

Move the Essential Tools catalog, Modern Bash 5.x feature lists, and References links into a references/ file (e.g., TOOLS.md) and link to it from SKILL.md to apply progressive disclosure.

Add explicit validation checkpoints to the Instructions workflow (e.g., 'Run shellcheck and bats; only proceed when both pass') so destructive/batch operations get a feedback loop.

DimensionReasoningScore

Conciseness

The ~300-line body is a wall of bulleted best practices, much of which restates knowledge Claude already has (quote variable expansions, prefer printf over echo, use [[ ]]), making it noticeably verbose with several padded sections.

2 / 5

Actionability

It provides many concrete, executable snippets (set -Eeuo pipefail, SCRIPT_DIR detection, readarray -d '' with find -print0, trap examples), but they are scattered fragments rather than complete end-to-end examples covering common cases.

4 / 5

Workflow Clarity

The Instructions section lists a 4-step sequence (define inputs -> strict mode -> core logic -> tests/linting), but it lacks explicit validation checkpoints, and because the skill covers destructive operations the rubric caps workflow clarity at 3.

3 / 5

Progressive Disclosure

There are no bundle files and the entire 300-line reference (Essential Tools catalog, Advanced Techniques, Modern Bash features, link lists) is inlined in SKILL.md; section headers provide structure, but content that belongs in separate reference files is not offloaded.

3 / 5

Total

12

/

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 scripting niche with good trigger keywords, but it relies on persona/credential framing ('Master', 'Expert') instead of concrete action verbs and entirely lacks a 'Use when' trigger clause.

Suggestions

Rewrite using third-person action verbs (e.g., 'Writes, reviews, and hardens Bash scripts...') instead of credential claims like 'Master of'/'Expert in'.

Add an explicit 'Use when...' clause naming concrete triggers, e.g., 'Use when writing or reviewing Bash scripts for automation, CI/CD pipelines, or system utilities.'

Include common synonyms/file extensions such as '.sh files' to round out trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain and several areas ('defensive Bash scripting for production automation, CI/CD pipelines, and system utilities'), but leads with credential claims ('Master of', 'Expert in') rather than concrete action verbs, so actions remain minimal rather than comprehensive.

3 / 5

Completeness

It gives a clear 'what' (defensive Bash scripting for automation/CI/CD/utilities) but contains no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

It includes natural terms users would say ('Bash scripting', 'CI/CD pipelines', 'production automation', 'system utilities', 'shell scripts'), but misses common synonyms like '.sh files', so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

'Bash scripting' is a clear niche with minimal conflict risk, with only minor overlap against a generic shell-scripting skill.

4 / 5

Total

14

/

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.

Validation15 / 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
administrakt0r/AI-Agents-Safe-Coding-Skills
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.