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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill bash-script-helperOverall
score
17%
Does it follow best practices?
Validation for skill structure
Activation
0%This description is severely lacking across all dimensions. It provides no concrete capabilities, uses redundant and unnatural trigger terms, fails to explain when the skill should be used, and is too generic to distinguish from other DevOps or scripting skills. The description reads more like a category label than a functional skill description.
Suggestions
Add specific capabilities the skill provides, e.g., 'Write, debug, and explain bash scripts. Convert commands to reusable scripts. Add error handling and logging to shell scripts.'
Add a 'Use when...' clause with natural trigger terms like 'Use when the user asks about bash scripts, shell scripting, .sh files, automating terminal commands, or writing shell functions.'
Remove the duplicate trigger term and replace with varied natural phrases users would actually say, such as 'bash', 'shell script', 'automate', 'command line script', '.sh file'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only 'Bash Script Helper' which is a name, not a capability. There's no indication of what the skill actually does (e.g., write scripts, debug scripts, explain syntax). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' (no capabilities listed) and 'when should Claude use it' (no explicit use-case guidance beyond the unhelpful duplicate trigger term). | 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 'shell script', 'bash', '.sh files', 'scripting', 'automation'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'helper' is extremely generic and 'DevOps Basics' is a broad category. Without specific capabilities or triggers, this could conflict with any shell, scripting, or DevOps-related skill. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%This skill is a placeholder template with no actual content. It repeatedly references 'bash script helper' without defining what that means or providing any actionable guidance, code examples, or concrete instructions. The entire document could be replaced with a single sentence: 'This skill helps with bash scripts' and convey the same (lack of) information.
Suggestions
Add concrete bash script examples showing common patterns (e.g., argument parsing, error handling, logging)
Include executable code snippets for specific tasks like 'creating a deployment script' or 'writing a backup script'
Define what 'bash script helper' actually means - list specific capabilities like shellcheck integration, shebang best practices, or portable scripting techniques
Remove generic boilerplate sections ('Capabilities', 'Example Triggers') and replace with actual technical content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic filler text that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless without specifics. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance is provided. The entire skill describes what it does abstractly without showing how to actually help with bash scripts. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps or procedures. | 1 / 3 |
Progressive Disclosure | No useful structure or references to detailed content. The sections are organizational boilerplate with no substantive content to organize or link to. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
- 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.