Feedback on your mastering-git-cli skill

[RichardHightower]

I took a look at your mastering-git-cli skill and wanted to share some thoughts.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 90/100, solid A-grade territory. This is based on Anthropic's best practices for agentic skills. Your strongest area is Progressive Disclosure Architecture (28/30) — the way you've layered the 428-line SKILL.md with 9 focused reference files is chef's kiss. Where there's room to improve: Spec Compliance (12/15) and Utility (18/20).

What's Working Well

• Progressive Disclosure is genuinely excellent. Your decision trees (sync/create/merge workflows), the foundational concepts split into separate references, and the clear separation between SKILL.md and deep dives shows you understand token economy. Every reference is exactly one level deep from the main file.
• Trigger coverage is comprehensive. You've nailed the discovery angle — git commands, merge conflicts, rebase operations, worktrees, CI/CD integration, large repo optimization. Developers will find this when they need it.
• Anti-patterns and verification commands are embedded intelligently. The bisect run pattern and the pre-commit checklist are solid touches that actually help people avoid mistakes.

The Big One

SKILL.md needs a table of contents. At 428 lines, it's crossed the readability threshold. Right now someone scrolling through hits decision trees, Easy Buttons, script usage, references, critical knowledge, 2025 features — all without a map. Add a TOC after your Triggers section with anchors to each section. This should bump you +1 point toward that 91.

Other Things Worth Fixing

1. Scripts lack explicit expected output examples. You describe what they do, but showing the actual result of git worktree list or the merge output helps users verify they're on track. Add an "Expected Output" block to each script snippet. (+0.5 points)

2. Config repetition in foundations.md. You show individual git config commands, then repeat them again in the combined .gitconfig block. Keep just the annotated .gitconfig version — cleaner and saves tokens. (+0.5 points)

3. Description could use more trigger phrases. Currently it's strong but dense. Add a few more keywords like "parallel development", "feature branches", "conflict resolution" to the metadata description for better discoverability. (+0.5 points)

Quick Wins

• Add TOC to SKILL.md (biggest bang for effort)
• Add "Expected Output" blocks to your script examples
• Trim the config repetition in foundations.md
• Expand trigger phrases in metadata

These three changes could realistically bump you to 92-93/100.

---

Checkout your skill here: [SkillzWave.ai](https://skillzwave.ai) | [SpillWave](https://spillwave.com) 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.