git-workflow-specialist

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

Links:

• GitHub
• Your skill on SkillzWave

The TL;DR

You're at 89/100 — solid B-grade territory. This is based on Anthropic's skill best practices rubric. Your strongest area is Progressive Disclosure Architecture (28/30) — the modular structure with separate files for detailed guidance really shines. The weakest spot is Spec Compliance (12/15), mainly around missing metadata that helps people discover and invoke your skill.

What's Working Well

• Architecture is clean — SKILL.md as the entry point with detailed modules in separate files is exactly how PDA should work. You're not dumping everything into one file, which keeps token usage lean.
• Strong utility focus — Your decision matrices and checklists (research-checklist.md, decision frameworks) give people actual tools to work with, not just theory. The problem-solving power here scored 8/8.
• Consistent voice — Imperative form throughout ("Do X", "Check Y") makes instructions clear without being prescriptive. The writing stays objective and instructional.

The Big One: Missing Trigger Phrases

Your description field lacks explicit trigger terms, and this is costing you 2+ points in spec compliance. Right now it reads:

"Git expert covering branching strategies, collaboration, conflict resolution..."

People invoking Claude won't know to call your skill. You need trigger phrases baked into that description. Change it to something like:

"Performs git workflow specialist operations. Use when asked to 'git workflow', 'git branching strategy', 'merge conflict resolution', 'git collaboration patterns', or 'git best practices'."

This small change makes your skill actually discoverable and invokable. It's low-effort, high-impact.

Other Things Worth Fixing

1. Confidence levels are mixed — modules/core-guidance.md has both 🟡 MEDIUM and 🔴 LOW confidence ratings for similar content. Pick one per section so users know what to trust.

2. Light on examples — You've got great conceptual guidance, but adding actual git command examples and workflow templates would bump utility from 18/20 to a solid 20/20. Show the actual commands people run.

3. Table of contents — For files over ~100 lines, a quick TOC at the top helps navigation. Your modules are well-structured but a _toc.md reference at the skill level would make it even clearer.

Quick Wins

✓ Add trigger phrases to description (frontmatter) — +2 points
✓ Consolidate confidence levels in core-guidance.md — +1 point
✓ Sprinkle in command examples (git checkout, merge commands) — +1 point

These three moves get you to 93/100 territory with minimal effort.

Checkout your skill here: SkillzWave.ai | SpillWave We have an agentic skill installer that installs skills in 14+ coding agent platforms. Check out this guide on how to improve your agentic skills.