pursuit-governance

I took a look at pursuit-governance and noticed you're tackling workflow orchestration for AI agents—that's a non-trivial problem space. The 67/100 score suggests the core concept is solid, but there might be some gaps in how the guidance flows or how accessible the skill is for developers who aren't already deep in agentic patterns.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 67/100, which is D territory. This is based on Anthropic's Progressive Disclosure Architecture and skill usability standards. Your strongest area is Spec Compliance (11/15), but you're leaving points on the table with Progressive Disclosure (18/30) and Utility (13/20). The good news: targeted fixes could push you into the 80s pretty easily.

What's Working Well

• Clean metadata – Your YAML frontmatter is valid and follows conventions (5/5 on frontmatter validity)
• Consistent terminology – "Pursuits," "cadences," and "escalation" are used uniformly throughout, which makes the skill easier to follow
• Real problem focus – You're addressing an actual governance gap for enterprise deals, not solving imaginary problems
• Structural headers – Framework, Tips, and Templates sections are logically organized

The Big One: Missing Templates and Reference Architecture

Here's what's killing your utility score: you mention three templates (pursuit governance calendar, decision log sheet, escalation matrix) but don't actually provide them. For a governance skill, that's like shipping a CLI tool without the command reference. Users read "Decision log sheet (request, owner, status, timestamp)" and think "okay, I need to build this myself"—which defeats the purpose.

Fix: Create a references/ directory with thre...