[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76RZ46TGCJCK3E403Y2G5W4":3,"skill-same:01M76RZ46TGCJCK3E403Y2G5W4":77},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M76RZ46TGCJCK3E403Y2G5W4","product-manager-toolkit",null,"Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritization, user research synthesis, requirement documentation, and product strategy development.","msm47\u002FGitskil","msm47","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F288053465?v=4","01M754J0R2V3Q31DD8BV9CCDEN","01M754J0S8Q6Y7P0S3AYCY0YQ5",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fproduct-team\u002Fskills\u002Fproduct-manager-toolkit\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: \"product-manager-toolkit\"\ndescription: Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritization, user research synthesis, requirement documentation, and product strategy development.\n---\n\n# Product Manager Toolkit\n\nEssential tools and frameworks for modern product management, from discovery to delivery.\n\n---\n\n## Table of Contents\n\n- [Quick Start](#quick-start)\n- [Core Workflows](#core-workflows)\n  - [Feature Prioritization](#feature-prioritization-process)\n  - [Customer Discovery](#customer-discovery-process)\n  - [PRD Development](#prd-development-process)\n- [Tools Reference](#tools-reference)\n  - [RICE Prioritizer](#rice-prioritizer)\n  - [Customer Interview Analyzer](#customer-interview-analyzer)\n- [Input\u002FOutput Examples](#inputoutput-examples)\n- [Integration Points](#integration-points)\n- [Common Pitfalls](#common-pitfalls-to-avoid)\n\n---\n\n## Quick Start\n\n### For Feature Prioritization\n```bash\n# Create sample data file\npython scripts\u002Frice_prioritizer.py sample\n\n# Run prioritization with team capacity\npython scripts\u002Frice_prioritizer.py sample_features.csv --capacity 15\n```\n\n### For Interview Analysis\n```bash\npython scripts\u002Fcustomer_interview_analyzer.py interview_transcript.txt\n```\n\n### For PRD Creation\n1. Choose template from `references\u002Fprd_templates.md`\n2. Fill sections based on discovery work\n3. Review with engineering for feasibility\n4. Version control in project management tool\n\n---\n\n## Core Workflows\n\n### Feature Prioritization Process\n\n```\nGather → Score → Analyze → Plan → Validate → Execute\n```\n\n#### Step 1: Gather Feature Requests\n- Customer feedback (support tickets, interviews)\n- Sales requests (CRM pipeline blockers)\n- Technical debt (engineering input)\n- Strategic initiatives (leadership goals)\n\n#### Step 2: Score with RICE\n```bash\n# Input: CSV with features\npython scripts\u002Frice_prioritizer.py features.csv --capacity 20\n```\n\nSee `references\u002Fframeworks.md` for RICE formula and scoring guidelines.\n\n#### Step 3: Analyze Portfolio\nReview the tool output for:\n- Quick wins vs big bets distribution\n- Effort concentration (avoid all XL projects)\n- Strategic alignment gaps\n\n#### Step 4: Generate Roadmap\n- Quarterly capacity allocation\n- Dependency identification\n- Stakeholder communication plan\n\n#### Step 5: Validate Results\n**Before finalizing the roadmap:**\n- [ ] Compare top priorities against strategic goals\n- [ ] Run sensitivity analysis (what if estimates are wrong by 2x?)\n- [ ] Review with key stakeholders for blind spots\n- [ ] Check for missing dependencies between features\n- [ ] Validate effort estimates with engineering\n\n#### Step 6: Execute and Iterate\n- Share roadmap with team\n- Track actual vs estimated effort\n- Revisit priorities quarterly\n- Update RICE inputs based on learnings\n\n---\n\n### Customer Discovery Process\n\n```\nPlan → Recruit → Interview → Analyze → Synthesize → Validate\n```\n\n#### Step 1: Plan Research\n- Define research questions\n- Identify target segments\n- Create interview script (see `references\u002Fframeworks.md`)\n\n#### Step 2: Recruit Participants\n- 5-8 interviews per segment\n- Mix of power users and churned users\n- Incentivize appropriately\n\n#### Step 3: Conduct Interviews\n- Use semi-structured format\n- Focus on problems, not solutions\n- Record with permission\n- Take minimal notes during interview\n\n#### Step 4: Analyze Insights\n```bash\npython scripts\u002Fcustomer_interview_analyzer.py transcript.txt\n```\n\nExtracts:\n- Pain points with severity\n- Feature requests with priority\n- Jobs to be done patterns\n- Sentiment and key themes\n- Notable quotes\n\n#### Step 5: Synthesize Findings\n- Group similar pain points across interviews\n- Identify patterns (3+ mentions = pattern)\n- Map to opportunity areas using Opportunity Solution Tree\n- Prioritize opportunities by frequency and severity\n\n#### Step 6: Validate Solutions\n**Before building:**\n- [ ] Create solution hypotheses (see `references\u002Fframeworks.md`)\n- [ ] Test with low-fidelity prototypes\n- [ ] Measure actual behavior vs stated preference\n- [ ] Iterate based on feedback\n- [ ] Document learnings for future research\n\n---\n\n### PRD Development Process\n\n```\nScope → Draft → Review → Refine → Approve → Track\n```\n\n#### Step 1: Choose Template\nSelect from `references\u002Fprd_templates.md`:\n\n| Template | Use Case | Timeline |\n|----------|----------|----------|\n| Standard PRD | Complex features, cross-team | 6-8 weeks |\n| One-Page PRD | Simple features, single team | 2-4 weeks |\n| Feature Brief | Exploration phase | 1 week |\n| Agile Epic | Sprint-based delivery | Ongoing |\n\n#### Step 2: Draft Content\n- Lead with problem statement\n- Define success metrics upfront\n- Explicitly state out-of-scope items\n- Include wireframes or mockups\n\n#### Step 3: Review Cycle\n- Engineering: feasibility and effort\n- Design: user experience gaps\n- Sales: market validation\n- Support: operational impact\n\n#### Step 4: Refine Based on Feedback\n- Address technical constraints\n- Adjust scope to fit timeline\n- Document trade-off decisions\n\n#### Step 5: Approval and Kickoff\n- Stakeholder sign-off\n- Sprint planning integration\n- Communication to broader team\n\n#### Step 6: Track Execution\n**After launch:**\n- [ ] Compare actual metrics vs targets\n- [ ] Conduct user feedback sessions\n- [ ] Document what worked and what didn't\n- [ ] Update estimation accuracy data\n- [ ] Share learnings with team\n\n---\n\n## Tools Reference\n\n### RICE Prioritizer\n\nAdvanced RICE framework implementation with portfolio analysis.\n\n**Features:**\n- RICE score calculation with configurable weights\n- Portfolio balance analysis (quick wins vs big bets)\n- Quarterly roadmap generation based on capacity\n- Multiple output formats (text, JSON, CSV)\n\n**CSV Input Format:**\n```csv\nname,reach,impact,confidence,effort,description\nUser Dashboard Redesign,5000,high,high,l,Complete redesign\nMobile Push Notifications,10000,massive,medium,m,Add push support\nDark Mode,8000,medium,high,s,Dark theme option\n```\n\n**Commands:**\n```bash\n# Create sample data\npython scripts\u002Frice_prioritizer.py sample\n\n# Run with default capacity (10 person-months)\npython scripts\u002Frice_prioritizer.py features.csv\n\n# Custom capacity\npython scripts\u002Frice_prioritizer.py features.csv --capacity 20\n\n# JSON output for integration\npython scripts\u002Frice_prioritizer.py features.csv --output json\n\n# CSV output for spreadsheets\npython scripts\u002Frice_prioritizer.py features.csv --output csv\n```\n\n---\n\n### Customer Interview Analyzer\n\nNLP-based interview analysis for extracting actionable insights.\n\n**Capabilities:**\n- Pain point extraction with severity assessment\n- Feature request identification and classification\n- Jobs-to-be-done pattern recognition\n- Sentiment analysis per section\n- Theme and quote extraction\n- Competitor mention detection\n\n**Commands:**\n```bash\n# Analyze interview transcript\npython scripts\u002Fcustomer_interview_analyzer.py interview.txt\n\n# JSON output for aggregation\npython scripts\u002Fcustomer_interview_analyzer.py interview.txt json\n```\n\n---\n\n## Input\u002FOutput Examples\n→ See references\u002Finput-output-examples.md for details\n\n## Integration Points\n\nCompatible tools and platforms:\n\n| Category | Platforms |\n|----------|-----------|\n| **Analytics** | Amplitude, Mixpanel, Google Analytics |\n| **Roadmapping** | ProductBoard, Aha!, Roadmunk, Productplan |\n| **Design** | Figma, Sketch, Miro |\n| **Development** | Jira, Linear, GitHub, Asana |\n| **Research** | Dovetail, UserVoice, Pendo, Maze |\n| **Communication** | Slack, Notion, Confluence |\n\n**JSON export enables integration with most tools:**\n```bash\n# Export for Jira import\npython scripts\u002Frice_prioritizer.py features.csv --output json > priorities.json\n\n# Export for dashboard\npython scripts\u002Fcustomer_interview_analyzer.py interview.txt json > insights.json\n```\n\n---\n\n## Common Pitfalls to Avoid\n\n| Pitfall | Description | Prevention |\n|---------|-------------|------------|\n| **Solution-First** | Jumping to features before understanding problems | Start every PRD with problem statement |\n| **Analysis Paralysis** | Over-researching without shipping | Set time-boxes for research phases |\n| **Feature Factory** | Shipping features without measuring impact | Define success metrics before building |\n| **Ignoring Tech Debt** | Not allocating time for platform health | Reserve 20% capacity for maintenance |\n| **Stakeholder Surprise** | Not communicating early and often | Weekly async updates, monthly demos |\n| **Metric Theater** | Optimizing vanity metrics over real value | Tie metrics to user value delivered |\n\n---\n\n## Best Practices\n\n**Writing Great PRDs:**\n- Start with the problem, not the solution\n- Include clear success metrics upfront\n- Explicitly state what's out of scope\n- Use visuals (wireframes, flows, diagrams)\n- Keep technical details in appendix\n- Version control all changes\n\n**Effective Prioritization:**\n- Mix quick wins with strategic bets\n- Consider opportunity cost of delays\n- Account for dependencies between features\n- Buffer 20% for unexpected work\n- Revisit priorities quarterly\n- Communicate decisions with context\n\n**Customer Discovery:**\n- Ask \"why\" five times to find root cause\n- Focus on past behavior, not future intentions\n- Avoid leading questions (\"Wouldn't you love...\")\n- Interview in the user's natural environment\n- Watch for emotional reactions (pain = opportunity)\n- Validate qualitative with quantitative data\n\n---\n\n## Quick Reference\n\n```bash\n# Prioritization\npython scripts\u002Frice_prioritizer.py features.csv --capacity 15\n\n# Interview Analysis\npython scripts\u002Fcustomer_interview_analyzer.py interview.txt\n\n# Generate sample data\npython scripts\u002Frice_prioritizer.py sample\n\n# JSON outputs\npython scripts\u002Frice_prioritizer.py features.csv --output json\npython scripts\u002Fcustomer_interview_analyzer.py interview.txt json\n```\n\n---\n\n## Reference Documents\n\n- `references\u002Fprd_templates.md` - PRD templates for different contexts\n- `references\u002Fframeworks.md` - Detailed framework documentation (RICE, MoSCoW, Kano, JTBD, etc.)\n","# Product Manager Toolkit\n\nEssential tools and frameworks for modern product management, from discovery to delivery.\n\n---\n\n## Table of Contents\n\n- [Quick Start](#quick-start)\n- [Core Workflows](#core-workflows)\n  - [Feature Prioritization](#feature-prioritization-process)\n  - [Customer Discovery](#customer-discovery-process)\n  - [PRD Development](#prd-development-process)\n- [Tools Reference](#tools-reference)\n  - [RICE Prioritizer](#rice-prioritizer)\n  - [Customer Interview Analyzer](#customer-interview-analyzer)\n- [Input\u002FOutput Examples](#inputoutput-examples)\n- [Integration Points](#integration-points)\n- [Common Pitfalls](#common-pitfalls-to-avoid)\n\n---\n\n## Quick Start\n\n### For Feature Prioritization\n```bash\n# Create sample data file\npython scripts\u002Frice_prioritizer.py sample\n\n# Run prioritization with team capacity\npython scripts\u002Frice_prioritizer.py sample_features.csv --capacity 15\n```\n\n### For Interview Analysis\n```bash\npython scripts\u002Fcustomer_interview_analyzer.py interview_transcript.txt\n```\n\n### For PRD Creation\n1. Choose template from `references\u002Fprd_templates.md`\n2. Fill sections based on discovery work\n3. Review with engineering for feasibility\n4. Version control in project management tool\n\n---\n\n## Core Workflows\n\n### Feature Prioritization Process\n\n```\nGather → Score → Analyze → Plan → Validate → Execute\n```\n\n#### Step 1: Gather Feature Requests\n- Customer feedback (support tickets, interviews)\n- Sales requests (CRM pipeline blockers)\n- Technical debt (engineering input)\n- Strategic initiatives (leadership goals)\n\n#### Step 2: Score with RICE\n```bash\n# Input: CSV with features\npython scripts\u002Frice_prioritizer.py features.csv --capacity 20\n```\n\nSee `references\u002Fframeworks.md` for RICE formula and scoring guidelines.\n\n#### Step 3: Analyze Portfolio\nReview the tool output for:\n- Quick wins vs big bets distribution\n- Effort concentration (avoid all XL projects)\n- Strategic alignment gaps\n\n#### Step 4: Generate Roadmap\n- Quarterly capacity allocation\n- Dependency identification\n- Stakeholder communication plan\n\n#### Step 5: Validate Results\n**Before finalizing the roadmap:**\n- [ ] Compare top priorities against strategic goals\n- [ ] Run sensitivity analysis (what if estimates are wrong by 2x?)\n- [ ] Review with key stakeholders for blind spots\n- [ ] Check for missing dependencies between features\n- [ ] Validate effort estimates with engineering\n\n#### Step 6: Execute and Iterate\n- Share roadmap with team\n- Track actual vs estimated effort\n- Revisit priorities quarterly\n- Update RICE inputs based on learnings\n\n---\n\n### Customer Discovery Process\n\n```\nPlan → Recruit → Interview → Analyze → Synthesize → Validate\n```\n\n#### Step 1: Plan Research\n- Define research questions\n- Identify target segments\n- Create interview script (see `references\u002Fframeworks.md`)\n\n#### Step 2: Recruit Participants\n- 5-8 interviews per segment\n- Mix of power users and churned users\n- Incentivize appropriately\n\n#### Step 3: Conduct Interviews\n- Use semi-structured format\n- Focus on problems, not solutions\n- Record with permission\n- Take minimal notes during interview\n\n#### Step 4: Analyze Insights\n```bash\npython scripts\u002Fcustomer_interview_analyzer.py transcript.txt\n```\n\nExtracts:\n- Pain points with severity\n- Feature requests with priority\n- Jobs to be done patterns\n- Sentiment and key themes\n- Notable quotes\n\n#### Step 5: Synthesize Findings\n- Group similar pain points across interviews\n- Identify patterns (3+ mentions = pattern)\n- Map to opportunity areas using Opportunity Solution Tree\n- Prioritize opportunities by frequency and severity\n\n#### Step 6: Validate Solutions\n**Before building:**\n- [ ] Create solution hypotheses (see `references\u002Fframeworks.md`)\n- [ ] Test with low-fidelity prototypes\n- [ ] Measure actual behavior vs stated preference\n- [ ] Iterate based on feedback\n- [ ] Document learnings for future research\n\n---\n\n### PRD Development Process\n\n```\nScope → Draft → Review → Refine → Approve → Track\n```\n\n#### Step 1: Choose Template\nSelect from `references\u002Fprd_templates.md`:\n\n| Template | Use Case | Timeline |\n|----------|----------|----------|\n| Standard PRD | Complex features, cross-team | 6-8 weeks |\n| One-Page PRD | Simple features, single team | 2-4 weeks |\n| Feature Brief | Exploration phase | 1 week |\n| Agile Epic | Sprint-based delivery | Ongoing |\n\n#### Step 2: Draft Content\n- Lead with problem statement\n- Define success metrics upfront\n- Explicitly state out-of-scope items\n- Include wireframes or mockups\n\n#### Step 3: Review Cycle\n- Engineering: feasibility and effort\n- Design: user experience gaps\n- Sales: market validation\n- Support: operational impact\n\n#### Step 4: Refine Based on Feedback\n- Address technical constraints\n- Adjust scope to fit timeline\n- Document trade-off decisions\n\n#### Step 5: Approval and Kickoff\n- Stakeholder sign-off\n- Sprint planning integration\n- Communication to broader team\n\n#### Step 6: Track Execution\n**After launch:**\n- [ ] Compare actual metrics vs targets\n- [ ] Conduct user feedback sessions\n- [ ] Document what worked and what didn't\n- [ ] Update estimation accuracy data\n- [ ] Share learnings with team\n\n---\n\n## Tools Reference\n\n### RICE Prioritizer\n\nAdvanced RICE framework implementation with portfolio analysis.\n\n**Features:**\n- RICE score calculation with configurable weights\n- Portfolio balance analysis (quick wins vs big bets)\n- Quarterly roadmap generation based on capacity\n- Multiple output formats (text, JSON, CSV)\n\n**CSV Input Format:**\n```csv\nname,reach,impact,confidence,effort,description\nUser Dashboard Redesign,5000,high,high,l,Complete redesign\nMobile Push Notifications,10000,massive,medium,m,Add push support\nDark Mode,8000,medium,high,s,Dark theme option\n```\n\n**Commands:**\n```bash\n# Create sample data\npython scripts\u002Frice_prioritizer.py sample\n\n# Run with default capacity (10 person-months)\npython scripts\u002Frice_prioritizer.py features.csv\n\n# Custom capacity\npython scripts\u002Frice_prioritizer.py features.csv --capacity 20\n\n# JSON output for integration\npython scripts\u002Frice_prioritizer.py features.csv --output json\n\n# CSV output for spreadsheets\npython scripts\u002Frice_prioritizer.py features.csv --output csv\n```\n\n---\n\n### Customer Interview Analyzer\n\nNLP-based interview analysis for extracting actionable insights.\n\n**Capabilities:**\n- Pain point extraction with severity assessment\n- Feature request identification and classification\n- Jobs-to-be-done pattern recognition\n- Sentiment analysis per section\n- Theme and quote extraction\n- Competitor mention detection\n\n**Commands:**\n```bash\n# Analyze interview transcript\npython scripts\u002Fcustomer_interview_analyzer.py interview.txt\n\n# JSON output for aggregation\npython scripts\u002Fcustomer_interview_analyzer.py interview.txt json\n```\n\n---\n\n## Input\u002FOutput Examples\n→ See references\u002Finput-output-examples.md for details\n\n## Integration Points\n\nCompatible tools and platforms:\n\n| Category | Platforms |\n|----------|-----------|\n| **Analytics** | Amplitude, Mixpanel, Google Analytics |\n| **Roadmapping** | ProductBoard, Aha!, Roadmunk, Productplan |\n| **Design** | Figma, Sketch, Miro |\n| **Development** | Jira, Linear, GitHub, Asana |\n| **Research** | Dovetail, UserVoice, Pendo, Maze |\n| **Communication** | Slack, Notion, Confluence |\n\n**JSON export enables integration with most tools:**\n```bash\n# Export for Jira import\npython scripts\u002Frice_prioritizer.py features.csv --output json > priorities.json\n\n# Export for dashboard\npython scripts\u002Fcustomer_interview_analyzer.py interview.txt json > insights.json\n```\n\n---\n\n## Common Pitfalls to Avoid\n\n| Pitfall | Description | Prevention |\n|---------|-------------|------------|\n| **Solution-First** | Jumping to features before understanding problems | Start every PRD with problem statement |\n| **Analysis Paralysis** | Over-researching without shipping | Set time-boxes for research phases |\n| **Feature Factory** | Shipping features without measuring impact | Define success metrics before building |\n| **Ignoring Tech Debt** | Not allocating time for platform health | Reserve 20% capacity for maintenance |\n| **Stakeholder Surprise** | Not communicating early and often | Weekly async updates, monthly demos |\n| **Metric Theater** | Optimizing vanity metrics over real value | Tie metrics to user value delivered |\n\n---\n\n## Best Practices\n\n**Writing Great PRDs:**\n- Start with the problem, not the solution\n- Include clear success metrics upfront\n- Explicitly state what's out of scope\n- Use visuals (wireframes, flows, diagrams)\n- Keep technical details in appendix\n- Version control all changes\n\n**Effective Prioritization:**\n- Mix quick wins with strategic bets\n- Consider opportunity cost of delays\n- Account for dependencies between features\n- Buffer 20% for unexpected work\n- Revisit priorities quarterly\n- Communicate decisions with context\n\n**Customer Discovery:**\n- Ask \"why\" five times to find root cause\n- Focus on past behavior, not future intentions\n- Avoid leading questions (\"Wouldn't you love...\")\n- Interview in the user's natural environment\n- Watch for emotional reactions (pain = opportunity)\n- Validate qualitative with quantitative data\n\n---\n\n## Quick Reference\n\n```bash\n# Prioritization\npython scripts\u002Frice_prioritizer.py features.csv --capacity 15\n\n# Interview Analysis\npython scripts\u002Fcustomer_interview_analyzer.py interview.txt\n\n# Generate sample data\npython scripts\u002Frice_prioritizer.py sample\n\n# JSON outputs\npython scripts\u002Frice_prioritizer.py features.csv --output json\npython scripts\u002Fcustomer_interview_analyzer.py interview.txt json\n```\n\n---\n\n## Reference Documents\n\n- `references\u002Fprd_templates.md` - PRD templates for different contexts\n- `references\u002Fframeworks.md` - Detailed framework documentation (RICE, MoSCoW, Kano, JTBD, etc.)\n",{"name":5,"description":7},"main","56d41613d1ca1e2b0614a19c3816ec97a6159ec2","product-team\u002Fskills\u002Fproduct-manager-toolkit","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil","https:\u002F\u002Fgithub.com\u002Fmsm47","2026-06-22 18:36:50",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add msm47\u002FGitskil --skill product-manager-toolkit",{"tool":35,"command":36},"bunx","bunx skills add msm47\u002FGitskil --skill product-manager-toolkit",{"tool":38,"command":39},"pnpm","pnpm dlx skills add msm47\u002FGitskil --skill product-manager-toolkit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fproduct-team\u002Fskills\u002Fproduct-manager-toolkit\u002FSKILL.md",true,[43,49,53,59,63,67,73],{"path":44,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":47,"sourceHtmlUrl":48},"assets\u002Fprd_template.md","ASSET","资产文件",3415,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fproduct-team\u002Fskills\u002Fproduct-manager-toolkit\u002Fassets\u002Fprd_template.md",{"path":50,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":51,"sourceHtmlUrl":52},"assets\u002Frice_input_template.csv",130,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fproduct-team\u002Fskills\u002Fproduct-manager-toolkit\u002Fassets\u002Frice_input_template.csv",{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fframeworks.md","REFERENCE","参考文档",16748,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fproduct-team\u002Fskills\u002Fproduct-manager-toolkit\u002Freferences\u002Fframeworks.md",{"path":60,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Finput-output-examples.md",3779,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fproduct-team\u002Fskills\u002Fproduct-manager-toolkit\u002Freferences\u002Finput-output-examples.md",{"path":64,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fprd_templates.md",7249,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fproduct-team\u002Fskills\u002Fproduct-manager-toolkit\u002Freferences\u002Fprd_templates.md",{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"scripts\u002Fcustomer_interview_analyzer.py","SCRIPT","脚本",17404,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fproduct-team\u002Fskills\u002Fproduct-manager-toolkit\u002Fscripts\u002Fcustomer_interview_analyzer.py",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"scripts\u002Frice_prioritizer.py",11872,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fproduct-team\u002Fskills\u002Fproduct-manager-toolkit\u002Fscripts\u002Frice_prioritizer.py",[78,85,92,99,106,113],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M76S8VB9Q65XVZXC99QVF20M","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Triggers whenever a user uploads a syllabus, course outline, or curriculum document and wants supplementary readings. Also triggers on: 'syllabus reading list', 'find papers for my course', 'create a reading list from this syllabus', 'recent research for my class', 'supplementary readings', 'find journal articles for these topics', 'what recent papers cover this material', 'any new research on these course topics', 'update my syllabus with recent papers'. Even casual mentions when a syllabus is attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M76S8K8X17M3CV7RENS6KA32","research","Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends\u002Fsentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Triggers — \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\", or any research request that doesn't obviously match a more-specific specialist skill. Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":18},"01M76S8AZCNS7Q5M4G1SBQ8HDV","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Triggers: 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]', or any variation requesting multi-source recency intelligence on a topic. Also use for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":18},"01M76S7YVS0NHD51AFTZM5965R","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Triggers: 'prior art search for [invention]', 'patent search on [topic]', 'freedom to operate analysis', 'FTO for [product]', 'patent landscape for [field]', 'is [invention] novel', 'patents on [topic]', 'competitive patent analysis', 'prior art for litigation', 'patent diligence on [company]'. Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":18},"01M76S7MQDZR49Y3DRXF394R2F","notebooklm","Browser automation skill for controlling Google's NotebookLM. Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio Overview, infographics, slide decks, study guides, briefing docs, mind maps, timelines, FAQs), and creating new notebooks. Triggers on any phrase involving NotebookLM — 'open NotebookLM', 'check my [name] notebook', 'pull info from NotebookLM', 'ask my notebook about X', 'add [source] to NotebookLM', 'create an infographic in NotebookLM', 'use NotebookLM Studio', 'generate a slide deck from my notebook', or any variation where the goal involves NotebookLM. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":18},"01M76S78K1ZJ092YYRKX0KBTYJ","litreview","Academic literature orientation skill that searches papers via Consensus, builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a professionally formatted Word document (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — not a finished review, but an orientation guide that lets a researcher dive in confidently. Triggers: 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'. Do NOT trigger for single one-off paper searches where the user just wants a quick list — that's a plain Consensus search.","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[]]