shell-script-development

This skill should be used when the user asks to "create a bash script", "write a shell script", or mentions shell scripting conventions.

Quality

77%

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 ./plugins/toolkit/skills/shell-script-development/SKILL.md

Quality

Content

93%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 a tight, fully executable reference for a simple single-purpose skill, with a copy-paste template, concrete conventions, and a clear post-creation reminder. The only gap is the absence of a syntax-verification step for the generated script.

Dimension	Reasoning	Score
Conciseness	Lean and token-efficient: a template, a conventions table, status patterns, and one reminder, with no padding or explanation of concepts Claude already knows.	5 / 5
Actionability	Provides a fully executable, copy-paste-ready template, concrete status-output lines, explicit convention rules, and a specific post-creation command (`chmod +x script.sh`).	5 / 5
Workflow Clarity	The single action (apply the template and conventions) is unambiguous, but there is no verification checkpoint such as `bash -n` or shellcheck for the generated script, leaving a minor validation gap.	4 / 5
Progressive Disclosure	A simple under-50-line skill with no need for external references, organized into clear labeled sections (Template, Conventions, Status Output Patterns, Important).	5 / 5
	Total	19 / 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 provides strong, explicit trigger guidance for a well-defined niche, but it leads entirely with the "when" and never states what the skill does as a capability. Adding a concise capability clause and a few more synonyms/extensions would lift it from adequate to strong.

Suggestions

Lead with an explicit capability statement (e.g., "Creates shell scripts following consistent conventions.") before the trigger clause so the "what" is stated, not just implied.

Broaden trigger coverage with natural synonyms and extensions users actually say, such as ".sh files", "bash scripts", and "shell scripts".

Tighten the phrasing to third-person voice (e.g., "Creates shell scripts... Use when the user asks to...") to remove the slightly indirect "This skill should be used when" framing.

Dimension	Reasoning	Score
Specificity	Names the bash/shell-script domain and embeds two concrete actions ("create a bash script", "write a shell script") in its triggers, but lists no explicit capability statement and is not comprehensive.	3 / 5
Completeness	The "when" is explicit and concrete, but the "what" is only implied through the quoted trigger phrases rather than stated as a capability, so it does not clearly answer both what and when.	3 / 5
Trigger Term Quality	Includes natural phrases a user would say ("create a bash script", "write a shell script", "shell scripting conventions"), but misses common synonyms and extensions such as ".sh", "bash scripts", or "shell scripts" alone.	4 / 5
Distinctiveness Conflict Risk	Bash/shell scripting is a clear niche with distinct triggers and low conflict risk, though there is minor overlap with general scripting or coding skills.	4 / 5
	Total	14 / 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: dwmkerr/claude-toolkit
Path: plugins/toolkit/skills/shell-script-development/SKILL.md
Commit: 4316684

Reviewed: 8 days 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.