All Skills
mySecond includes a skill for every core PM job, organized by category. Skills with a slash command have a dedicated tutorial. Skills without a command work by describing what you want in the chat — just be specific about the what, the for what, and point Claude to any relevant files.
Discovery (10 skills)
| Skill | Command | What you give it | What you get | Time saved |
|---|---|---|---|---|
| User Interview Analyzer | /user-interview-analyzer | One interview transcript (paste or file) | JTBD statements, opportunities, key quotes | 1-2 hrs → 5 min |
| Research Synthesis Engine | /research-synthesis-engine | Multiple interview/research files in discovery/inputs/ | Cross-file patterns, themes, prioritized insights, optional jobs-to-be-done lens | 4 hrs → 3 min |
| Persona Generator | /persona-generator | Research files or synthesized findings | 2-3 behavioral personas with JTBD, pains, gains | 3-4 hrs → 10 min |
| Opportunity Solution Tree Builder | — | Desired outcome + research findings | OST linking outcome → opportunities → solutions | 2-3 hrs → 10 min |
| Journey Map Creator | — | User type + key job to be done | Journey map with touchpoints, emotions, pain points | 4-6 hrs → 15 min |
| Feedback Categorizer | — | Raw feedback dump (support tickets, app reviews, NPS, feature requests) | Themed and prioritized feedback clusters | 2-3 hrs → 5 min |
| Survey Question Generator | /survey-question-generator | Research objective + audience description | Survey with unbiased questions and analysis plan | 3-4 hrs → 15 min |
Tutorials: Analyze an Interview · Build Personas · Analyze All Your Research at Once
Competitive (4 skills)
| Skill | Command | What you give it | What you get | Time saved |
|---|---|---|---|---|
| Competitive Profile Builder | /competitive-profile-builder | Competitor name (+ optional URL or notes) | Structured profile: positioning, strengths, weaknesses, how to beat them | 15 hrs → 5 min |
| Competitive Intel Pack (workflow) | /workflow-competitive-intel-pack | List of 1-5 competitor names | Sourced landscape map, competitor profiles, feature and pricing comparison | 4 hrs → 30 min |
| Market Sizing Calculator | — | Market description + target segment | TAM, SAM, SOM with methodology and assumptions | 4-6 hrs → 10 min |
| Win/Loss Analyzer | — | Sales call notes or win/loss interview transcripts | Patterns in why you win and lose, prioritized fixes | 1-2 days → 15 min |
Tutorials: Analyze a Competitor · Analyze Multiple Competitors at Once
Strategy (10 skills)
| Skill | Command | What you give it | What you get | Time saved |
|---|---|---|---|---|
| Set Goals | /set-goals | Goal description or a draft of your OKRs | Measurable, outcome-focused OKRs saved to goals.md, or a review of your draft | 2 hrs → 10 min |
| Prioritization Engine | — | Feature/initiative list or full backlog + scoring criteria | RICE or ICE scores, ranked list with rationale | 3-4 hrs → 10 min |
| Positioning Statement Generator | /positioning-statement-generator | Target customer, competitors, key differentiators | Positioning using April Dunford's Obviously Awesome framework, with an optional Value Proposition Canvas | 3 hrs → 10 min |
| Go-to-Market Strategy | /go-to-market-strategy | Feature or product description + launch date | GTM plan: channels, messaging, timeline, success metrics | 6-8 hrs → 30 min |
| Decision Maker | /decision-maker | Decision description + options or constraints (time, cost, team) | Recommendation with tradeoff analysis, including build vs. buy, and a decision record | 4-6 hrs → 15 min |
| Pricing Strategy Analyzer | /pricing-strategy-analyzer | Current pricing + competitive context + customer segments | Pricing strategy with packaging options and revenue modeling | 2-3 days → 30 min |
Planning (5 skills)
| Skill | Command | What you give it | What you get | Time saved |
|---|---|---|---|---|
| Roadmap Builder | /roadmap-builder | Goals, initiatives list, time horizon | Structured roadmap with themes, sequencing, and rationale, or a quarterly plan with bets | 4-6 hrs → 15 min |
| Sprint Planning Assistant | /sprint-planning-assistant | Backlog items + team capacity | Sprint plan with goals, committed work, and buffer | 2 hrs → 10 min |
Specs (8 skills)
| Skill | Command | What you give it | What you get | Time saved |
|---|---|---|---|---|
| PRD Generator | /prd-generator | Problem description + any relevant context | Complete PRD: problem, solution, requirements, success metrics | 4-6 hrs → 10 min |
| One-Pager Creator | — | Feature idea or problem statement | One-page proposal or product brief for quick stakeholder alignment | 1-2 hrs → 5 min |
| User Story Writer | — | Feature description or acceptance criteria notes | Feature split into shippable slices, with user stories and acceptance criteria, ready for sprint | 30 min → 2 min |
| Onboarding Flow Designer | /onboarding-flow-designer | User type + desired activation event | Onboarding flow with steps, triggers, and fallback paths | 1-2 days → 15 min |
Tutorial: Create a PRD
Data (6 skills)
| Skill | Command | What you give it | What you get | Time saved |
|---|---|---|---|---|
| Metric Framework Builder | — | Product description + business goals | Metrics framework with a North Star, leading and lagging indicators, and an optional dashboard spec | 4-6 hrs → 15 min |
| A/B Test Analyzer | — | Test results (control vs. variant data) | Analysis with recommendation and confidence level | 2-3 hrs → 10 min |
| Funnel Analyzer | — | Funnel step names + conversion rates | Drop-off analysis with root causes and fix recommendations | 2-3 hrs → 10 min |
| Experiment Designer | /experiment-designer | Hypothesis + metric to move | A/B test or experiment design with methodology, sample size, timeline | 2-3 hrs → 15 min |
Communication (5 skills)
| Skill | Command | What you give it | What you get | Time saved |
|---|---|---|---|---|
| Stakeholder Simulator | /stakeholder-simulator | Doc to review (PRD, spec, proposal — paste or file) | Feedback from CTO, UX, Sales, Exec, and User Advocate | 5 hrs → 5 min |
| Executive Update Generator | /executive-update-generator | Current status notes (rough is fine) | Structured executive update in SCARF format, or a board update | 1 hr → 5 min |
| Meeting Notes Processor | /meeting-notes-processor | Raw meeting notes (paste or file) | Decisions, action items, key points — cleaned up | 30 min → 2 min |
Tutorials: Write a Status Update · Process Meeting Notes · Get Stakeholder Feedback
Launch (5 skills)
| Skill | Command | What you give it | What you get | Time saved |
|---|---|---|---|---|
| Launch Checklist Generator | /launch-checklist-generator | Feature/product description + launch date | Launch checklist covering eng, design, marketing, legal, support | 2-3 hrs → 10 min |
| Release Notes Pro | /release-notes-pro | What shipped (feature name + what it does) | Benefit-first release notes in multiple formats, plus customer announcements | 1 hr → 5 min |
| Sales Enablement Kit | — | Feature or product description | Sales kit: battlecard, talk track, objection handling, one-pager | 6-8 hrs → 20 min |
Tutorial: Write Release Notes
Operations (5 skills)
| Skill | Command | What you give it | What you get | Time saved |
|---|---|---|---|---|
| Sprint Retro Facilitator | /sprint-retro-facilitator | Sprint summary or team feedback (or nothing — Claude will ask) | Structured retro with what went well, what didn't, action items | 1 hr → 10 min |
| Process Documentation | /process-documentation | Process description or rough notes | Process doc with step-by-step instructions and quick reference checklist | 2-3 hrs → 10 min |
Using skills without a slash command
For skills without a dedicated command, just describe what you want in the chat. The formula that works:
"[Skill task] for [specific context]. Use [file or data]."
Examples:
- "Build an Opportunity Solution Tree for reducing churn. Use the interview transcripts in
discovery/inputs/and ourpersonas.md." - "Design an A/B test for our pricing page — testing whether showing annual pricing first increases upgrades. Use the metrics in my context files."
- "Extract JTBD statements from the 5 interviews in
discovery/inputs/."
Bad ask: "a/b test" — Claude needs to know what, for what, and where to look.
Claude already knows your company from your context files. You just need to tell it what to build.