pm-skill-creator
Design a new PM skill through guided conversation
Install / Use
npx skills add deanpeters/Product-Manager-Skills --skill pm-skill-creatorInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of pm-skill-creator
pm-skill-creator scores 83/100 on our quality scale, 3060th of 4,698 Development & Engineering skills we index.
Its SKILL.md is 16 KB long, well organised into 29 sections and no code examples: a thorough specification that gives an agent plenty to work with.
With 7,063 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 3 months ago, so pm-skill-creator is actively maintained.
- Our last check on 2026-11-06 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-27. Automated pattern scan on 2026-09-27. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
pm-skill-creator compared with similar skills
All 4 of these similar skills score higher than pm-skill-creator; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| pm-skill-creator (this skill)by deanpeters | 83 | 7.1k | 3mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
Frequently asked questions
- How do I install pm-skill-creator?
- Run
npx skills add deanpeters/Product-Manager-Skills --skill pm-skill-creator. The install tabs above show the steps for each supported agent. - Which AI agents does pm-skill-creator work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is pm-skill-creator safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is pm-skill-creator still maintained?
- The repository was last updated about 3 months ago, so pm-skill-creator is actively maintained.
Skill content
View source on GitHubname: pm-skill-creator argument-hint: "[idea or raw content]" description: Design a new PM skill through guided conversation. Use when you have raw content or an idea and want to shape it into a compliant skill. intent: >- Walk through the full skill design process interactively — from raw idea or content to a structured, repo-compliant SKILL.md draft. Asks adaptive questions to determine skill type, scope, structure, and content, then generates a ready-to-validate draft. type: interactive theme: meta-authoring best_for:
- "Turning a rough idea or framework into a structured PM skill"
- "Deciding whether raw content should be a component, interactive, or workflow skill"
- "Getting from blank page to a complete SKILL.md draft through guided conversation" scenarios:
- "I have notes from a workshop and want to turn them into a skill"
- "Help me create a new skill — I know the topic but not the structure"
- "I have a PM framework I want to formalize as a repo skill" estimated_time: "10-15 min"
Purpose
Walk through the full skill design process interactively — from raw idea or content to a structured, repo-compliant SKILL.md draft. Asks adaptive questions to determine skill type, scope, structure, and content, then generates a ready-to-validate draft.
This skill is the conversational complement to skill-authoring-workflow. That skill defines the process and validation gates. This one sits with you and figures out what to build before you build it.
Input
Bring the seed for the skill you want to design — half-formed is fine; shaping it is this skill's job:
- Works best with: the idea, framework, or raw content (notes, prompt sequence, article) the skill should capture
- Also useful: the skill type you suspect it is, who it's for, and any existing skills it should relate to
If you supply this inline with your request (e.g., "help me design a skill from my pricing-tiers framework"), the conversation uses that as the answer to Q1 and moves on — it won't re-ask. With no input, it opens by asking what you want the skill to help someone do.
Example: Use pm-skill-creator: I have a decision tree for choosing north-star metrics — help me shape it into a skill.
Key Concepts
When to Use This vs. Other Authoring Tools
| Tool | Best When |
|------|-----------|
| This skill (skill-creator) | You have an idea or raw content and need help shaping it into the right structure through conversation |
| skill-authoring-workflow | You already know what to build and need the process checklist and validation steps |
| scripts/build-a-skill.sh | You know the structure and want a terminal wizard to collect sections |
| scripts/add-a-skill.sh | You have a source document and want AI-assisted generation end-to-end |
The Three Skill Types (Decision Criteria)
- Component: One artifact or template. Self-contained. Gets referenced by other skills. Ask: "Is this a thing someone creates?"
- Interactive: Guided conversation with adaptive questions and enumerated recommendations. Ask: "Does this require back-and-forth to be useful?"
- Workflow: Multi-phase orchestration referencing other skills. Ask: "Does this coordinate multiple activities across steps?"
Skill Anatomy (Non-Negotiable Sections)
Every skill requires these sections in order:
- Purpose — What it does + when to use it (outcome-focused)
- Input — What the user can bring (subject, optional context), an example invocation, and the rule that inline input counts as answers already given. Must read as an invitation: zero input is fine, the guided flow covers it. Plain language only — no runtime template syntax like
$ARGUMENTS - Key Concepts — Frameworks, definitions, mental models
- Application — Step-by-step instructions an agent can follow
- Examples — At least one concrete, specific example
- Common Pitfalls — Named failure modes with consequences and fixes
- References — Related skills, external frameworks, source material
Metadata Constraints
name: lowercase kebab-case, ≤ 64 charactersdescription: ≤ 200 characters, must include trigger cue ("Use when...")intent: longer repo-facing summary (no character limit)type: one ofcomponent,interactive,workflow
Facilitation Source of Truth
Use workshop-facilitation as the default interaction protocol for this skill.
It defines:
- Session heads-up + entry mode (Guided, Context dump, Best guess)
- One-question turns with plain-language prompts
- Progress labels (e.g., Context Q1/5)
- Interruption handling and pause/resume behavior
- Numbered recommendations at decision points
- Quick-select numbered response options (include
Other (specify)when useful)
This file defines the domain-specific content. If there is a conflict, follow this file's domain logic.
Application
This interactive skill asks up to 5 adaptive questions, then delivers a complete SKILL.md draft with frontmatter, all required sections, and repo-compliant structure.
Step 0: Session Start
Agent says:
"I'll help you design a new PM skill from scratch. This takes about 10-15 minutes and up to 5 questions. How do you want to start?
- Guided — I'll ask questions one at a time and build the skill from your answers (recommended)
- Context dump — Paste your raw content, notes, or framework and I'll propose a skill structure
- Best guess — Tell me just the topic and I'll draft a skill you can refine"
Question 1: What's the Raw Material? (Q1/5)
Agent asks:
"What are we turning into a skill? Give me whatever you have."
- A framework or mental model — A structured way of thinking about a PM problem (e.g., prioritization matrix, decision tree)
- A template or artifact — A deliverable PMs create (e.g., PRD section, positioning statement, epic format)
- A process or workflow — A multi-step method for completing a PM task (e.g., discovery sprint, roadmap planning)
- A coaching or advisory topic — A domain where PMs need guided, adaptive help (e.g., stakeholder navigation, pricing decisions)
Or describe what you have in your own words.
Agent note: If the user pastes raw content instead of choosing an option, analyze the content and infer the answer. Confirm your interpretation before proceeding.
Question 2: Skill Type Decision (Q2/5)
Based on Q1 answer, agent recommends a type and confirms:
If Q1 = Framework or Template:
"This sounds like a component skill — a self-contained artifact or reference. It would include a template, quality criteria, and examples. Does that fit, or is there a conversational/adaptive element I'm missing?
- Yes, component — It's a standalone deliverable or reference
- Actually, it needs conversation — Users need guided questions to use it well (→ interactive)
- It's bigger than one artifact — It orchestrates multiple steps or other skills (→ workflow)"
If Q1 = Process or Workflow:
"This sounds like a workflow skill — a multi-phase process. Does it reference or orchestrate other discrete skills/artifacts, or is it more of a guided conversation?
- Yes, workflow — It has distinct phases and may reference other skills
- It's more conversational — The value comes from adaptive questions and recommendations (→ interactive)
- It's simpler than I described — Really it's one artifact with steps (→ component)"
If Q1 = Coaching or Advisory:
"This sounds like an interactive skill — guided questions that adapt based on answers, ending with enumerated recommendations. Sound right?
- Yes, interactive — It needs back-and-forth to be useful
- It's more of a reference — Users just need the framework, not a conversation (→ component)
- It's a full process — Multiple phases, orchestrates other skills (→ workflow)"
Question 3: Scope and Naming (Q3/5)
Agent asks:
"What should we call this skill? I need two things:
a) A working name — lowercase-kebab-case, max 64 characters (e.g., feature-investment-advisor, user-story, discovery-process)
b) A one-sentence description — What it does + when to use it. Must fit in 200 characters and start with a verb or 'Use when...'
Give me your best attempt and I'll tighten it if needed. Or just describe the skill's purpose and I'll propose both."
Agent note: Validate the name format (kebab-case, ≤ 64 chars) and description length (≤ 200 chars) before proceeding. If either fails, suggest a fix.
Question 4: Key Content (Q4/5)
This question adapts based on skill type from Q2:
For component skills:
"What are the core elements of this artifact or framework? I need:
- The template or structure — What sections/fields does it contain?
- Quality criteria — What separates a good one from a bad one?
- One concrete example — A filled-in version showing it done well; optimally ask for (or generate) a second from a different business domain — one SaaS, one industrial/non-SaaS — so the skill doesn't quietly teach "this only works in SaaS." Use the repo's fictional universes and name the second file by domain (
sample-industrial.md); all example companies must be fictional
Give me whatever you have — bullet points, rough notes, or a full draft."
For interactive skills:
"Walk me through the conversation flow:
- What's the opening question? — What does the user need to tell you first?
- What are the 2-4 branching paths? — How do answers change what comes next?
- What recommendations emerge? — What are the 3-5 outcomes you'd offer?
Give me the decision tree as you see it — even if it's rough."
For workflow skills:
"Map out the phases:
- What are the major steps? (Usually 3-6 phases)
- What's the input and output of each phase?
- Which existing skills does this reference? (Check with
scripts/find-a-skill.sh --keyword <topic>) - Where are the decision points?
Give me the flow — sequential, branching, or both."
Question 5: Pitfalls and Edge Cases (Q5/5)
Agent asks:
"What goes wrong when people do this badly? I need 2-3 failure modes:
- Name the failure — Give it a label (e.g., 'Metrics Theater', 'Hero Syndrome')
- Describe the consequence — What happens when someone falls into this trap?
- State the fix — What's the corrective action?
If you're not sure, tell me the most common mistake you've seen and I'll help structure it."
Draft Generation
After collecting answers to Q1-Q5, the agent generates a complete SKILL.md draft including:
- YAML frontmatter —
name,description,intent,type,best_for,scenarios,estimated_time - Purpose — Synthesized from Q1 + Q3
- Input — Derived from Q2/Q3: what the user provides, an example invocation, and the inline-input rule (use what's supplied, don't re-ask)
- Key Concepts — Structured from Q4 content
- Application — Step-by-step instructions derived from Q4
- Examples — Concrete example from Q4 (or generated if not provided); dual-domain (SaaS + industrial) is the quality bar for full adornment
- Common Pitfalls — Structured from Q5
- References — Related skills identified during conversation + source material
Agent says after generating:
"Here's your draft SKILL.md. Before we call it done:
- Review the draft — Does it capture your intent?
- Run validation —
python3 scripts/check-skill-metadata.py skills/<name>/SKILL.md - Check triggers —
python3 scripts/check-skill-triggers.py skills/<name>/SKILL.md --show-cases - Smoke test —
./scripts/test-a-skill.sh --skill <name> --smoke
Want me to adjust anything, or are you ready to validate?"
Examples
Example: Framework → Component Skill
Q1: "1 — A framework. It's a 2x2 matrix for evaluating build-vs-buy decisions." Q2: "1
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
