[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"extension-skill-marfoerst-pm-postmortem-de":3,"guides-for-marfoerst-pm-postmortem":901,"similar-k1734q48va5bhhmrzp3pm507zh86mdfb-de":902},{"_creationTime":4,"_id":5,"children":6,"community":7,"display":9,"evaluation":15,"identity":259,"isFallback":251,"parentExtension":265,"providers":334,"relations":338,"repo":339,"tags":899,"workflow":900},1778692726926.7598,"k1734q48va5bhhmrzp3pm507zh86mdfb",[],{"reviewCount":8},0,{"description":10,"installMethods":11,"name":13,"sourceUrl":14},"Blameless incident and failure post-mortem generator using 5 Whys root cause analysis. Produces structured post-mortem documents with timeline, contributing factors, corrective actions, and lessons learned. Tracks MTTR and detection time metrics. Use when someone says \"post-mortem\", \"postmortem\", \"incident review\", \"root cause analysis\", \"5 whys\", \"what happened\", \"outage review\", \"failure analysis\", \"RCA\".\n",{"claudeCode":12},"marfoerst/the-pragmatic-pm","PM Post-Mortem Facilitator","https://github.com/marfoerst/the-pragmatic-pm",{"_creationTime":16,"_id":17,"extensionId":5,"locale":18,"result":19,"trustSignals":243,"workflow":257},1778693394157.6245,"kn70fg2tvp6w6sv6zc4k6yw7cs86mqxe","en",{"checks":20,"evaluatedAt":192,"extensionSummary":193,"features":194,"nonGoals":200,"practices":204,"prerequisites":209,"promptVersionExtension":213,"promptVersionScoring":214,"purpose":215,"rationale":216,"score":217,"summary":218,"tags":219,"targetMarket":225,"tier":226,"useCases":227,"workflow":232},[21,26,29,32,36,39,44,48,51,54,58,62,65,69,72,75,78,81,84,87,91,95,99,103,107,110,114,117,121,124,127,130,133,136,139,143,147,150,153,157,160,163,166,169,173,176,179,182,185,189],{"category":22,"check":23,"severity":24,"summary":25},"Practical Utility","Problem relevance","pass","The description clearly names the problem of generating blameless incident post-mortems and the specific user intent related to incident review and root cause analysis.",{"category":22,"check":27,"severity":24,"summary":28},"Unique selling proposition","The skill offers a specific methodology (5 Whys), structured output, and metrics tracking (MTTR, detection time), which is more than a thin wrapper or default LLM behavior.",{"category":22,"check":30,"severity":24,"summary":31},"Production readiness","The skill generates structured post-mortem documents covering the full lifecycle from incident clarification to corrective actions and lessons learned.",{"category":33,"check":34,"severity":24,"summary":35},"Scope","Single responsibility principle","The skill is focused on facilitating blameless post-mortems and incident analysis, with a clear scope around this specific task.",{"category":33,"check":37,"severity":24,"summary":38},"Description quality","The description is accurate, concise, and effectively communicates the skill's purpose and usage triggers.",{"category":40,"check":41,"severity":42,"summary":43},"Invocation","Scoped tools","not_applicable","This skill appears to be a single, coherent LLM interaction and does not expose distinct tools with verb-noun names.",{"category":45,"check":46,"severity":42,"summary":47},"Documentation","Configuration & parameter reference","The skill does not expose configurable parameters or options that require documentation beyond its core interaction flow.",{"category":33,"check":49,"severity":42,"summary":50},"Tool naming","The skill does not expose individual tools with names, relying on a conversational interface.",{"category":33,"check":52,"severity":42,"summary":53},"Minimal I/O surface","As this is a conversational skill, its I/O surface is managed by the LLM's conversational interface and not exposed as specific tool parameters.",{"category":55,"check":56,"severity":24,"summary":57},"License","License usability","The extension is licensed under the MIT License, which is a permissive open-source license.",{"category":59,"check":60,"severity":24,"summary":61},"Maintenance","Commit recency","The latest commit was on 2026-04-15, which is within the last 90 days.",{"category":59,"check":63,"severity":42,"summary":64},"Dependency Management","The skill does not appear to have external dependencies that require explicit management.",{"category":66,"check":67,"severity":24,"summary":68},"Security","Secret Management","The skill's functionality does not involve handling or exposing secrets.",{"category":66,"check":70,"severity":24,"summary":71},"Injection","The skill's interaction model and context reading (`domain-context.md`) appear to treat external data as contextual rather than executable instructions.",{"category":66,"check":73,"severity":24,"summary":74},"Transitive Supply-Chain Grenades","The skill does not fetch remote content or execute code outside of its bundle.",{"category":66,"check":76,"severity":24,"summary":77},"Sandbox Isolation","The skill operates within the LLM's sandbox and does not appear to interact with or modify files outside its designated scope.",{"category":66,"check":79,"severity":24,"summary":80},"Sandbox escape primitives","No detached-process spawns or deny-retry loops were found in the skill's logic.",{"category":66,"check":82,"severity":24,"summary":83},"Data Exfiltration","The skill's documented purpose does not involve reading or submitting confidential data to third parties.",{"category":66,"check":85,"severity":24,"summary":86},"Hidden Text Tricks","The bundled content and descriptions appear free of hidden-steering tricks or malicious Unicode characters.",{"category":88,"check":89,"severity":24,"summary":90},"Hooks","Opaque code execution","The skill's logic is presented in readable Markdown and does not contain obfuscated code like base64 payloads or eval statements.",{"category":92,"check":93,"severity":24,"summary":94},"Portability","Structural Assumption","The skill relies on `domain-context.md` and `personal-context.md` which are designed to be customized, rather than assuming a specific project structure.",{"category":96,"check":97,"severity":24,"summary":98},"Trust","Issues Attention","There are 0 open and 0 closed issues in the last 90 days, indicating low activity but no negative signal for engagement.",{"category":100,"check":101,"severity":24,"summary":102},"Versioning","Release Management","The README and SKILL.md mention install methods referencing specific versions or the main branch, and the code itself has recent commits, indicating a managed release.",{"category":104,"check":105,"severity":42,"summary":106},"Execution","Validation","The skill's interaction is conversational, and explicit schema validation for parameters is not applicable in this context.",{"category":66,"check":108,"severity":24,"summary":109},"Unguarded Destructive Operations","The skill's primary function is document generation, not destructive operations.",{"category":111,"check":112,"severity":24,"summary":113},"Code Execution","Error Handling","The skill's interaction flow is managed by the LLM, which inherently handles errors gracefully by re-prompting or indicating inability to fulfill a request.",{"category":111,"check":115,"severity":24,"summary":116},"Logging","The README mentions a `Usage Logger` hook that logs skill execution to `~/.claude/pm-toolkit/audit.jsonl`.",{"category":118,"check":119,"severity":24,"summary":120},"Compliance","GDPR","The skill's primary function is generating post-mortem documents based on user input and context files, not processing personal data directly without sanitization.",{"category":118,"check":122,"severity":24,"summary":123},"Target market","The skill is domain-agnostic and does not contain regional or jurisdictional logic, making it globally applicable.",{"category":92,"check":125,"severity":24,"summary":126},"Runtime stability","The skill's logic is contained within the LLM environment and does not make assumptions about specific operating systems or shells.",{"category":45,"check":128,"severity":24,"summary":129},"README","The README is comprehensive, detailing installation, setup, skills, workflows, agents, design principles, customization, and frameworks.",{"category":33,"check":131,"severity":42,"summary":132},"Tool surface size","This is a single skill and does not expose multiple distinct tools.",{"category":40,"check":134,"severity":42,"summary":135},"Overlapping near-synonym tools","The skill does not expose multiple tools, so there are no overlapping synonyms.",{"category":45,"check":137,"severity":24,"summary":138},"Phantom features","All advertised features, including the core post-mortem generation, are implemented and described in the SKILL.md and README.",{"category":140,"check":141,"severity":24,"summary":142},"Install","Installation instruction","The README provides clear installation instructions and usage examples for the plugin and individual skills.",{"category":144,"check":145,"severity":24,"summary":146},"Errors","Actionable error messages","The skill's interaction flow, managed by the LLM, will naturally prompt for clarification or indicate when it cannot fulfill a request, acting as actionable error reporting.",{"category":104,"check":148,"severity":42,"summary":149},"Pinned dependencies","The skill does not appear to have third-party dependencies that require pinning via lockfiles.",{"category":33,"check":151,"severity":42,"summary":152},"Dry-run preview","The skill's output is generated text, not a state-changing operation that would benefit from a dry-run mode.",{"category":154,"check":155,"severity":42,"summary":156},"Protocol","Idempotent retry & timeouts","The skill does not involve remote calls or state-changing operations that would require idempotency or timeouts.",{"category":118,"check":158,"severity":24,"summary":159},"Telemetry opt-in","The README indicates a `Usage Logger` hook that logs skill execution to `audit.jsonl` and implies this is for analytics, which is generally opt-in by default for such logging mechanisms.",{"category":40,"check":161,"severity":24,"summary":162},"Precise Purpose","The description clearly states the skill generates blameless post-mortems using 5 Whys and provides specific triggers for its use.",{"category":40,"check":164,"severity":24,"summary":165},"Concise Frontmatter","The frontmatter in SKILL.md is concise and effectively summarizes the core capability and trigger phrases.",{"category":45,"check":167,"severity":24,"summary":168},"Concise Body","The SKILL.md is well-structured with distinct sections and avoids excessive length, deferring deeper material as described in the README.",{"category":170,"check":171,"severity":24,"summary":172},"Context","Progressive Disclosure","The skill documentation outlines a clear interaction flow and refers to external context files (`domain-context.md`) for deeper information.",{"category":170,"check":174,"severity":42,"summary":175},"Forked exploration","The skill's workflow does not involve deep exploration or code review that would necessitate a forked context.",{"category":22,"check":177,"severity":24,"summary":178},"Usage examples","The README provides a table with suggested starting points and usage patterns for various skills, including a clear example invocation for the plugin itself.",{"category":22,"check":180,"severity":24,"summary":181},"Edge cases","The SKILL.md details a structured interaction flow with clear steps for clarifying the incident, and the facilitation tips address potential issues like shallow root causes.",{"category":111,"check":183,"severity":42,"summary":184},"Tool Fallback","The skill does not rely on external tools like a custom MCP server with fallbacks.",{"category":186,"check":187,"severity":24,"summary":188},"Safety","Halt on unexpected state","The skill's interactive nature and structured prompting encourage users to provide necessary information, implicitly halting if crucial details are missing.",{"category":92,"check":190,"severity":24,"summary":191},"Cross-skill coupling","The skill is self-contained and does not appear to implicitly rely on other skills. It does not explicitly cross-link to sibling skills.",1778693394040,"This skill acts as a blameless post-mortem facilitator, guiding users through incident analysis using the 5 Whys methodology to produce structured post-mortem documents. It collects details on incident impact, timeline, root cause, contributing factors, and corrective actions, also tracking metrics like MTTR and detection time.",[195,196,197,198,199],"Generates blameless incident post-mortem documents","Utilizes 5 Whys for root cause analysis","Includes structured sections for timeline, contributing factors, and corrective actions","Tracks key incident metrics (MTTR, detection time)","Adapts to company/personal context via `domain-context.md` and `personal-context.md`",[201,202,203],"Assigning blame to individuals for incidents.","Performing real-time incident response or mitigation.","Generating generic incident reports without user-provided context.",[205,206,207,208],"Blameless analysis","Root cause identification","Actionable corrective planning","Metric tracking",[210,211,212],"Access to the `marfoerst/the-pragmatic-pm` plugin","Ability to provide incident details and context","Optional: Customized `domain-context.md` and `personal-context.md` files for tailored output","3.0.0","4.4.0","To streamline and standardize the process of conducting blameless incident post-mortems, ensuring thorough analysis and actionable outcomes.","The extension is exceptionally well-documented and robust, with no critical or warning findings. The only minor areas were 'not_applicable' for aspects not relevant to a conversational skill.",99,"High-quality, well-documented skill for generating blameless incident post-mortems.",[220,221,222,223,224],"post-mortem","incident-management","root-cause-analysis","5-whys","documentation","global","verified",[228,229,230,231],"When an incident requires a formal post-mortem review.","To establish a consistent process for analyzing failures and identifying systemic causes.","To generate structured documentation for incident follow-up and prevention.","When needing to track and improve MTTR and detection times.",[233,234,235,236,237,238,239,240,241,242],"Clarify incident details (what happened, impact, timeline)","Generate post-mortem document template","Fill in metadata, metrics, executive summary, customer impact","Construct incident timeline","Perform 5 Whys root cause analysis","Identify contributing factors, what went well, and what went poorly","Define corrective actions with owners and deadlines","Document lessons learned","Conduct domain-specific compliance checks if applicable","Determine output delivery method (chat, file, Notion)",{"codeQuality":244,"collectedAt":246,"documentation":247,"maintenance":250,"security":254,"testCoverage":256},{"hasLockfile":245},false,1778693377328,{"descriptionLength":248,"readmeSize":249},411,16111,{"closedIssues90d":8,"forks":8,"hasChangelog":251,"openIssues90d":8,"pushedAt":252,"stars":253},true,1776252922000,6,{"hasNpmPackage":245,"license":255,"smitheryVerified":245},"MIT",{"hasCi":245,"hasTests":245},{"updatedAt":258},1778693394157,{"basePath":260,"githubOwner":261,"githubRepo":262,"locale":18,"slug":263,"type":264},"skills/pm-postmortem","marfoerst","the-pragmatic-pm","pm-postmortem","skill",{"_creationTime":266,"_id":267,"community":268,"display":269,"identity":274,"parentExtension":277,"providers":310,"relations":330,"tags":331,"workflow":332},1778692726926.7524,"k17ehawghqbe3ff7rxmq9cq1xs86nm21",{"reviewCount":8},{"description":270,"installMethods":271,"name":273,"sourceUrl":14},"PM leadership toolkit: 45 skills + 5 agents + 5 workflows + 4 hooks for product teams. Enforces problem clarity, leading+lagging metrics, and scope discipline. Domain-agnostic — customize via domain-context.md for your company, industry, and compliance requirements.",{"claudeCode":272},"pm-toolkit","PM Leadership Toolkit",{"basePath":275,"githubOwner":261,"githubRepo":262,"locale":18,"slug":262,"type":276},"","plugin",{"_creationTime":278,"_id":279,"community":280,"display":281,"identity":285,"providers":287,"relations":304,"tags":306,"workflow":307},1778692726926.7522,"k176y75es9j5jccf2knfgvtv7x86m7z0",{"reviewCount":8},{"description":282,"installMethods":283,"name":284,"sourceUrl":14},"PM leadership toolkit: 43 skills + 5 agents + 4 workflows for product teams",{"claudeCode":12},"The Pragmatic PM",{"basePath":275,"githubOwner":261,"githubRepo":262,"locale":18,"slug":262,"type":286},"marketplace",{"evaluate":288,"extract":298},{"promptVersionExtension":289,"promptVersionScoring":214,"score":290,"tags":291,"targetMarket":225,"tier":297},"3.1.0",79,[292,293,294,295,296],"product-management","b2b-saas","leadership","productivity","workflows","community",{"commitSha":299,"license":255,"marketplace":300,"plugin":302},"HEAD",{"name":262,"pluginCount":301},1,{"mcpCount":8,"provider":303,"skillCount":8},"classify",{"repoId":305},"kd731k864fr1ezp8r85ecbhz9986mzz7",[293,294,292,295,296],{"evaluatedAt":308,"extractAt":309,"updatedAt":308},1778692746860,1778692726926,{"evaluate":311,"extract":327},{"promptVersionExtension":213,"promptVersionScoring":214,"score":312,"tags":313,"targetMarket":225,"tier":297},95,[292,293,314,315,316,317,318,319,320,321,322,323,324,325,326],"pm-leadership","quality-gate","prd","okr","discovery","metrics","sales-enablement","go-to-market","battlecard","gtm","ai-pricing","migration","process-documentation",{"commitSha":299,"license":255,"plugin":328},{"mcpCount":8,"provider":303,"skillCount":329},50,{"parentExtensionId":279,"repoId":305},[324,293,322,318,321,323,319,325,317,314,316,326,292,315,320],{"evaluatedAt":333,"extractAt":309,"updatedAt":333},1778692775030,{"evaluate":335,"extract":337},{"promptVersionExtension":213,"promptVersionScoring":214,"score":217,"tags":336,"targetMarket":225,"tier":226},[220,221,222,223,224],{"commitSha":299,"license":255},{"parentExtensionId":267,"repoId":305},{"_creationTime":340,"_id":305,"identity":341,"providers":342,"workflow":895},1778692722125.5374,{"githubOwner":261,"githubRepo":262,"sourceUrl":14},{"classify":343,"discover":885,"github":888},{"commitSha":299,"extensions":344},[345,358,487,496,504,512,520,528,536,544,552,560,568,576,584,592,600,608,616,624,632,640,648,656,664,672,680,688,696,704,712,720,725,733,741,749,757,765,773,781,789,797,805,813,821,829,837,845,853,861,869,877],{"basePath":275,"description":282,"displayName":262,"installMethods":346,"rationale":347,"selectedPaths":348,"source":357,"sourceLanguage":18,"type":286},{"claudeCode":12},"marketplace.json at .claude-plugin/marketplace.json",[349,352,354],{"path":350,"priority":351},".claude-plugin/marketplace.json","mandatory",{"path":353,"priority":351},"README.md",{"path":355,"priority":356},"LICENSE","high","rule",{"basePath":275,"description":270,"displayName":272,"installMethods":359,"rationale":360,"selectedPaths":361,"source":357,"sourceLanguage":18,"type":276},{"claudeCode":272},"plugin manifest at .claude-plugin/plugin.json",[362,364,365,366,369,371,373,375,377,379,381,383,385,387,389,391,393,395,397,399,401,403,405,407,409,411,413,415,417,419,421,423,425,427,429,431,433,435,437,439,441,443,445,447,449,451,453,455,457,459,461,463,465,467,469,471,473,475,477,479,481,483,485],{"path":363,"priority":351},".claude-plugin/plugin.json",{"path":353,"priority":351},{"path":355,"priority":356},{"path":367,"priority":368},"skills/pm-ab-test/SKILL.md","medium",{"path":370,"priority":368},"skills/pm-ai-pricing/SKILL.md",{"path":372,"priority":368},"skills/pm-battlecard/SKILL.md",{"path":374,"priority":368},"skills/pm-board-deck/SKILL.md",{"path":376,"priority":368},"skills/pm-build-vs-buy/SKILL.md",{"path":378,"priority":368},"skills/pm-customer-success/SKILL.md",{"path":380,"priority":368},"skills/pm-dashboard-designer/SKILL.md",{"path":382,"priority":368},"skills/pm-decision-document/SKILL.md",{"path":384,"priority":368},"skills/pm-devils-advocate/SKILL.md",{"path":386,"priority":368},"skills/pm-executive-update/SKILL.md",{"path":388,"priority":368},"skills/pm-feature-requests/SKILL.md",{"path":390,"priority":368},"skills/pm-feedback-categorizer/SKILL.md",{"path":392,"priority":368},"skills/pm-funnel-analyzer/SKILL.md",{"path":394,"priority":368},"skills/pm-gtm-launch/SKILL.md",{"path":396,"priority":368},"skills/pm-hub/SKILL.md",{"path":398,"priority":368},"skills/pm-journey-map/SKILL.md",{"path":400,"priority":368},"skills/pm-jtbd/SKILL.md",{"path":402,"priority":368},"skills/pm-meeting-notes/SKILL.md",{"path":404,"priority":368},"skills/pm-messaging-framework/SKILL.md",{"path":406,"priority":368},"skills/pm-metric-framework/SKILL.md",{"path":408,"priority":368},"skills/pm-migration-planner/SKILL.md",{"path":410,"priority":368},"skills/pm-north-star/SKILL.md",{"path":412,"priority":368},"skills/pm-objection-handler/SKILL.md",{"path":414,"priority":368},"skills/pm-okr/SKILL.md",{"path":416,"priority":368},"skills/pm-onboarding-flow/SKILL.md",{"path":418,"priority":368},"skills/pm-one-pager/SKILL.md",{"path":420,"priority":368},"skills/pm-opportunity-tree/SKILL.md",{"path":422,"priority":368},"skills/pm-pe-migration-report/SKILL.md",{"path":424,"priority":368},"skills/pm-persona-generator/SKILL.md",{"path":426,"priority":368},"skills/pm-postmortem/SKILL.md",{"path":428,"priority":368},"skills/pm-prd/SKILL.md",{"path":430,"priority":368},"skills/pm-pricing/SKILL.md",{"path":432,"priority":368},"skills/pm-process-docs/SKILL.md",{"path":434,"priority":368},"skills/pm-product-brief/SKILL.md",{"path":436,"priority":368},"skills/pm-quarterly-planning/SKILL.md",{"path":438,"priority":368},"skills/pm-release-notes/SKILL.md",{"path":440,"priority":368},"skills/pm-review/SKILL.md",{"path":442,"priority":368},"skills/pm-risk-register/SKILL.md",{"path":444,"priority":368},"skills/pm-sales-deck/SKILL.md",{"path":446,"priority":368},"skills/pm-sprint-retro/SKILL.md",{"path":448,"priority":368},"skills/pm-stakeholder-simulator/SKILL.md",{"path":450,"priority":368},"skills/pm-strategic-review/SKILL.md",{"path":452,"priority":368},"skills/pm-swot/SKILL.md",{"path":454,"priority":368},"skills/pm-value-prop-canvas/SKILL.md",{"path":456,"priority":368},"skills/pm-win-loss/SKILL.md",{"path":458,"priority":368},"skills/pm-workflow-competitive-intel/SKILL.md",{"path":460,"priority":368},"skills/pm-workflow-migration/SKILL.md",{"path":462,"priority":368},"skills/pm-workflow-problem-to-prd/SKILL.md",{"path":464,"priority":368},"skills/pm-workflow-quarterly-cycle/SKILL.md",{"path":466,"priority":368},"skills/pm-workflow-sales-enablement/SKILL.md",{"path":468,"priority":356},"agents/pm-comms-writer.md",{"path":470,"priority":356},"agents/pm-data-analyst.md",{"path":472,"priority":356},"agents/pm-discovery-lead.md",{"path":474,"priority":356},"agents/pm-gtm-strategist.md",{"path":476,"priority":356},"agents/pm-ops-facilitator.md",{"path":478,"priority":356},"hooks/context-reinject.sh",{"path":480,"priority":356},"hooks/hooks.json",{"path":482,"priority":356},"hooks/quality-gate.sh",{"path":484,"priority":356},"hooks/usage-logger.sh",{"path":486,"priority":356},"hooks/workflow-tracker.sh",{"basePath":488,"description":489,"displayName":490,"installMethods":491,"rationale":492,"selectedPaths":493,"source":357,"sourceLanguage":18,"type":264},"skills/pm-ab-test","Design rigorous A/B tests with hypothesis formulation, sample size calculation, success criteria, guardrail metrics, and rollout planning. Includes Bayesian vs frequentist guidance and compliance-aware staged rollout for ERP features. Use when someone says \"A/B test\", \"experiment\", \"split test\", \"hypothesis\", \"test this feature\", \"should we experiment\", \"sample size\", \"statistical significance\".\n","pm-ab-test",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-ab-test/SKILL.md",[494],{"path":495,"priority":351},"SKILL.md",{"basePath":497,"description":498,"displayName":499,"installMethods":500,"rationale":501,"selectedPaths":502,"source":357,"sourceLanguage":18,"type":264},"skills/pm-ai-pricing","AI pricing strategy for SaaS products. Covers embed-vs-charge decisions, AI cost modeling, value quantification, packaging AI features, WTP research, and AI-specific pricing metrics. Use when someone says \"AI pricing\", \"how to price AI\", \"price AI feature\", \"AI add-on\", \"AI copilot pricing\", \"AI agent pricing\", \"charge for AI\", \"AI monetization\", \"AI cost model\", \"inference costs\", \"AI credits\", \"AI packaging\", \"per-agent pricing\", \"AI willingness to pay\", \"AI embed or charge\", \"AI margin\", \"copilot tax\", or \"AI pricing strategy\".\n","pm-ai-pricing",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-ai-pricing/SKILL.md",[503],{"path":495,"priority":351},{"basePath":505,"description":506,"displayName":507,"installMethods":508,"rationale":509,"selectedPaths":510,"source":357,"sourceLanguage":18,"type":264},"skills/pm-battlecard","Per-competitor sales battlecard — a 1-page scannable cheat sheet a rep pulls up mid-call. Competitive positioning, objection handling, landmine questions, proof points, and deal stage guidance. Use when someone says \"battlecard\", \"competitive cheat sheet\", \"how do we sell against\", \"competitor comparison\", \"competitive positioning\", \"sales enablement\", \"win against\", \"deal strategy against [competitor]\", \"they're evaluating [competitor]\".\n","pm-battlecard",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-battlecard/SKILL.md",[511],{"path":495,"priority":351},{"basePath":513,"description":514,"displayName":515,"installMethods":516,"rationale":517,"selectedPaths":518,"source":357,"sourceLanguage":18,"type":264},"skills/pm-board-deck","Generate content for board or investor deck presentations. Creates the narrative arc, key slides content, and talking points. Covers: market context, product progress, metrics, roadmap, asks. Use when someone says \"board deck\", \"investor deck\", \"board meeting\", \"quarterly board update\", or \"prepare for the board\".\n","pm-board-deck",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-board-deck/SKILL.md",[519],{"path":495,"priority":351},{"basePath":521,"description":522,"displayName":523,"installMethods":524,"rationale":525,"selectedPaths":526,"source":357,"sourceLanguage":18,"type":264},"skills/pm-build-vs-buy","Build/buy/partner decision framework with scoring across time-to-value, TCO, strategic control, and integration complexity. Use when someone says \"build or buy\", \"build vs buy\", \"should we build this\", \"vendor evaluation\", \"make or buy\", \"partnership evaluation\", \"third-party vs in-house\", \"buy vs partner\".\n","pm-build-vs-buy",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-build-vs-buy/SKILL.md",[527],{"path":495,"priority":351},{"basePath":529,"description":530,"displayName":531,"installMethods":532,"rationale":533,"selectedPaths":534,"source":357,"sourceLanguage":18,"type":264},"skills/pm-customer-success","Customer success playbook generator for lifecycle stages: onboarding, adoption, expansion, renewal, churn prevention. Creates playbooks with triggers, actions, owners, and health indicators. Domain-aware: adapts to compliance and onboarding requirements from domain-context.md. Use when someone says \"customer success\", \"CS playbook\", \"onboarding playbook\", \"churn prevention\", \"renewal\", \"expansion\", \"customer health\", \"lifecycle\", \"adoption\", \"NRR\".\n","pm-customer-success",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-customer-success/SKILL.md",[535],{"path":495,"priority":351},{"basePath":537,"description":538,"displayName":539,"installMethods":540,"rationale":541,"selectedPaths":542,"source":357,"sourceLanguage":18,"type":264},"skills/pm-dashboard-designer","Analytics dashboard design tool. Defines audience, selects leading + lagging metrics, designs information hierarchy, and specifies data sources. Follows dashboard design principles: most important metric top-left, comparison context, anomaly highlighting. Use when someone says \"dashboard\", \"analytics\", \"metrics dashboard\", \"KPI dashboard\", \"reporting\", \"data visualization\", \"executive dashboard\", \"product dashboard\".\n","pm-dashboard-designer",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-dashboard-designer/SKILL.md",[543],{"path":495,"priority":351},{"basePath":545,"description":546,"displayName":547,"installMethods":548,"rationale":549,"selectedPaths":550,"source":357,"sourceLanguage":18,"type":264},"skills/pm-decision-document","Create ADR-style product decision records. Documents context, options considered, trade-offs, the decision made, and consequences. Enforces that alternatives were considered. Use when someone says \"decision doc\", \"ADR\", \"we decided to\", \"document this decision\", \"why did we choose\", or \"decision record\".\n","pm-decision-document",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-decision-document/SKILL.md",[551],{"path":495,"priority":351},{"basePath":553,"description":554,"displayName":555,"installMethods":556,"rationale":557,"selectedPaths":558,"source":357,"sourceLanguage":18,"type":264},"skills/pm-devils-advocate","Structured challenge of product decisions with pre-mortem and counter-arguments. Use when someone says \"challenge this\", \"devil's advocate\", \"poke holes\", \"stress test\", \"pre-mortem\", \"what could go wrong\", \"am I missing something\", \"sanity check this decision\".\n","pm-devils-advocate",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-devils-advocate/SKILL.md",[559],{"path":495,"priority":351},{"basePath":561,"description":562,"displayName":563,"installMethods":564,"rationale":565,"selectedPaths":566,"source":357,"sourceLanguage":18,"type":264},"skills/pm-executive-update","Generate SCQA-structured executive or investor updates. Covers weekly status reports, monthly business reviews, and quarterly investor updates. Concise, board-ready, focused on outcomes not activities. Use when someone says \"executive update\", \"status report\", \"investor update\", \"board update\", \"what should I report?\", or \"monthly business review\".\n","pm-executive-update",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-executive-update/SKILL.md",[567],{"path":495,"priority":351},{"basePath":569,"description":570,"displayName":571,"installMethods":572,"rationale":573,"selectedPaths":574,"source":357,"sourceLanguage":18,"type":264},"skills/pm-feature-requests","Analyze, categorize, and prioritize feature requests using affinity mapping, frequency-severity scoring, and demand curve analysis. Ingest from pasted lists, CSV, or freeform text. Flags compliance/regulatory implications automatically. Use when someone says \"feature requests\", \"customer requests\", \"what should we build\", \"request backlog\", \"prioritize requests\", \"demand analysis\", \"feature voting\".\n","pm-feature-requests",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-feature-requests/SKILL.md",[575],{"path":495,"priority":351},{"basePath":577,"description":578,"displayName":579,"installMethods":580,"rationale":581,"selectedPaths":582,"source":357,"sourceLanguage":18,"type":264},"skills/pm-feedback-categorizer","Categorize user feedback using affinity mapping. Ingest from multiple sources, de-duplicate, cluster into themes, score by frequency + severity + sentiment, and output a theme map with representative quotes and recommended actions. Distinguishes bugs, feature requests, usability issues, and praise. Use when someone says \"categorize feedback\", \"sort feedback\", \"feedback analysis\", \"NPS comments\", \"what are users saying\", \"support themes\", \"voice of customer\".\n","pm-feedback-categorizer",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-feedback-categorizer/SKILL.md",[583],{"path":495,"priority":351},{"basePath":585,"description":586,"displayName":587,"installMethods":588,"rationale":589,"selectedPaths":590,"source":357,"sourceLanguage":18,"type":264},"skills/pm-funnel-analyzer","Diagnose conversion funnel drop-offs, generate hypotheses, and recommend interventions with success metrics. Includes statistical significance guidance and domain-specific funnel stages from domain-context.md. Use when someone says \"funnel\", \"conversion\", \"drop-off\", \"activation\", \"onboarding\", \"churn\", \"retention\", \"pipeline\", \"trial to paid\".\n","pm-funnel-analyzer",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-funnel-analyzer/SKILL.md",[591],{"path":495,"priority":351},{"basePath":593,"description":594,"displayName":595,"installMethods":596,"rationale":597,"selectedPaths":598,"source":357,"sourceLanguage":18,"type":264},"skills/pm-gtm-launch","Go-to-market launch playbook for a feature, module, or product. Generates cross-functional checklists, enablement timelines, communication plans, and success metrics. Scales from lightweight P2 launches to full P0 GTM motions. Use when someone says \"launch plan\", \"go-to-market\", \"GTM\", \"launch playbook\", \"launch checklist\", \"feature launch\", \"product launch\", \"release planning\", \"launch readiness\", or \"launch brief\".\n","pm-gtm-launch",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-gtm-launch/SKILL.md",[599],{"path":495,"priority":351},{"basePath":601,"description":602,"displayName":603,"installMethods":604,"rationale":605,"selectedPaths":606,"source":357,"sourceLanguage":18,"type":264},"skills/pm-hub","Master PM skill router. Lists all available PM skills by category and routes to the right one based on user intent. Use when someone says \"help me with PM work\", \"what PM skills are available\", \"I need to write a...\", or any vague product management request. Entry point for the PM Toolkit plugin.\n","pm-hub",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-hub/SKILL.md",[607],{"path":495,"priority":351},{"basePath":609,"description":610,"displayName":611,"installMethods":612,"rationale":613,"selectedPaths":614,"source":357,"sourceLanguage":18,"type":264},"skills/pm-journey-map","Customer journey mapping across the full lifecycle: awareness through renewal. Maps actions, touchpoints, emotions, pain points, and opportunities per stage. Domain-aware: includes compliance and onboarding milestones from domain-context.md. Use when someone says \"journey map\", \"customer journey\", \"user journey\", \"experience map\", \"touchpoints\", \"pain points\", \"customer experience\", \"CX mapping\".\n","pm-journey-map",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-journey-map/SKILL.md",[615],{"path":495,"priority":351},{"basePath":617,"description":618,"displayName":619,"installMethods":620,"rationale":621,"selectedPaths":622,"source":357,"sourceLanguage":18,"type":264},"skills/pm-jtbd","Jobs-to-be-Done discovery and analysis using Christensen/Ulwick methodology. Three modes: write JTBD interview scripts, extract job statements from transcripts, or prioritize outcomes by importance vs satisfaction. Use when someone says \"JTBD\", \"jobs to be done\", \"interview script\", \"customer jobs\", \"outcome-driven\", \"what are customers trying to do\", \"job statements\".\n","pm-jtbd",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-jtbd/SKILL.md",[623],{"path":495,"priority":351},{"basePath":625,"description":626,"displayName":627,"installMethods":628,"rationale":629,"selectedPaths":630,"source":357,"sourceLanguage":18,"type":264},"skills/pm-meeting-notes","Create structured PM meeting notes with decisions, action items, open questions, and parking lot. Works from raw notes, transcripts, or memory. Use when someone says \"meeting notes\", \"action items\", \"what did we decide?\", \"summarize this meeting\", or \"process these notes\".\n","pm-meeting-notes",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-meeting-notes/SKILL.md",[631],{"path":495,"priority":351},{"basePath":633,"description":634,"displayName":635,"installMethods":636,"rationale":637,"selectedPaths":638,"source":357,"sourceLanguage":18,"type":264},"skills/pm-messaging-framework","Messaging framework for consistent customer-facing language across all touchpoints. Positioning statements, value pillars, elevator pitches, per-persona and per-competitor messaging. Use when someone says \"messaging framework\", \"positioning statement\", \"elevator pitch\", \"value pillars\", \"how do we talk about this\", \"sales messaging\", \"competitive messaging\", \"product messaging\", \"positioning\", \"tagline\", \"one-liner\", \"how do we position against\".\n","pm-messaging-framework",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-messaging-framework/SKILL.md",[639],{"path":495,"priority":351},{"basePath":641,"description":642,"displayName":643,"installMethods":644,"rationale":645,"selectedPaths":646,"source":357,"sourceLanguage":18,"type":264},"skills/pm-metric-framework","Build a complete metric hierarchy from North Star through input metrics, health metrics, and counter metrics. Enforces leading + lagging indicators at every level. Includes instrumentation guidance and AARRR/custom framework decomposition. Use when someone says \"metric framework\", \"measurement plan\", \"KPI hierarchy\", \"AARRR metrics\", \"pirate metrics\", \"health metrics\", \"counter metrics\", \"leading indicators\", \"instrumentation\", \"analytics plan\", or \"how do we measure success\".\n","pm-metric-framework",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-metric-framework/SKILL.md",[647],{"path":495,"priority":351},{"basePath":649,"description":650,"displayName":651,"installMethods":652,"rationale":653,"selectedPaths":654,"source":357,"sourceLanguage":18,"type":264},"skills/pm-migration-planner","Migration planning skill for platform migrations, data migrations, product consolidations, vendor/API swaps, and compliance-driven migrations. Generates feature parity matrices, data migration plans, go/no-go gate frameworks, customer communication playbooks, and legacy sunset plans. Use when someone says \"migration plan\", \"platform migration\", \"data migration\", \"product consolidation\", \"vendor migration\", \"API migration\", \"compliance migration\", \"feature parity\", \"cutover plan\", \"migration readiness\", \"legacy sunset\", \"decommission\", \"strangler fig\", \"parallel run\", or \"migration strategy\".\n","pm-migration-planner",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-migration-planner/SKILL.md",[655],{"path":495,"priority":351},{"basePath":657,"description":658,"displayName":659,"installMethods":660,"rationale":661,"selectedPaths":662,"source":357,"sourceLanguage":18,"type":264},"skills/pm-north-star","Define and validate a North Star metric and its input metric tree for a B2B SaaS product. Uses Sean Ellis criteria for validation. Builds the full metric hierarchy from North Star down to team-level input metrics. Use when someone says \"north star metric\", \"what should we measure\", \"product metric\", \"input metrics\", \"metric tree\", \"Sean Ellis\", \"one metric that matters\", \"how do we know if we're winning\", or \"product health metric\".\n","pm-north-star",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-north-star/SKILL.md",[663],{"path":495,"priority":351},{"basePath":665,"description":666,"displayName":667,"installMethods":668,"rationale":669,"selectedPaths":670,"source":357,"sourceLanguage":18,"type":264},"skills/pm-objection-handler","Objection handling playbook organized by category. Teaches reps to diagnose the real concern behind the stated objection and respond with evidence, not clever comebacks. Use when someone says \"objection handling\", \"how do we respond when they say\", \"too expensive\", \"competitor says\", \"they have concerns about\", \"common objections\", \"sales objections\", \"objection playbook\", \"why do we lose deals\", \"buyer pushback\", \"handle pricing objection\", \"they think we're too small\".\n","pm-objection-handler",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-objection-handler/SKILL.md",[671],{"path":495,"priority":351},{"basePath":673,"description":674,"displayName":675,"installMethods":676,"rationale":677,"selectedPaths":678,"source":357,"sourceLanguage":18,"type":264},"skills/pm-okr","Full OKR lifecycle: define, refine, check-in, score, and align OKRs across organizational levels. Enforces outcome-over-output writing standards, leading vs lagging KR balance, and strategic alignment mapping. Use when someone says \"OKRs\", \"objectives and key results\", \"write OKRs\", \"review our OKRs\", \"OKR check-in\", \"score OKRs\", \"grade OKRs\", \"mid-quarter review\", \"OKR alignment\", \"cascade OKRs\", \"are our OKRs good\", \"help me write key results\", \"quarterly goals\", \"OKR scoring\", \"OKR retrospective\", or \"team objectives\".\n","pm-okr",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-okr/SKILL.md",[679],{"path":495,"priority":351},{"basePath":681,"description":682,"displayName":683,"installMethods":684,"rationale":685,"selectedPaths":686,"source":357,"sourceLanguage":18,"type":264},"skills/pm-onboarding-flow","Design SaaS onboarding flows with time-to-first-value analysis, activation metric definition, and progressive disclosure patterns. Maps current flows, identifies the \"aha moment\", and designs optimal paths to activation. Use when someone says \"onboarding\", \"time to value\", \"activation\", \"first-run experience\", \"setup wizard\", \"aha moment\", \"TTFV\", \"user activation\", \"onboarding checklist\", \"empty states\", \"progressive disclosure\", or \"new user experience\".\n","pm-onboarding-flow",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-onboarding-flow/SKILL.md",[687],{"path":495,"priority":351},{"basePath":689,"description":690,"displayName":691,"installMethods":692,"rationale":693,"selectedPaths":694,"source":357,"sourceLanguage":18,"type":264},"skills/pm-one-pager","Create an executive one-pager for initiatives and proposals. Structured as: Problem, Approach, Metrics, Timeline, Ask. Maximum one page. Use when someone says \"one pager\", \"executive summary\", \"initiative brief\", \"proposal\", \"I need to pitch this\", or \"summarize this for leadership\".\n","pm-one-pager",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-one-pager/SKILL.md",[695],{"path":495,"priority":351},{"basePath":697,"description":698,"displayName":699,"installMethods":700,"rationale":701,"selectedPaths":702,"source":357,"sourceLanguage":18,"type":264},"skills/pm-opportunity-tree","Teresa Torres Opportunity Solution Tree: outcome, opportunity space, solutions, experiments. Use when someone says \"opportunity tree\", \"OST\", \"opportunity solution tree\", \"discovery\", \"what should we build\", \"map opportunities\", \"Teresa Torres\", \"continuous discovery\".\n","pm-opportunity-tree",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-opportunity-tree/SKILL.md",[703],{"path":495,"priority":351},{"basePath":705,"description":706,"displayName":707,"installMethods":708,"rationale":709,"selectedPaths":710,"source":357,"sourceLanguage":18,"type":264},"skills/pm-pe-migration-report","PE board migration progress report generator. Produces a 1-page dashboard for PE operating partners covering ARR migration status, wave progress, synergy realization, risks, and customer health. Designed for busy board members who scan 10-15 portfolio reports per month. Use when someone says \"PE report\", \"migration board update\", \"PE operating review\", \"ARR migration status\", \"synergy report\", \"portfolio migration update\", \"board migration progress\".\n","pm-pe-migration-report",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-pe-migration-report/SKILL.md",[711],{"path":495,"priority":351},{"basePath":713,"description":714,"displayName":715,"installMethods":716,"rationale":717,"selectedPaths":718,"source":357,"sourceLanguage":18,"type":264},"skills/pm-persona-generator","Data-driven persona creation grounded in behavioral patterns, not demographics. Guides you from raw data to validated persona profiles with goals, frustrations, decision criteria, and tools. Use when someone says \"persona\", \"user profile\", \"who are our users\", \"customer segments\", \"target audience\", \"ICP\", \"ideal customer profile\".\n","pm-persona-generator",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-persona-generator/SKILL.md",[719],{"path":495,"priority":351},{"basePath":260,"description":10,"displayName":263,"installMethods":721,"rationale":722,"selectedPaths":723,"source":357,"sourceLanguage":18,"type":264},{"claudeCode":12},"SKILL.md frontmatter at skills/pm-postmortem/SKILL.md",[724],{"path":495,"priority":351},{"basePath":726,"description":727,"displayName":728,"installMethods":729,"rationale":730,"selectedPaths":731,"source":357,"sourceLanguage":18,"type":264},"skills/pm-prd","Generate a Product Requirements Document (PRD) with four modes: Full PRD for net-new features, Lightweight Feature Spec for sprint-level work, Iteration/V2 Spec for follow-ups on shipped features, and Migration/Compliance Spec for regulatory or API migrations. Enforces problem-first thinking, leading + lagging metrics, non-goals, and testable acceptance criteria. Use when someone says \"PRD\", \"product requirements\", \"feature spec\", \"write a spec\", \"requirements document\", \"what to build\", \"engineering spec\", \"technical requirements\", \"migration spec\", \"compliance spec\", \"V2 spec\", or \"iteration spec\".\n","pm-prd",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-prd/SKILL.md",[732],{"path":495,"priority":351},{"basePath":734,"description":735,"displayName":736,"installMethods":737,"rationale":738,"selectedPaths":739,"source":357,"sourceLanguage":18,"type":264},"skills/pm-pricing","SaaS pricing analysis. Covers value metrics, packaging, willingness-to-pay research, competitive positioning, and pricing model design. Use when someone says \"pricing strategy\", \"how should we price this\", \"packaging\", \"willingness to pay\", \"Van Westendorp\", \"price sensitivity\", \"monetization\", \"competitive pricing\", \"premium tier\", \"pricing page\", \"value metric\", \"Gabor-Granger\", \"behavioral pricing\", \"feature shock\", \"pricing failure\", \"WTP segmentation\", \"monetization failure\", or \"pricing integrity\".\n","pm-pricing",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-pricing/SKILL.md",[740],{"path":495,"priority":351},{"basePath":742,"description":743,"displayName":744,"installMethods":745,"rationale":746,"selectedPaths":747,"source":357,"sourceLanguage":18,"type":264},"skills/pm-process-docs","SOP and runbook generator for PM processes. Documents steps, decision points, checklists, ownership, and compliance checkpoints. Produces actionable runbooks. Use when someone says \"SOP\", \"standard operating procedure\", \"runbook\", \"process doc\", \"how do we do X\", \"document the process\", \"playbook\", \"checklist\", \"workflow documentation\".\n","pm-process-docs",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-process-docs/SKILL.md",[748],{"path":495,"priority":351},{"basePath":750,"description":751,"displayName":752,"installMethods":753,"rationale":754,"selectedPaths":755,"source":357,"sourceLanguage":18,"type":264},"skills/pm-product-brief","Create a lightweight product brief using Amazon-style working-backwards method. Starts with the customer outcome (press release), then works back to requirements. One page max. Use when someone says \"product brief\", \"working backwards\", \"PR/FAQ\", \"pitch this feature\", \"one-page brief\", or \"write the press release first\".\n","pm-product-brief",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-product-brief/SKILL.md",[756],{"path":495,"priority":351},{"basePath":758,"description":759,"displayName":760,"installMethods":761,"rationale":762,"selectedPaths":763,"source":357,"sourceLanguage":18,"type":264},"skills/pm-quarterly-planning","Full quarter planning: strategic themes, capacity allocation, dependency mapping, bet sizing, and commitment plans. Use when someone says \"plan next quarter\", \"quarterly planning\", \"Q2 planning\", \"capacity planning\", \"what should we build next quarter\", \"quarter kickoff\".\n","pm-quarterly-planning",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-quarterly-planning/SKILL.md",[764],{"path":495,"priority":351},{"basePath":766,"description":767,"displayName":768,"installMethods":769,"rationale":770,"selectedPaths":771,"source":357,"sourceLanguage":18,"type":264},"skills/pm-release-notes","Generate customer-facing release notes from git logs, changelogs, or manual input. Narrative style focused on customer benefit, not feature names. Supports multiple output formats: blog post, email snippet, in-app notification, changelog entry. Use when someone says \"release notes\", \"changelog\", \"what shipped\", \"customer update\", \"release communication\", \"what's new\", \"product update email\", \"in-app notification\", \"ship log\", or \"announce this release\".\n","pm-release-notes",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-release-notes/SKILL.md",[772],{"path":495,"priority":351},{"basePath":774,"description":775,"displayName":776,"installMethods":777,"rationale":778,"selectedPaths":779,"source":357,"sourceLanguage":18,"type":264},"skills/pm-review","Pre-review quality gate that checks any PM artifact (PRD, strategy doc, one-pager, brief) against Head of Product standards. Scores problem clarity, metrics quality, scope discipline, and compliance awareness. Acts as \"the HoP reviewing your work before the real HoP sees it.\" Use when someone says \"review this\", \"check this PRD\", \"is this ready for review\", \"quality check\", \"does this meet the bar\", or \"pre-review my spec\".\n","pm-review",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-review/SKILL.md",[780],{"path":495,"priority":351},{"basePath":782,"description":783,"displayName":784,"installMethods":785,"rationale":786,"selectedPaths":787,"source":357,"sourceLanguage":18,"type":264},"skills/pm-risk-register","Product risk identification, scoring, matrix plotting, and mitigation planning. Use when someone says \"risk register\", \"risk assessment\", \"what could go wrong\", \"risk matrix\", \"risk mitigation\", \"identify risks\", \"risk planning\", \"risk review\".\n","pm-risk-register",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-risk-register/SKILL.md",[788],{"path":495,"priority":351},{"basePath":790,"description":791,"displayName":792,"installMethods":793,"rationale":794,"selectedPaths":795,"source":357,"sourceLanguage":18,"type":264},"skills/pm-sales-deck","Generate sales and pitch deck CONTENT — narrative structure, slide-by-slide content, talk tracks, and anticipated objections. NOT visual design. Covers B2B sales presentations, competitive pitches, and demo intros. Use when someone says \"sales deck\", \"pitch deck\", \"sales presentation\", \"customer pitch\", \"demo deck\", \"prospect presentation\", \"deal deck\", or \"competitive pitch\".\n","pm-sales-deck",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-sales-deck/SKILL.md",[796],{"path":495,"priority":351},{"basePath":798,"description":799,"displayName":800,"installMethods":801,"rationale":802,"selectedPaths":803,"source":357,"sourceLanguage":18,"type":264},"skills/pm-sprint-retro","Sprint retrospective facilitator with Start/Stop/Continue and 4Ls formats. Generates structured retro outputs with action items, owners, and deadlines. Use when someone says \"retro\", \"retrospective\", \"sprint review\", \"what went well\", \"start stop continue\", \"4Ls\", \"team reflection\", \"iteration review\".\n","pm-sprint-retro",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-sprint-retro/SKILL.md",[804],{"path":495,"priority":351},{"basePath":806,"description":807,"displayName":808,"installMethods":809,"rationale":810,"selectedPaths":811,"source":357,"sourceLanguage":18,"type":264},"skills/pm-stakeholder-simulator","Simulate how different stakeholders would react to a proposed product change. Surface objections, concerns, and political dynamics before the real meeting. Use when someone says \"how will X react?\", \"stakeholder analysis\", \"what objections will I face?\", \"prepare me for the meeting\", or \"simulate the room\".\n","pm-stakeholder-simulator",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-stakeholder-simulator/SKILL.md",[812],{"path":495,"priority":351},{"basePath":814,"description":815,"displayName":816,"installMethods":817,"rationale":818,"selectedPaths":819,"source":357,"sourceLanguage":18,"type":264},"skills/pm-strategic-review","End-of-quarter strategic review in narrative style with a bets scorecard. Use when someone says \"quarter review\", \"strategic review\", \"what happened last quarter\", \"quarterly retro\", \"bets scorecard\", \"review our bets\", \"end of quarter report\".\n","pm-strategic-review",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-strategic-review/SKILL.md",[820],{"path":495,"priority":351},{"basePath":822,"description":823,"displayName":824,"installMethods":825,"rationale":826,"selectedPaths":827,"source":357,"sourceLanguage":18,"type":264},"skills/pm-swot","SWOT analysis with structured strategic implications and SO/ST/WO/WT options. Use when someone says \"SWOT analysis\", \"strategic analysis\", \"competitive position\", \"strengths and weaknesses\", \"market analysis\", \"where do we stand\".\n","pm-swot",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-swot/SKILL.md",[828],{"path":495,"priority":351},{"basePath":830,"description":831,"displayName":832,"installMethods":833,"rationale":834,"selectedPaths":835,"source":357,"sourceLanguage":18,"type":264},"skills/pm-value-prop-canvas","Strategyzer Value Proposition Canvas: customer profile, value map, and fit analysis. Use when someone says \"value proposition\", \"value prop canvas\", \"customer jobs\", \"jobs to be done\", \"pain points\", \"why do customers buy us\", \"product-market fit\".\n","pm-value-prop-canvas",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-value-prop-canvas/SKILL.md",[836],{"path":495,"priority":351},{"basePath":838,"description":839,"displayName":840,"installMethods":841,"rationale":842,"selectedPaths":843,"source":357,"sourceLanguage":18,"type":264},"skills/pm-win-loss","Structure and analyze win/loss data. Two modes: generate interview guides for win/loss calls, or analyze existing data to identify patterns and recommendations. Covers competitive analysis, decision factors, and segment-level insights. Use when someone says \"win loss\", \"win/loss analysis\", \"why did we lose\", \"deal analysis\", \"competitive win rate\", \"lost deal review\", \"churn analysis\", \"win loss interview\", or \"why did we win\".\n","pm-win-loss",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-win-loss/SKILL.md",[844],{"path":495,"priority":351},{"basePath":846,"description":847,"displayName":848,"installMethods":849,"rationale":850,"selectedPaths":851,"source":357,"sourceLanguage":18,"type":264},"skills/pm-workflow-competitive-intel","Multi-skill workflow that produces a complete competitive intelligence package. Chain: (1) SWOT analysis, (2) Market sizing via web research, (3) Competitive profiles, (4) Positioning analysis, (5) One-pager summary. Uses web search to gather real competitive data. Outputs a comprehensive competitive brief. Use when someone says \"competitive analysis\", \"competitive intel\", \"competitor research\", \"market analysis\", \"how do we compare\", \"competitive landscape\", \"market positioning\".\n","pm-workflow-competitive-intel",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-workflow-competitive-intel/SKILL.md",[852],{"path":495,"priority":351},{"basePath":854,"description":855,"displayName":856,"installMethods":857,"rationale":858,"selectedPaths":859,"source":357,"sourceLanguage":18,"type":264},"skills/pm-workflow-migration","Multi-skill workflow that produces a complete migration execution package. Chain: (1) Migration PRD, (2) Migration Planner, (3) Risk Register, (4) Stakeholder Simulation, (5) Comms + PE Report. Each stage produces an artifact that feeds the next. Designed for platform migrations, product consolidations, and post-acquisition integrations. Use when someone says \"migration workflow\", \"migration plan end to end\", \"consolidation workflow\", \"post-acquisition migration\", \"platform migration plan\", \"full migration package\", \"migration execution plan\", \"M&A integration workflow\".\n","pm-workflow-migration",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-workflow-migration/SKILL.md",[860],{"path":495,"priority":351},{"basePath":862,"description":863,"displayName":864,"installMethods":865,"rationale":866,"selectedPaths":867,"source":357,"sourceLanguage":18,"type":264},"skills/pm-workflow-problem-to-prd","Multi-skill workflow chain that takes a raw problem statement and produces a complete PRD. Chain: (1) JTBD extraction, (2) Persona generation, (3) Opportunity tree mapping, (4) Feature spec / PRD generation, (5) Quality review. Each stage produces an artifact that feeds the next. Shows progress between stages. Use when someone says \"problem to PRD\", \"build a PRD from scratch\", \"full spec workflow\", \"take this problem and write a PRD\", \"end-to-end spec\", \"problem to solution\".\n","pm-workflow-problem-to-prd",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-workflow-problem-to-prd/SKILL.md",[868],{"path":495,"priority":351},{"basePath":870,"description":871,"displayName":872,"installMethods":873,"rationale":874,"selectedPaths":875,"source":357,"sourceLanguage":18,"type":264},"skills/pm-workflow-quarterly-cycle","Multi-skill workflow that runs the full quarterly planning cycle. The \"big one.\" Chain: (1) Strategic review of past quarter, (2) North star validation, (3) OKR definition, (4) Quarterly planning with capacity and bets, (5) Roadmap generation. Each stage builds on the previous. Complete quarterly planning ceremony. Use when someone says \"quarterly planning\", \"Q[N] planning\", \"quarterly cycle\", \"next quarter\", \"planning ceremony\", \"OKRs\", \"roadmap planning\", \"quarterly review\".\n","pm-workflow-quarterly-cycle",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-workflow-quarterly-cycle/SKILL.md",[876],{"path":495,"priority":351},{"basePath":878,"description":879,"displayName":880,"installMethods":881,"rationale":882,"selectedPaths":883,"source":357,"sourceLanguage":18,"type":264},"skills/pm-workflow-sales-enablement","Multi-skill workflow that produces a complete sales enablement package. Chain: (1) Messaging framework, (2) Competitive battlecards, (3) Objection playbook, (4) GTM launch playbook. Each stage produces an artifact that feeds the next. Outputs are written for revenue teams, not product teams. Use when someone says \"sales enablement\", \"enable the sales team\", \"sales toolkit\", \"go-to-market package\", \"competitive sales materials\", \"arm the sales team\", \"sales readiness\", \"launch enablement pack\".\n","pm-workflow-sales-enablement",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-workflow-sales-enablement/SKILL.md",[884],{"path":495,"priority":351},{"sources":886},[887],"manual",{"closedIssues90d":8,"description":889,"forks":8,"homepage":890,"license":255,"openIssues90d":8,"pushedAt":252,"readmeSize":249,"stars":253,"topics":891},"Hopefully  the only Toolkit you need to become a successful PM ","https://makeitnice.de",[892,893,894],"productmanagement","productmanagemenysystem","saas",{"classifiedAt":896,"discoverAt":897,"extractAt":898,"githubAt":898,"updatedAt":896},1778692726243,1778692722125,1778692724347,[223,224,221,220,222],{"evaluatedAt":258,"extractAt":309,"updatedAt":258},[],[903,931,955,981,1010,1032],{"_creationTime":904,"_id":905,"community":906,"display":907,"identity":913,"providers":917,"relations":924,"tags":927,"workflow":928},1778695548458.341,"k17bhvgckw8em3vfdvx2e18w9986mrzq",{"reviewCount":8},{"description":908,"installMethods":909,"name":911,"sourceUrl":912},"Conduct a blameless post-mortem analysis after an incident. Build timeline reconstruction, identify contributing factors, and generate actionable improvements. Focus on systemic issues rather than individual blame. Use after any production incident or service degradation, following a near-miss, when investigating recurring issues, or to share systemic learnings across teams.\n",{"claudeCode":910},"pjt222/agent-almanac","conduct-post-mortem","https://github.com/pjt222/agent-almanac",{"basePath":914,"githubOwner":915,"githubRepo":916,"locale":18,"slug":911,"type":264},"skills/conduct-post-mortem","pjt222","agent-almanac",{"evaluate":918,"extract":923},{"promptVersionExtension":213,"promptVersionScoring":214,"score":217,"tags":919,"targetMarket":225,"tier":226},[220,920,921,221,922],"incident-review","blameless","observability",{"commitSha":299},{"parentExtensionId":925,"repoId":926},"k170h0janaa9kwn7cfgfz2ykss86mmh9","kd7aryv63z61j39n2td1aeqkvh86mh12",[921,221,920,922,220],{"evaluatedAt":929,"extractAt":930,"updatedAt":929},1778696760664,1778695548458,{"_creationTime":932,"_id":933,"community":934,"display":935,"identity":939,"providers":941,"relations":951,"tags":952,"workflow":953},1778695548458.4048,"k17e5nn93syzxrybh3he9fz5eh86nbme",{"reviewCount":8},{"description":936,"installMethods":937,"name":938,"sourceUrl":912},"Guide a person in becoming a better teacher and explainer. AI coaches content structuring, audience calibration, explanation clarity, Socratic questioning technique, feedback interpretation, and reflective practice for technical presentations, documentation, and mentoring. Use when a person needs to present technical content and wants preparation coaching, wants to write better documentation or tutorials, struggles to explain concepts across expertise levels, is mentoring a colleague, or is preparing for a talk or knowledge-sharing session.\n",{"claudeCode":910},"teach-guidance",{"basePath":940,"githubOwner":915,"githubRepo":916,"locale":18,"slug":938,"type":264},"skills/teach-guidance",{"evaluate":942,"extract":950},{"promptVersionExtension":213,"promptVersionScoring":214,"score":943,"tags":944,"targetMarket":225,"tier":226},100,[945,946,947,224,948,949],"teaching","coaching","presentation","explanation","guidance",{"commitSha":299},{"parentExtensionId":925,"repoId":926},[946,224,948,949,947,945],{"evaluatedAt":954,"extractAt":930,"updatedAt":954},1778701952682,{"_creationTime":956,"_id":957,"community":958,"display":959,"identity":963,"providers":965,"relations":977,"tags":978,"workflow":979},1778695548458.385,"k17avw7n0q0zss1q5kna5zvjzx86mdvr",{"reviewCount":8},{"description":960,"installMethods":961,"name":962,"sourceUrl":912},"Prepare an organisation for regulatory inspection by assessing readiness against agency-specific focus areas (FDA, EMA, MHRA). Covers warning letter and 483 theme analysis, mock inspection protocols, document bundle preparation, inspection logistics, and response template creation. Use when a regulatory inspection has been announced or is anticipated, when a periodic self-assessment is due, when new systems have been implemented since the last inspection, or after a significant audit finding that may attract regulatory attention.\n",{"claudeCode":910},"prepare-inspection-readiness",{"basePath":964,"githubOwner":915,"githubRepo":916,"locale":18,"slug":962,"type":264},"skills/prepare-inspection-readiness",{"evaluate":966,"extract":976},{"promptVersionExtension":213,"promptVersionScoring":214,"score":943,"tags":967,"targetMarket":225,"tier":226},[968,969,970,971,972,973,974,224,975],"compliance","gxp","inspection","fda","ema","mhra","readiness","process-automation",{"commitSha":299},{"parentExtensionId":925,"repoId":926},[968,224,972,971,969,970,973,975,974],{"evaluatedAt":980,"extractAt":930,"updatedAt":980},1778700122939,{"_creationTime":982,"_id":983,"community":984,"display":985,"identity":991,"providers":995,"relations":1003,"tags":1006,"workflow":1007},1778699234184.6135,"k175frmf44tn80mcd6gvw1c1th86ngq9",{"reviewCount":8},{"description":986,"installMethods":987,"name":989,"sourceUrl":990},"Invoke parallel document-specialist agents for external web searches and documentation lookup",{"claudeCode":988},"Yeachan-Heo/oh-my-claudecode","external-context","https://github.com/Yeachan-Heo/oh-my-claudecode",{"basePath":992,"githubOwner":993,"githubRepo":994,"locale":18,"slug":989,"type":264},"skills/external-context","Yeachan-Heo","oh-my-claudecode",{"evaluate":996,"extract":1002},{"promptVersionExtension":213,"promptVersionScoring":214,"score":943,"tags":997,"targetMarket":225,"tier":226},[998,224,999,1000,1001],"search","research","information-retrieval","multi-agent",{"commitSha":299},{"parentExtensionId":1004,"repoId":1005},"k17brg5egdw1jbncj1j4wfv3fh86n639","kd74zv63fryf9prygtq7gf4es986n22y",[224,1000,1001,999,998],{"evaluatedAt":1008,"extractAt":1009,"updatedAt":1008},1778699449790,1778699234184,{"_creationTime":1011,"_id":1012,"community":1013,"display":1014,"identity":1018,"providers":1020,"relations":1028,"tags":1029,"workflow":1030},1778699234184.6133,"k170q6m14w6ah5ygc0jr5sa54986mpx7",{"reviewCount":8},{"description":1015,"installMethods":1016,"name":1017,"sourceUrl":990},"Deep codebase initialization with hierarchical AGENTS.md documentation",{"claudeCode":988},"deepinit",{"basePath":1019,"githubOwner":993,"githubRepo":994,"locale":18,"slug":1017,"type":264},"skills/deepinit",{"evaluate":1021,"extract":1027},{"promptVersionExtension":213,"promptVersionScoring":214,"score":943,"tags":1022,"targetMarket":225,"tier":226},[224,1023,1024,1025,1026],"codebase","agent","typescript","javascript",{"commitSha":299},{"parentExtensionId":1004,"repoId":1005},[1024,1023,224,1026,1025],{"evaluatedAt":1031,"extractAt":1009,"updatedAt":1031},1778699437749,{"_creationTime":1033,"_id":1034,"community":1035,"display":1036,"identity":1042,"providers":1047,"relations":1055,"tags":1058,"workflow":1059},1778699328001.0105,"k17e2h7ptrey632b63a9phc4sn86m79w",{"reviewCount":8},{"description":1037,"installMethods":1038,"name":1040,"sourceUrl":1041},"Nutzen Sie dies, wenn der Benutzer eine Repository-README übersetzen, ein Repository mehrsprachig machen, Dokumentationen lokalisieren, einen Sprachumschalter hinzufügen, die README internationalisieren oder lokalisierte README-Varianten in einem GitHub-ähnlichen Repository aktualisieren möchte.",{"claudeCode":1039},"xixu-me/skills","readme-i18n","https://github.com/xixu-me/skills",{"basePath":1043,"githubOwner":1044,"githubRepo":1045,"locale":1046,"slug":1040,"type":264},"skills/readme-i18n","xixu-me","skills","de",{"evaluate":1048,"extract":1054},{"promptVersionExtension":213,"promptVersionScoring":214,"score":943,"tags":1049,"targetMarket":225,"tier":226},[1050,224,1051,1052,1053],"localization","internationalization","markdown","github",{"commitSha":299},{"repoId":1056,"translatedFrom":1057},"kd77r2vb42jmgam0qbr9f2c6kn86mebv","k173sze6h2kdjhyfbveynf98t586n5wt",[224,1053,1051,1050,1052],{"evaluatedAt":1060,"extractAt":1061,"updatedAt":1062},1778699174967,1778699106670,1778699328001]