forge-lang-bash

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

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 61/100, which puts you in D territory. This is based on Anthropic's agentic skill best practices. The good news: your writing style is solid (8/10) — the explanations are clear and direct. The challenge: the skill needs better progressive disclosure architecture (18/30) and utility (13/20). You're addressing real bash problems, but the structure and discoverability need work.

What's Working Well

• Writing is clear and technical — No fluff, instructions are straightforward. You nail the imperative voice in code comments.
• File triggers are present — Detecting .sh and .bash files is good, though you could lean harder into action-based triggers.
• Solid templates for common tasks — Your script template and bats test template give users a real starting point.
• TDD cycle is structured — The testing section has clear steps, which is exactly what developers need.

The Big One: Templates Are Bloating Your File

Your SKILL.md is 165 lines, but roughly 50+ of those are embedded code templates. This violates progressive disclosure architecture — you're forcing users to scroll through boilerplate when they just need the concept.

The Fix: Create a references/ directory and move those templates out:

• references/script-template.sh — Your bash script example
• references/test-template.bats — Your bats testing template

Then in SKILL.md, replace the full templates with one-liners like:

See [script template](references/script-template.sh) for a starting point

Impact: This alone gets you +4 points and makes the skill feel less overwhelming.

Other Things W...