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]".
triggers:
  - "create branch"
  - "new branch"
  - "start branch for"
---

This alone will bump you ~9 points by making your skill actually parseable and discoverable.

Other Things Worth Fixing

1. Add a table of contents: At ~200 lines, readers need signposts. Add a quick "## Contents" section listing your 5 phases after the metadata. Low effort, +2 points.

2. Missing input/output examples: You hint at how names are generated ("adding metrics" → "adding-metrics") but don't show a full user interaction. Add one concrete example: User: "create branch for login refactor" → Result: feature/login-refactor created from main. Helps people understand expected behavior immediately.

3. Tighten your validation gates: Lines like "IF base branch successfully determined → PROCEED to Phase 3" could be condensed. Try: "Success → Phase 3 | Failure → ask user for explicit base branch." Cuts verbosity, same clarity.

Quick Wins

• Fix frontmatter YAML (+9 points) - close the tag, complete the description, add trigger phrases
• Add TOC (+2 points) - one small section at the top
• One example walkthrough (+1 point) - shows real-world usage
• Tighten validation phrasing (+1 point) - cuts bloat, improves readability

You've got a genuinely useful skill here—the logic is solid and it solves a real problem. Getting the spec stuff squared away and adding that example will take you from 60 to ~73, which is a meaningful jump.

Checkout your skill here: SkillzWave.ai | SpillWave 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.