bash-defensive-patterns

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

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 66/100, which puts you in D territory. This is evaluated against Anthropic's best practices for agentic skills. Your strongest area is Spec Compliance (12/15) — the metadata and naming are solid. But Progressive Disclosure Architecture (14/30) is where you're losing the most points. The skill's a flat 534-line file that loads entirely every time, which isn't efficient for how agentic systems work.

What's Working Well

• Solid metadata: Your triggers ('production-grade scripts', 'CI/CD pipelines', 'fault tolerance') are specific and searchable. The skill name follows conventions perfectly.
• Comprehensive coverage: You actually cover the critical patterns — strict mode, error trapping, signal handling. This addresses a real gap in defensive Bash practices.
• Clear organization: Numbered patterns and section headers make manual navigation reasonable, even if it could be better.
• Practical scope: Good balance between providing complete patterns and letting users adapt them to their needs.

The Big One: Progressive Disclosure Architecture

This is your biggest opportunity. Right now, all 10 patterns plus advanced techniques live in one massive file. Users get everything whether they need it or not.

Here's the fix: Break it into a layered structure:

• Create a references/ directory with pattern-specific files: strict-mode.md, error-trapping.md, argument-parsing.md, cleanup-patterns.md, etc.
• Reduce SKILL.md to an 80-line overview that summarizes each pattern and links to the references
• This way, the main file ...