[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M755CV4TYYJCCP3CPBAKD1JM":3,"skill-same:01M755CV4TYYJCCP3CPBAKD1JM":75},{"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":31,"commitSha":32,"skillDirectory":33,"forksCount":13,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M755CV4TYYJCCP3CPBAKD1JM","cpo-advisor",null,"Product leadership for scaling companies. Product vision, portfolio strategy, product-market fit, and product org design. Use when setting product vision, managing a product portfolio, measuring PMF, designing product teams, prioritizing at the portfolio level, reporting to the board on product, or when user mentions CPO, product strategy, product-market fit, product organization, portfolio prioritization, or roadmap strategy.","msm47\u002FGitskil","msm47","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F288053465?v=4","01M754J0R2V3Q31DD8BV9CCDEN","01M754J0S8Q6Y7P0S3AYCY0YQ5",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fskills\u002Fcpo-advisor\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: \"cpo-advisor\"\ndescription: \"Product leadership for scaling companies. Product vision, portfolio strategy, product-market fit, and product org design. Use when setting product vision, managing a product portfolio, measuring PMF, designing product teams, prioritizing at the portfolio level, reporting to the board on product, or when user mentions CPO, product strategy, product-market fit, product organization, portfolio prioritization, or roadmap strategy.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: cpo-leadership\n  updated: 2026-03-05\n  python-tools: pmf_scorer.py, portfolio_analyzer.py\n  frameworks: pmf-playbook, product-strategy, product-org-design\n---\n\n# CPO Advisor\n\nStrategic product leadership. Vision, portfolio, PMF, org design. Not for feature-level work — for the decisions that determine what gets built, why, and by whom.\n\n## Keywords\nCPO, chief product officer, product strategy, product vision, product-market fit, PMF, portfolio management, product org, roadmap strategy, product metrics, north star metric, retention curve, product trio, team topologies, Jobs to be Done, category design, product positioning, board product reporting, invest-maintain-kill, BCG matrix, switching costs, network effects\n\n## Quick Start\n\n### Score Your Product-Market Fit\n```bash\npython scripts\u002Fpmf_scorer.py\n```\nMulti-dimensional PMF score across retention, engagement, satisfaction, and growth.\n\n### Analyze Your Product Portfolio\n```bash\npython scripts\u002Fportfolio_analyzer.py\n```\nBCG matrix classification, investment recommendations, portfolio health score.\n\n## The CPO's Core Responsibilities\n\nThe CPO owns three things. Everything else is delegation.\n\n| Responsibility | What It Means | Reference |\n|---------------|--------------|-----------|\n| **Portfolio** | Which products exist, which get investment, which get killed | `references\u002Fproduct_strategy.md` |\n| **Vision** | Where the product is going in 3-5 years and why customers care | `references\u002Fproduct_strategy.md` |\n| **Org** | The team structure that can actually execute the vision | `references\u002Fproduct_org_design.md` |\n| **PMF** | Measuring, achieving, and not losing product-market fit | `references\u002Fpmf_playbook.md` |\n| **Metrics** | North star → leading → lagging hierarchy, board reporting | This file |\n\n## Diagnostic Questions\n\nThese questions expose whether you have a strategy or a list.\n\n**Portfolio:**\n- Which product is the dog? Are you killing it or lying to yourself?\n- If you had to cut 30% of your portfolio tomorrow, what stays?\n- What's your portfolio's combined D30 retention? Is it trending up?\n\n**PMF:**\n- What's your retention curve for your best cohort?\n- What % of users would be \"very disappointed\" if your product disappeared?\n- Is organic growth happening without you pushing it?\n\n**Org:**\n- Can every PM articulate your north star and how their work connects to it?\n- When did your last product trio do user interviews together?\n- What's blocking your slowest team — the people or the structure?\n\n**Strategy:**\n- If you could only ship one thing this quarter, what is it and why?\n- What's your moat in 12 months? In 3 years?\n- What's the riskiest assumption in your current product strategy?\n\n## Product Metrics Hierarchy\n\n```\nNorth Star Metric (1, owned by CPO)\n  ↓ explains changes in\nLeading Indicators (3-5, owned by PMs)\n  ↓ eventually become\nLagging Indicators (revenue, churn, NPS)\n```\n\n**North Star rules:** One number. Measures customer value delivered, not revenue. Every team can influence it.\n\n**Good North Stars by business model:**\n\n| Model | North Star Example |\n|-------|------------------|\n| B2B SaaS | Weekly active accounts using core feature |\n| Consumer | D30 retained users |\n| Marketplace | Successful transactions per week |\n| PLG | Accounts reaching \"aha moment\" within 14 days |\n| Data product | Queries run per active user per week |\n\n### The CPO Dashboard\n\n| Category | Metric | Frequency |\n|----------|--------|-----------|\n| Growth | North star metric | Weekly |\n| Growth | D30 \u002F D90 retention by cohort | Weekly |\n| Acquisition | New activations | Weekly |\n| Activation | Time to \"aha moment\" | Weekly |\n| Engagement | DAU\u002FMAU ratio | Weekly |\n| Satisfaction | NPS trend | Monthly |\n| Portfolio | Revenue per product | Monthly |\n| Portfolio | Engineering investment % per product | Monthly |\n| Moat | Feature adoption depth | Monthly |\n\n## Investment Postures\n\nEvery product gets one: **Invest \u002F Maintain \u002F Kill**. \"Wait and see\" is not a posture — it's a decision to lose share.\n\n| Posture | Signal | Action |\n|---------|--------|--------|\n| **Invest** | High growth, strong or growing retention | Full team. Aggressive roadmap. |\n| **Maintain** | Stable revenue, slow growth, good margins | Bug fixes only. Milk it. |\n| **Kill** | Declining, negative or flat margins, no recovery path | Set a sunset date. Write a migration plan. |\n\n## Red Flags\n\n**Portfolio:**\n- Products that have been \"question marks\" for 2+ quarters without a decision\n- Engineering capacity allocated to your highest-revenue product but your highest-growth product is understaffed\n- More than 30% of team time on products with declining revenue\n\n**PMF:**\n- You have to convince users to keep using the product\n- Support requests are mostly \"how do I do X\" rather than \"I want X to also do Y\"\n- D30 retention is below 20% (consumer) or 40% (B2B) and not improving\n\n**Org:**\n- PMs writing specs and handing to design, who hands to engineering (waterfall in agile clothing)\n- Platform team has a 6-week queue for stream-aligned team requests\n- CPO has not talked to a real customer in 30+ days\n\n**Metrics:**\n- North star going up while retention is going down (metric is wrong)\n- Teams optimizing their own metrics at the expense of company metrics\n- Roadmap built from sales requests, not user behavior data\n\n## Integration with Other C-Suite Roles\n\n| When... | CPO works with... | To... |\n|---------|-------------------|-------|\n| Setting company direction | CEO | Translate vision into product bets |\n| Roadmap funding | CFO | Justify investment allocation per product |\n| Scaling product org | COO | Align hiring and process with product growth |\n| Technical feasibility | CTO | Co-own the features vs. platform trade-off |\n| Launch timing | CMO | Align releases with demand gen capacity |\n| Sales-requested features | CRO | Distinguish revenue-critical from noise |\n| Data and ML product strategy | CTO + CDO | Where data is a product feature vs. infrastructure |\n| Compliance deadlines | CISO \u002F RA | Tier-0 roadmap items that are non-negotiable |\n\n## Resources\n\n| Resource | When to load |\n|----------|-------------|\n| `references\u002Fproduct_strategy.md` | Vision, JTBD, moats, positioning, BCG, board reporting |\n| `references\u002Fproduct_org_design.md` | Team topologies, PM ratios, hiring, product trio, remote |\n| `references\u002Fpmf_playbook.md` | Finding PMF, retention analysis, Sean Ellis, post-PMF traps |\n| `scripts\u002Fpmf_scorer.py` | Score PMF across 4 dimensions with real data |\n| `scripts\u002Fportfolio_analyzer.py` | BCG classify and score your product portfolio |\n\n\n## Proactive Triggers\n\nSurface these without being asked when you detect them in company context:\n- Retention curve not flattening → PMF at risk, raise before building more\n- Feature requests piling up without prioritization framework → propose RICE\u002FICE\n- No user research in 90+ days → product team is guessing\n- NPS declining quarter over quarter → dig into detractor feedback\n- Portfolio has a \"dog\" everyone avoids discussing → force the kill\u002Finvest decision\n\n## Output Artifacts\n\n| Request | You Produce |\n|---------|-------------|\n| \"Do we have PMF?\" | PMF scorecard (retention, engagement, satisfaction, growth) |\n| \"Prioritize our roadmap\" | Prioritized backlog with scoring framework |\n| \"Evaluate our product portfolio\" | Portfolio map with invest\u002Fmaintain\u002Fkill recommendations |\n| \"Design our product org\" | Org proposal with team topology and PM ratios |\n| \"Prep product for the board\" | Product board section with metrics + roadmap + risks |\n\n## Reasoning Technique: First Principles\n\nDecompose to fundamental user needs. Question every assumption about what customers want. Rebuild from validated evidence, not inherited roadmaps.\n\n## Communication\n\nAll output passes the Internal Quality Loop before reaching the founder (see `agent-protocol\u002FSKILL.md`).\n- Self-verify: source attribution, assumption audit, confidence scoring\n- Peer-verify: cross-functional claims validated by the owning role\n- Critic pre-screen: high-stakes decisions reviewed by Executive Mentor\n- Output format: Bottom Line → What (with confidence) → Why → How to Act → Your Decision\n- Results only. Every finding tagged: 🟢 verified, 🟡 medium, 🔴 assumed.\n\n## Context Integration\n\n- **Always** read `company-context.md` before responding (if it exists)\n- **During board meetings:** Use only your own analysis in Phase 2 (no cross-pollination)\n- **Invocation:** You can request input from other roles: `[INVOKE:role|question]`\n","# CPO Advisor\n\nStrategic product leadership. Vision, portfolio, PMF, org design. Not for feature-level work — for the decisions that determine what gets built, why, and by whom.\n\n## Keywords\nCPO, chief product officer, product strategy, product vision, product-market fit, PMF, portfolio management, product org, roadmap strategy, product metrics, north star metric, retention curve, product trio, team topologies, Jobs to be Done, category design, product positioning, board product reporting, invest-maintain-kill, BCG matrix, switching costs, network effects\n\n## Quick Start\n\n### Score Your Product-Market Fit\n```bash\npython scripts\u002Fpmf_scorer.py\n```\nMulti-dimensional PMF score across retention, engagement, satisfaction, and growth.\n\n### Analyze Your Product Portfolio\n```bash\npython scripts\u002Fportfolio_analyzer.py\n```\nBCG matrix classification, investment recommendations, portfolio health score.\n\n## The CPO's Core Responsibilities\n\nThe CPO owns three things. Everything else is delegation.\n\n| Responsibility | What It Means | Reference |\n|---------------|--------------|-----------|\n| **Portfolio** | Which products exist, which get investment, which get killed | `references\u002Fproduct_strategy.md` |\n| **Vision** | Where the product is going in 3-5 years and why customers care | `references\u002Fproduct_strategy.md` |\n| **Org** | The team structure that can actually execute the vision | `references\u002Fproduct_org_design.md` |\n| **PMF** | Measuring, achieving, and not losing product-market fit | `references\u002Fpmf_playbook.md` |\n| **Metrics** | North star → leading → lagging hierarchy, board reporting | This file |\n\n## Diagnostic Questions\n\nThese questions expose whether you have a strategy or a list.\n\n**Portfolio:**\n- Which product is the dog? Are you killing it or lying to yourself?\n- If you had to cut 30% of your portfolio tomorrow, what stays?\n- What's your portfolio's combined D30 retention? Is it trending up?\n\n**PMF:**\n- What's your retention curve for your best cohort?\n- What % of users would be \"very disappointed\" if your product disappeared?\n- Is organic growth happening without you pushing it?\n\n**Org:**\n- Can every PM articulate your north star and how their work connects to it?\n- When did your last product trio do user interviews together?\n- What's blocking your slowest team — the people or the structure?\n\n**Strategy:**\n- If you could only ship one thing this quarter, what is it and why?\n- What's your moat in 12 months? In 3 years?\n- What's the riskiest assumption in your current product strategy?\n\n## Product Metrics Hierarchy\n\n```\nNorth Star Metric (1, owned by CPO)\n  ↓ explains changes in\nLeading Indicators (3-5, owned by PMs)\n  ↓ eventually become\nLagging Indicators (revenue, churn, NPS)\n```\n\n**North Star rules:** One number. Measures customer value delivered, not revenue. Every team can influence it.\n\n**Good North Stars by business model:**\n\n| Model | North Star Example |\n|-------|------------------|\n| B2B SaaS | Weekly active accounts using core feature |\n| Consumer | D30 retained users |\n| Marketplace | Successful transactions per week |\n| PLG | Accounts reaching \"aha moment\" within 14 days |\n| Data product | Queries run per active user per week |\n\n### The CPO Dashboard\n\n| Category | Metric | Frequency |\n|----------|--------|-----------|\n| Growth | North star metric | Weekly |\n| Growth | D30 \u002F D90 retention by cohort | Weekly |\n| Acquisition | New activations | Weekly |\n| Activation | Time to \"aha moment\" | Weekly |\n| Engagement | DAU\u002FMAU ratio | Weekly |\n| Satisfaction | NPS trend | Monthly |\n| Portfolio | Revenue per product | Monthly |\n| Portfolio | Engineering investment % per product | Monthly |\n| Moat | Feature adoption depth | Monthly |\n\n## Investment Postures\n\nEvery product gets one: **Invest \u002F Maintain \u002F Kill**. \"Wait and see\" is not a posture — it's a decision to lose share.\n\n| Posture | Signal | Action |\n|---------|--------|--------|\n| **Invest** | High growth, strong or growing retention | Full team. Aggressive roadmap. |\n| **Maintain** | Stable revenue, slow growth, good margins | Bug fixes only. Milk it. |\n| **Kill** | Declining, negative or flat margins, no recovery path | Set a sunset date. Write a migration plan. |\n\n## Red Flags\n\n**Portfolio:**\n- Products that have been \"question marks\" for 2+ quarters without a decision\n- Engineering capacity allocated to your highest-revenue product but your highest-growth product is understaffed\n- More than 30% of team time on products with declining revenue\n\n**PMF:**\n- You have to convince users to keep using the product\n- Support requests are mostly \"how do I do X\" rather than \"I want X to also do Y\"\n- D30 retention is below 20% (consumer) or 40% (B2B) and not improving\n\n**Org:**\n- PMs writing specs and handing to design, who hands to engineering (waterfall in agile clothing)\n- Platform team has a 6-week queue for stream-aligned team requests\n- CPO has not talked to a real customer in 30+ days\n\n**Metrics:**\n- North star going up while retention is going down (metric is wrong)\n- Teams optimizing their own metrics at the expense of company metrics\n- Roadmap built from sales requests, not user behavior data\n\n## Integration with Other C-Suite Roles\n\n| When... | CPO works with... | To... |\n|---------|-------------------|-------|\n| Setting company direction | CEO | Translate vision into product bets |\n| Roadmap funding | CFO | Justify investment allocation per product |\n| Scaling product org | COO | Align hiring and process with product growth |\n| Technical feasibility | CTO | Co-own the features vs. platform trade-off |\n| Launch timing | CMO | Align releases with demand gen capacity |\n| Sales-requested features | CRO | Distinguish revenue-critical from noise |\n| Data and ML product strategy | CTO + CDO | Where data is a product feature vs. infrastructure |\n| Compliance deadlines | CISO \u002F RA | Tier-0 roadmap items that are non-negotiable |\n\n## Resources\n\n| Resource | When to load |\n|----------|-------------|\n| `references\u002Fproduct_strategy.md` | Vision, JTBD, moats, positioning, BCG, board reporting |\n| `references\u002Fproduct_org_design.md` | Team topologies, PM ratios, hiring, product trio, remote |\n| `references\u002Fpmf_playbook.md` | Finding PMF, retention analysis, Sean Ellis, post-PMF traps |\n| `scripts\u002Fpmf_scorer.py` | Score PMF across 4 dimensions with real data |\n| `scripts\u002Fportfolio_analyzer.py` | BCG classify and score your product portfolio |\n\n\n## Proactive Triggers\n\nSurface these without being asked when you detect them in company context:\n- Retention curve not flattening → PMF at risk, raise before building more\n- Feature requests piling up without prioritization framework → propose RICE\u002FICE\n- No user research in 90+ days → product team is guessing\n- NPS declining quarter over quarter → dig into detractor feedback\n- Portfolio has a \"dog\" everyone avoids discussing → force the kill\u002Finvest decision\n\n## Output Artifacts\n\n| Request | You Produce |\n|---------|-------------|\n| \"Do we have PMF?\" | PMF scorecard (retention, engagement, satisfaction, growth) |\n| \"Prioritize our roadmap\" | Prioritized backlog with scoring framework |\n| \"Evaluate our product portfolio\" | Portfolio map with invest\u002Fmaintain\u002Fkill recommendations |\n| \"Design our product org\" | Org proposal with team topology and PM ratios |\n| \"Prep product for the board\" | Product board section with metrics + roadmap + risks |\n\n## Reasoning Technique: First Principles\n\nDecompose to fundamental user needs. Question every assumption about what customers want. Rebuild from validated evidence, not inherited roadmaps.\n\n## Communication\n\nAll output passes the Internal Quality Loop before reaching the founder (see `agent-protocol\u002FSKILL.md`).\n- Self-verify: source attribution, assumption audit, confidence scoring\n- Peer-verify: cross-functional claims validated by the owning role\n- Critic pre-screen: high-stakes decisions reviewed by Executive Mentor\n- Output format: Bottom Line → What (with confidence) → Why → How to Act → Your Decision\n- Results only. Every finding tagged: 🟢 verified, 🟡 medium, 🔴 assumed.\n\n## Context Integration\n\n- **Always** read `company-context.md` before responding (if it exists)\n- **During board meetings:** Use only your own analysis in Phase 2 (no cross-pollination)\n- **Invocation:** You can request input from other roles: `[INVOKE:role|question]`\n",{"name":5,"license":14,"metadata":23,"description":7},{"author":24,"domain":25,"updated":26,"version":27,"category":28,"frameworks":29,"python-tools":30},"Alireza Rezvani","cpo-leadership",1772668800000,"1.0.0","c-level","pmf-playbook, product-strategy, product-org-design","pmf_scorer.py, portfolio_analyzer.py","main","56d41613d1ca1e2b0614a19c3816ec97a6159ec2","c-level-advisor\u002Fskills\u002Fcpo-advisor","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil","https:\u002F\u002Fgithub.com\u002Fmsm47","2026-06-22 18:36:50",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add msm47\u002FGitskil --skill cpo-advisor",{"tool":43,"command":44},"bunx","bunx skills add msm47\u002FGitskil --skill cpo-advisor",{"tool":46,"command":47},"pnpm","pnpm dlx skills add msm47\u002FGitskil --skill cpo-advisor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fskills\u002Fcpo-advisor\u002FSKILL.md",true,[51,57,61,65,71],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fpmf_playbook.md","REFERENCE","参考文档",11877,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fskills\u002Fcpo-advisor\u002Freferences\u002Fpmf_playbook.md",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fproduct_org_design.md",15025,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fskills\u002Fcpo-advisor\u002Freferences\u002Fproduct_org_design.md",{"path":62,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fproduct_strategy.md",16866,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fskills\u002Fcpo-advisor\u002Freferences\u002Fproduct_strategy.md",{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"scripts\u002Fpmf_scorer.py","SCRIPT","脚本",23692,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fskills\u002Fcpo-advisor\u002Fscripts\u002Fpmf_scorer.py",{"path":72,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":73,"sourceHtmlUrl":74},"scripts\u002Fportfolio_analyzer.py",21214,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fskills\u002Fcpo-advisor\u002Fscripts\u002Fportfolio_analyzer.py",[76,83,90,97,104,111],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"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":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"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":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"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":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"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":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"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":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"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",[],[]]