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 description is essentially a placeholder with no substantive content. It fails on every dimension: it describes no concrete actions, includes no natural trigger terms, lacks both 'what' and 'when' information, and is too generic to be distinguishable from other skills. The repeated trigger term 'bash script helper' suggests auto-generated boilerplate rather than a thoughtfully crafted description.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Writes, debugs, and optimizes bash/shell scripts, creates cron jobs, builds CI/CD pipeline scripts, and handles file automation tasks.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to write a bash script, shell script, .sh file, automate a task with bash, or needs help with shell commands, piping, or scripting syntax.'
Remove the redundant duplicate trigger term and replace with varied natural language terms users would actually use, such as 'shell script', 'sh', 'bash automation', 'command line script', 'cron job'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It says 'Bash Script Helper' but never describes what it actually does—no mention of writing, debugging, optimizing, or any specific bash-related capabilities. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no 'Use when...' clause, and the description provides no information about the skill's actual functionality. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'bash script helper' repeated twice. These are not natural phrases users would say; users would more likely say 'write a bash script', 'shell script', 'sh file', 'automate with bash', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic—'Bash Script Helper' could overlap with any shell scripting, DevOps, automation, or general coding skill. There are no distinct triggers or scope boundaries to differentiate it. | 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/placeholder with no actual instructional content. It repeatedly references 'bash script helper' without ever defining what that means, providing any bash scripting guidance, or offering any actionable information. The entire content could be replaced by a single sentence and would convey the same (zero) information.
Suggestions
Add concrete, executable bash script examples covering common patterns (e.g., argument parsing with getopts, error handling with set -euo pipefail, trap for cleanup, logging functions).
Include a clear workflow for writing robust bash scripts: e.g., 1. Add shebang and strict mode, 2. Define functions, 3. Validate inputs, 4. Run shellcheck to validate.
Replace all generic placeholder text with specific bash scripting best practices, common pitfalls, and copy-paste-ready code snippets.
Add references to related detailed guides (e.g., SHELLCHECK.md, COMMON_PATTERNS.md) if the skill is meant to be an overview, or inline the essential content if it's meant to be self-contained.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know and provides zero domain-specific information. Every section restates the same vague concept ('bash script helper') without adding substance. | 1 / 3 |
Actionability | There are no concrete commands, code examples, scripts, or specific instructions. The content describes capabilities abstractly ('provides step-by-step guidance') without actually providing any guidance whatsoever. | 1 / 3 |
Workflow Clarity | No workflow, steps, or processes are defined. The skill claims to provide 'step-by-step guidance' but contains zero steps. There are no validation checkpoints or sequences of any kind. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic placeholder text with no references to external files, no structured navigation, and no meaningful content organization. Section headers exist but contain no useful 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
c8a915c
- 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.