القائمة
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.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/TuYv/ccpm --skill pm-skill-creatorيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Use when auditing a paid ad account for incremental contribution, wasted spend, or measurement integrity before scaling; runs a typed 20-item ROAS profile with verified vetoes and a SHIP/FIX/BLOCK/UNDECIDED gate on own exported data. Not for campaign structure design — use campaign-architect; not for creative production — use ad-creative-builder. 付费广告账户审计/ROAS评分
Use when the user asks to "write ad copy", "generate RSA headlines", or "build ad creative at volume"; produces ad units — RSA headlines/descriptions, hooks, and an angle matrix — message-matched to the destination landing page. Not for scoring an ad account — use ad-account-auditor; not for the post-click page — use landing-optimizer; not for organic articles — use content-writer. 广告创意/广告文案/RSA标题
Use when the user asks to "design an A/B test", "set up a creative/landing test", "run an incrementality test", or "is this result statistically and practically material?"; produces a hypothesis, variant matrix, sample-size/duration/power plan, and a documented effect/uncertainty read from own exported results. It applies only a precommitted owner-approved action rule; the statistical helper never chooses a business action. Not for producing variants — use ad-creative-builder; not for reading back one shipped change — use paid-measurement-loop. 广告AB测试设计/实验设计/显著性判定/增效测试
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | 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 |
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.
Bring the seed for the skill you want to design — half-formed is fine; shaping it is this skill's job:
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.
| 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 |
Every skill requires these sections in order:
$ARGUMENTSname: lowercase kebab-case, ≤ 64 charactersdescription: ≤ 200 characters, must include trigger cue ("Use when...")intent: longer repo-facing summary (no character limit)type: one of component, interactive, workflowUse workshop-facilitation as the default interaction protocol for this skill.
It defines:
Other (specify) when useful)This file defines the domain-specific content. If there is a conflict, follow this file's domain logic.
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.
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?
Agent asks:
"What are we turning into a skill? Give me whatever you have."
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.
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?
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?
If Q1 = Coaching or Advisory:
"This sounds like an interactive skill — guided questions that adapt based on answers, ending with enumerated recommendations. Sound right?
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.
This question adapts based on skill type from Q2:
For component skills:
"What are the core elements of this artifact or framework? I need:
sample-industrial.md); all example companies must be fictionalGive me whatever you have — bullet points, rough notes, or a full draft."
For interactive skills:
"Walk me through the conversation flow:
Give me the decision tree as you see it — even if it's rough."
For workflow skills:
"Map out the phases:
scripts/find-a-skill.sh --keyword <topic>)Give me the flow — sequential, branching, or both."
Agent asks:
"What goes wrong when people do this badly? I need 2-3 failure modes:
If you're not sure, tell me the most common mistake you've seen and I'll help structure it."
After collecting answers to Q1-Q5, the agent generates a complete SKILL.md draft including:
name, description, intent, type, best_for, scenarios, estimated_timeAgent says after generating:
"Here's your draft SKILL.md. Before we call it done:
python3 scripts/check-skill-metadata.py skills/<name>/SKILL.mdpython3 scripts/check-skill-triggers.py skills/<name>/SKILL.md --show-cases./scripts/test-a-skill.sh --skill <name> --smokeWant me to adjust anything, or are you ready to validate?"
Q1: "1 — A framework. It's a 2x2 matrix for evaluating build-vs-buy decisions."
Q2: "1 — Yes, component."
Q3: "Name: build-vs-buy-matrix. Description: 'Evaluate build-vs-buy decisions using a 2x2 matrix of strategic value and implementation complexity. Use when choosing between building internally and buying a solution.'"
Q4: "The axes are strategic differentiation (low/high) and implementation complexity (low/high). Four quadrants: Buy (low/low), Partner (low/high), Build (high/low), Invest (high/high). Quality criteria: each quadrant has a clear decision rule and one example."
Q5: "Biggest mistake: treating it as a one-time decision. Consequence: you build something, market shifts, and you're stuck maintaining undifferentiated tech. Fix: revisit quarterly."
Output: Complete component skill with template, filled example, and the quarterly-review pitfall.
Q1: "4 — Coaching topic. Helping PMs navigate their first pricing conversation with leadership."
Q2: "1 — Yes, interactive."
Q3: "Name: pricing-conversation-advisor. Description: 'Prepare for your first pricing conversation with leadership. Use when presenting pricing changes or new monetization to executives.'"
Q4: "Opening question: What's the pricing change? Branches: new product pricing, price increase on existing, freemium-to-paid conversion, usage-based transition. Recommendations: data to bring, objection handling, framing strategies."
Q5: "Failure mode: 'Leading with the Number.' Consequence: executives fixate on the price point instead of the strategy. Fix: always lead with the business case and customer impact before revealing the number."
Output: Complete interactive skill with 3-question flow, 4 branches, and enumerated recommendations per branch.
Q1: "I want a skill that covers all of product strategy — vision, roadmaps, OKRs, prioritization, stakeholder alignment, and metrics."
Agent response: "That's 4-6 separate skills, not one. Let's pick the one that matters most right now and build that. Which piece is most urgent?
roadmap-planning)prioritization-advisor)Start with one. We can build the others after."
Symptom: Calling something a "workflow" when it's really a template with numbered steps.
Consequence: Over-engineered skill that references non-existent sub-skills and confuses users.
Fix: Apply the type decision questions from Q2 honestly. If it doesn't orchestrate other skills or have distinct phases with different inputs/outputs, it's probably a component.
Symptom: Description says what the skill is ("A framework for pricing decisions") but not when to use it.
Consequence: Claude can't match user requests to the skill. It sits unused.
Fix: Every description must answer "Use when..." — e.g., "Evaluate pricing decisions using a structured framework. Use when choosing between pricing models or preparing a pricing proposal."
Symptom: "The draft looks good, let's ship it."
Consequence: Broken frontmatter, missing sections, failed cross-references, inconsistent catalog counts.
Fix: Always run check-skill-metadata.py and check-skill-triggers.py before considering the skill done. No exceptions.
Symptom: Trying to pack an entire domain into one skill.
Consequence: A 500-line monster that does nothing well. Too broad to trigger accurately, too long to be useful.
Fix: One skill = one job. If you need more than 6 application steps or more than 4 branches, you probably need multiple skills.
skill-authoring-workflow — The process checklist and validation gates; use after this skill generates a draftworkshop-facilitation — Facilitation protocol for this interactive skillscripts/build-a-skill.sh — Terminal wizard for section-by-section skill creationscripts/add-a-skill.sh — Content-first automated skill generatorscripts/check-skill-metadata.py — Structural validationscripts/check-skill-triggers.py — Trigger-readiness auditscripts/test-a-skill.sh — Full quality gatescripts/find-a-skill.sh — Check for overlapping skills before creatingCLAUDE.md — Master skill distillation protocol and quality standardsdocs/Building PM Skills.md — Manual skill creation guidedocs/Add-a-Skill Utility Guide.md — Automated creation guide