bash-script-validator

Comprehensive toolkit for validating, linting, and optimizing bash and shell scripts. Use this skill when working with shell scripts (.sh, .bash), validating script syntax, detecting unquoted variables, checking POSIX compliance, identifying unsafe command substitutions, validating shebang lines, finding security vulnerabilities, or debugging shell script problems.

Quality

83%

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

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

A highly actionable, well-structured skill with an exemplary bundle layout — every referenced file exists, references are one level deep, and commands are copy-paste ready. The main weakness is redundancy: the Mindset paragraph and the Anti-Patterns section state the same four points twice, and the workflow lacks an explicit re-validation loop after fixes.

Suggestions

Merge the Mindset paragraph with the Anti-Patterns section — they cover the same four points (static-analysis limits, global disables, POSIX vs bash, exit-code suppression) in nearly identical wording, roughly halving that content.

Add a final workflow step such as '6. Re-run bash scripts/validate.sh to confirm all issues are resolved' to close the fix-verify feedback loop.

Drop the Layout tree (or the References section) — they enumerate the same files twice; the workflow's inline references plus one listing suffice.

Dimension	Reasoning	Score
Conciseness	The four Mindset points (ShellCheck is static-only, no global disables, POSIX vs bash, exit-code propagation) are restated nearly verbatim as the four Anti-Patterns sections, and the Layout tree duplicates the References section — the content is accurate but noticeably duplicated and could be tightened.	3 / 5
Actionability	Everything is executable: 'bash scripts/validate.sh <script-path>', concrete install commands for three platforms, wrapper invocations with flags, documented exit codes, a numbered response-format template, and a full sample output covering the common case.	5 / 5
Workflow Clarity	The Required Workflow is a clear numbered sequence with per-issue sub-steps (show, explain, fix, justify) and running the validator acts as an upfront checkpoint, but it ends at 'provide the corrected code' with no re-run/re-validate step to confirm fixes.	4 / 5
Progressive Disclosure	All referenced bundle files exist (8 references, 2 scripts, 4 assets) and match the body's References and Layout listings; references are one level deep, clearly signaled with per-file descriptions, and the body stays an overview while details live in the bundle.	5 / 5
	Total	17 / 20 Passed

Description

88%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 explicitly covers both what the skill does and when to use it, with concrete capability enumeration and file-extension triggers. Its main gaps are the missing 'ShellCheck' keyword — the single most natural term a user would say for this task — and slight overlap risk from 'optimizing' and 'debugging'.

Suggestions

Add 'running ShellCheck' or 'linting with ShellCheck' to the trigger terms, since users asking for this skill will most often say 'shellcheck' or 'lint my script'.

Consider trimming 'optimizing' or scoping it (e.g., 'suggesting performance and safety fixes') to reduce overlap with a bash-script-generation/editing skill.

Drop the 'Comprehensive toolkit for' opener — it is generic padding before the real capability list.

Dimension	Reasoning	Score
Specificity	Beyond the generic opener ('Comprehensive toolkit for validating, linting, and optimizing'), the trigger clause enumerates multiple concrete actions — 'detecting unquoted variables, checking POSIX compliance, identifying unsafe command substitutions, validating shebang lines, finding security vulnerabilities' — giving comprehensive, specific coverage of the skill's capabilities.	5 / 5
Completeness	It clearly answers 'what' ('validating, linting, and optimizing bash and shell scripts' plus the enumerated checks) and 'when' via the explicit 'Use this skill when working with shell scripts (.sh, .bash), validating script syntax...' trigger clause with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural terms include 'shell scripts', '.sh', '.bash', 'shebang', 'POSIX compliance', and 'debugging shell script problems', covering synonyms and file extensions, but the most natural user phrasings for this task — 'ShellCheck' and 'lint my script' — are absent (only 'linting' appears indirectly).	4 / 5
Distinctiveness Conflict Risk	The validation/linting niche is distinct with clear triggers, but 'optimizing' and 'debugging shell script problems' create minor overlap with a script-generation or general-debugging skill, so it is not a pure anchor-5 niche.	4 / 5
	Total	18 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: pantheon-org/tekhne
Path: skills/development/scripting/bash-script/validator/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.