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: "Perform...