Guides contributors from a PM skill idea to a complete Skill Implementation Packet aligned with pm-skills conventions. Runs gap analysis, validates through a Why Gate, classifies by type and phase, generates draft files, and writes to a staging area for review before promotion.
SkillScore73Maintained
Automatic
◆Product Management pack
Last verified 8/19/2026
What it changes
Passed 16 of 22 test cases with the skill, and 4 of 22 without it.
Without skill18%
With skill73%
Checks it passed that the model alone missed
Advises against creating a new skill.
The directory name uses the develop- prefix.
The directory name uses the utility- prefix.
and 14 more in the full report
12 fixed4 passed either way6 still failing0 broke
Pass-rate lift
+55 pp
Tokens
+161%
Agent turns
0%
Response time
-42%
Measured 8/19/2026v1 · latest is v216 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.8-flash on 10/20/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
See it in action
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 12
Prompt
When generating the catalog registration entry for AGENTS.md, what heading level and path formatting must be used?
What was checked, without and with the skill
Checked
Without skill
With skill
Uses #### for the skill heading and **Path:** for the repository path.
Missed
Passed
case-22 · gemini-3.6-flash · 8/19/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md350 lines3 files
PM Skill Builder
This skill creates new PM skills for the pm-skills library. It produces a
Skill Implementation Packet - a complete design document with draft files
in a staging area for review before promotion to canonical locations.
When to Use
When you have an idea for a new PM skill
When you want to add a domain skill (phase-specific), foundation skill
(cross-cutting), or utility skill (meta/tooling) to the pm-skills library
When a contributor needs guided skill creation that follows repo conventions
When NOT to Use
To modify or improve an existing skill → use utility-pm-skill-iterate
To audit an existing skill against conventions → use utility-pm-skill-validate
To create a skill for a non-pm-skills context → use a general agent skill builder
To create a workflow → workflows are authored directly, not via this builder
Instructions
When asked to create a new PM skill, follow these steps:
Step 1: Understand the Idea
Accept the idea in either form:
Problem-first: "What PM problem does this skill solve? Who runs into
this problem, and what do they currently produce (or fail to produce)?"
Skill-first: "Describe the skill you want to create. What artifact
does it produce? What PM activity does it support?"
Both entry points produce the same downstream flow. If the user provides
one form, do not ask for the other - extract what you need and proceed.
If the idea is vague, ask ONE follow-up question to clarify the artifact
type and target audience before proceeding.