bash-script-helper
Bash Script Helper - Auto-activating skill for DevOps Basics. Triggers on: bash script helper, bash script helper Part of the DevOps Basics skill category.
34
0%
Does it follow best practices?
Impact
98%
1.03xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/01-devops-basics/bash-script-helper/SKILL.mdQuality
Discovery
0%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an extremely weak description that functions more as a label than a useful skill description. It provides no concrete actions, no natural trigger terms, and no guidance on when Claude should select this skill. It would be nearly impossible for Claude to correctly choose this skill from a pool of available skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Writes, debugs, and optimizes bash shell scripts, creates cron jobs, and builds automation pipelines.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about bash scripts, shell scripting, .sh files, cron jobs, or command-line automation.'
Remove the duplicate trigger term 'bash script helper' and replace with varied natural language terms users would actually say, such as 'bash', 'shell script', 'scripting', 'command line', '.sh'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Bash Script Helper' is a name, not a description of capabilities. There is no mention of what the skill actually does (e.g., write scripts, debug scripts, optimize scripts). | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. The description only states it's an 'auto-activating skill' in a category, with no explanation of functionality or explicit usage triggers. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'bash script helper' repeated twice, which is not a natural phrase users would say. Missing natural terms like 'bash', 'shell script', '.sh', 'scripting', 'automation', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it could overlap with any shell scripting, DevOps, or automation skill. 'Bash Script Helper' provides no clear niche or distinguishing characteristics. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template with no actual content. It contains only generic boilerplate text that repeats the phrase 'bash script helper' without providing any actionable bash scripting guidance, code examples, best practices, or workflows. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable bash script examples (e.g., a template script with proper error handling using `set -euo pipefail`, argument parsing with `getopts`, and logging patterns).
Define a clear workflow for writing bash scripts: e.g., 1) Start with shebang and safety flags, 2) Define variables and validate inputs, 3) Implement logic, 4) Test with `shellcheck` and `bash -n` for validation.
Remove all generic boilerplate ('This skill provides automated assistance...') and replace with specific, actionable content about bash scripting patterns, common pitfalls, and DevOps-relevant examples (e.g., deployment scripts, health checks).
Add a quick-reference section with common bash idioms and anti-patterns that are specific to DevOps contexts (e.g., safe file operations, proper signal handling, idempotent scripts).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'bash script helper' excessively, and contains zero substantive information about bash scripting. | 1 / 3 |
Actionability | There are no concrete commands, code examples, scripts, or executable guidance whatsoever. Every section is vague and abstract — 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow, steps, or processes are defined. The skill claims to provide 'step-by-step guidance' but contains no steps at all. | 1 / 3 |
Progressive Disclosure | No bundle files exist, no references to external resources, and the content itself is a flat, uninformative page with no meaningful structure or navigation to deeper content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
13d35b8
- 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.