creating-branch

I took a look at your creating-branch skill and wanted to share some thoughts.

Links:

• GitHub
• Your skill in the SkillzWave marketplace

The TL;DR

You're at 60/100, which puts you in D territory. The skill has solid bones—your workflow is clear and handles edge cases well—but it's getting dinged hard on spec compliance. The good news? This is fixable with some structured improvements. Your strongest area is Ease of Use (21/25), but Spec Compliance (0/15) is completely broken, which is dragging your score down.

What's Working Well

• Clear workflow structure: Your 5-phase approach with validation gates is easy to follow. The decision tree for branch naming (auto-generate vs. explicit) gives users real flexibility without being overwhelming.
• Solid edge case handling: You're thinking about uncommitted changes, determining base branches intelligently, and providing explicit error recovery paths. That's the kind of detail that makes a skill actually usable.
• Consistent terminology: Using "mainline," "base branch," and "feature branch" consistently throughout keeps readers oriented.

The Big One: Fix Your Frontmatter

Your YAML frontmatter is invalid and incomplete—it's literally cut off mid-description. This is why you scored 0/15 on spec compliance. Fix this:

Current (broken):

---
name: creating-branch
description: Standard workflow for all branch operations ('create branch', 'new branch', 'start branch for'): replaces bash-based git checkout/branch workflows—determines bas

Should be:

---
name: creating-branch
description: Creates feature branches following convention-based naming and error recovery. Use when asked to "create branch", "new branch", or "start a branch for [feature]".
trigg...