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
Quality
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 placeholder text with no substantive content. It provides only a vague title and category metadata without explaining what the skill does, what actions it performs, or when it should be selected. It would be nearly impossible for Claude to correctly choose this skill from a pool of alternatives.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Writes, debugs, and optimizes bash shell scripts. Handles variable expansion, conditionals, loops, and error handling.'
Include a 'Use when...' clause with natural trigger terms like 'Use when the user asks about bash scripts, shell scripting, .sh files, or automating command-line tasks.'
Add common user phrases and file extensions as triggers: 'bash', 'shell script', '.sh', 'scripting', 'command line automation', 'cron jobs'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Bash Script Helper' is a vague label with no explanation of what it actually does - no verbs describing capabilities like 'writes', 'debugs', 'optimizes', or 'validates'. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no 'Use when...' clause and no explanation of capabilities - only category metadata. | 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 obvious terms like 'shell script', 'bash', '.sh files', 'scripting', 'automation', or specific bash operations. | 1 / 3 |
Distinctiveness Conflict Risk | Extremely generic - 'Helper' could apply to anything. Would conflict with any shell, scripting, DevOps, or automation-related skills. No distinct triggers or specific use cases 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 essentially an empty template with no actual content. It describes what a bash script helper skill would theoretically do but provides zero actionable guidance, no code examples, no commands, and no concrete information about bash scripting. The entire content could be replaced with actual bash scripting guidance in fewer tokens.
Suggestions
Replace the generic 'Capabilities' section with actual bash script patterns, e.g., shebang usage, error handling with 'set -euo pipefail', argument parsing examples
Add executable code examples for common bash tasks like loops, conditionals, functions, and file operations
Include a quick reference section with common bash idioms and gotchas (e.g., quoting rules, variable expansion, exit codes)
Remove all meta-description content ('This skill provides...', 'When to Use...') and replace with actual instructional content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actual information. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific examples. The skill describes what it supposedly does but provides no executable instructions for actually helping with bash scripts. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill mentions 'step-by-step guidance' but provides none. There are no steps, no validation checkpoints, and no actual process to follow. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no structure pointing to detailed materials. No references to other files, no organized sections with actual content to navigate. | 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
994edc4
- 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.