shell-scripting

I took a look at your shell-scripting skill and wanted to share some thoughts.

Links:

• GitHub
• Your shell-scripting skill in the SkillzWave marketplace

The TL;DR

You're at 79/100, which puts you in solid C territory. This is based on Anthropic's 5-pillar skill best practices. Your strongest area is Utility (17/20) — the defensive programming patterns and ShellCheck integration genuinely solve real problems. The weakest area is Progressive Disclosure Architecture (18/30), which is the main thing holding you back from a B grade.

What's Working Well

• Practical defensive patterns — Your mandatory foundations (set -euo pipefail, error handling) address real gaps in how most people write shell scripts. The ShellCheck integration as a validation loop is solid.
• Clear structure within the single file — Section headers are logical, patterns are numbered, and the Quick Reference Checklist gives people a concrete path forward. That's good teaching.
• Solid examples — You show complete, runnable templates (simple script, main-function pattern). The Wrong/Correct pairs demonstrate actual anti-patterns developers encounter.
• Good bonus points — The grep-friendly structure and quality pre-commit checklist earned you extra points. Those details matter.

The Big One: Split This Into Multiple Files

Here's the issue: your skill is 574 lines in a single SKILL.md file. That violates progressive disclosure architecture, which Claude skills are supposed to follow. You pack Mandatory Foundations, Core Safety Patterns, Intermediate Patterns, Advanced patterns, and Anti-Patterns all into one file.

Why it matters: New users get overwhelmed. Advanced users have to scroll through basics. Token economy suffers — you're forcing people to load everythin...