bash-script-generator

Creates bash scripts with argument parsing, error handling, logging, and input validation following current standards. Use when creating new bash or shell scripts, .sh files, CLI tools, scripting automation, text processing workflows (grep/awk/sed pipelines), or building production-ready command-line utilities. Trigger phrases include 'write a bash script', 'create a shell script', 'generate a .sh file', 'bash command', 'scripting', or 'automate with bash'.

Quality

86%

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

Quality

Content

81%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 a well-sequenced, validated generation workflow and mostly well-signaled bundle references. It loses points for re-explaining shell fundamentals Claude already knows, duplicating the getopts example, and one broken reference path.

Suggestions

Trim the Anti-Patterns 'WHY' explanations of what set -euo pipefail flags and unquoted-variable word splitting do — state the rule and keep only non-obvious rationale.

Remove the duplicated getopts demonstration in Pattern 1 (and the inlined Stage 4 template code) in favor of pointing to assets/templates/standard-template.sh, which already contains the full implementations.

Fix the broken reference 'examples/log-analyzer.sh' to the actual bundle path 'assets/log-analyzer.sh'.

Dimension	Reasoning	Score
Conciseness	Mostly efficient executable guidance, but the Anti-Patterns 'WHY' lines explain basics Claude already knows (what set -e/-u/pipefail each do, why unquoted $VAR word-splits), the Mindset section is long prose, and Pattern 1 re-demonstrates the getopts parsing already shown in Stage 4 — fitting 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than anchor 2, since padding is limited and not pervasive.	3 / 5
Actionability	Copy-paste-ready implementations throughout: full logging functions, die/check_command/validate_file, a complete getopts parser, a runnable main() with validation calls, the template-generator command, and an external validator step — covering the common cases as anchor 5 requires.	5 / 5
Workflow Clarity	An explicit 8-stage sequence with a required pre-generation checklist and a validate-fix-revalidate feedback loop in Stage 8 ('Fix issues and re-validate until all checks pass'), plus cleanup-trap guidance — matching the clear-sequence-with-explicit-validation anchor.	5 / 5
Progressive Disclosure	References are one level deep, clearly segregated into 'Internal references (offline, load as context)' with per-file descriptions, and nearly all paths resolve in the bundle; however 'examples/log-analyzer.sh' is a broken path (the file lives at assets/log-analyzer.sh) and Stage 4/Pattern 1 inline substantial template code already held in assets/templates/standard-template.sh, fitting 'good structure; minor organization gaps' rather than anchor 5.	4 / 5
	Total	17 / 20 Passed

Description

91%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.

A strong description that clearly states capabilities in third person and gives both an explicit 'Use when' clause and a list of natural trigger phrases including file extensions. Its only weaknesses are the vague 'following current standards' filler and slight over-broad triggers around text-processing pipelines and 'bash command'.

Dimension	Reasoning	Score
Specificity	Lists four concrete actions ('argument parsing, error handling, logging, and input validation') in third person, matching the 'several specific actions; minor gaps' anchor; 'following current standards' is filler and coverage omits traps/cleanup/portability, keeping it below the comprehensive anchor 5.	4 / 5
Completeness	Explicitly answers both what ('Creates bash scripts with argument parsing, error handling, logging, and input validation') and when ('Use when creating new bash or shell scripts... Trigger phrases include...') with concrete trigger phrases, matching anchor 5; not a 4 because the 'when' clause is fully explicit rather than improvable.	5 / 5
Trigger Term Quality	Covers natural synonyms and file extensions ('bash or shell scripts, .sh files, CLI tools') plus explicit trigger phrases users would actually say ('write a bash script', 'create a shell script', 'generate a .sh file', 'automate with bash'), matching the comprehensive anchor.	5 / 5
Distinctiveness Conflict Risk	Clear bash/shell scripting niche with distinct triggers, but 'text processing workflows (grep/awk/sed pipelines)' and 'bash command' create minor overlap risk with a text-processing skill or one-off shell commands, fitting 'mostly distinct; minor overlap risk' rather than the minimal-conflict anchor 5.	4 / 5
	Total	18 / 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
referenced_paths_exist	Referenced path issues: 2 deeper-than-1-level	Warning

	Total	15 / 16 Passed

Repository: pantheon-org/tekhne
Path: skills/development/scripting/bash-script/generator/SKILL.md
Commit: a1083f4

Reviewed: 1 hour 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.