check-bash

I took a look at your check-bash skill and wanted to share some thoughts.

Links:

• GitHub
• Your skill in the SkillzWave marketplace

The TL;DR

You're at 58/100 — F grade territory. This is based on Anthropic's skill best practices rubric. The good news: your spec compliance is solid (11/15), which means the basics are there. The pain points: Utility (9/20) and Progressive Disclosure (16/30) are dragging the score down. You've got a useful core here, but it needs more depth and better support materials.

What's Working Well

• Spec compliance is tight — Valid YAML frontmatter, proper hyphen-case naming (check-bash), and required fields all in place.
• Token economy is excellent — The script is only 15 lines with zero fluff. Every line earns its place.
• Clear triggers — Users know how to activate this: "check bash", "verify syntax", "bash scripts". That's solid discoverability.
• Real use case — Pre-commit syntax validation is a genuine workflow need.

The Big One: Missing Dependency Script

Here's the showstopper: your script delegates to check-bash-syntax.sh on line 6, but that file isn't bundled in the skill package. Users download your skill and get a broken reference.

The fix: Either bundle check-bash-syntax.sh in your scripts/ directory, or inline the syntax checking logic directly. If it's a utility from BitBot proper, document the external dependency clearly in your description. Right now, it'll fail silently or with a cryptic error. This alone is costing you ~4 points.

Other Things Worth Fixing

1. Description needs trigger phrases — Your description says "Check bash script syntax" but doesn't include the actual phrases users say. Add: "Performs check bash operations. Use when asked to 'check bash', 'run check bash', or 'verify bash syntax'." (+2 points)

2. No expected output examples — Users don't know what success looks like. Add a section showing both passing syntax validation and a real error with line numbers. (+3 points)

3. Missing workflow guidance — "Use before committing" is vague. Structure it: 1) Write script 2) Run check-bash 3) Fix errors 4) Commit. Shows the actual workflow. (+2 points)

4. No error handling docs — What do common syntax errors look like? How does bash-check format its output? A quick troubleshooting section fixes this. (+2 points)

Quick Wins

• Bundle or document the check-bash-syntax.sh dependency (high impact, fixes broken functionality)
• Add trigger phrases to your description (easy win, +2 points)
• Include example output showing both success and error cases (clarity boost, +3 points)
• Add a workflow section so users know when/how to use this in their actual process

Focus on the dependency issue first — that's a hard blocker. Then tackle the description and examples. Those three changes alone could push you toward 70+.

Checkout your skill here: SkillzWave.ai | SpillWave We have an agentic skill installer that install skills in 14+ coding agent platforms. Check out this guide on how to improve your agentic skills.