[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76RYKR89ZP9MQKAB1TCSMD8":3,"skill-same:01M76RYKR89ZP9MQKAB1TCSMD8":67},{"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},"01M76RYKR89ZP9MQKAB1TCSMD8","competitive-teardown",null,"Analyzes competitor products and companies by synthesizing data from pricing pages, app store reviews, job postings, SEO signals, and social media into structured competitive intelligence. Produces feature comparison matrices scored across 12 dimensions, SWOT analyses, positioning maps, UX audits, pricing model breakdowns, action item roadmaps, and stakeholder presentation templates. Use when conducting competitor analysis, comparing products against competitors, researching the competitive landscape, building battle cards for sales, preparing for a product strategy or roadmap session, responding to a competitor's new feature or pricing change, or performing a quarterly competitive review.","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\u002Fcompetitive-teardown\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: \"competitive-teardown\"\ndescription: \"Analyzes competitor products and companies by synthesizing data from pricing pages, app store reviews, job postings, SEO signals, and social media into structured competitive intelligence. Produces feature comparison matrices scored across 12 dimensions, SWOT analyses, positioning maps, UX audits, pricing model breakdowns, action item roadmaps, and stakeholder presentation templates. Use when conducting competitor analysis, comparing products against competitors, researching the competitive landscape, building battle cards for sales, preparing for a product strategy or roadmap session, responding to a competitor's new feature or pricing change, or performing a quarterly competitive review.\"\n---\n\n# Competitive Teardown\n\n**Tier:** POWERFUL  \n**Category:** Product Team  \n**Domain:** Competitive Intelligence, Product Strategy, Market Analysis\n\n---\n\n## When to Use\n\n- Before a product strategy or roadmap session\n- When a competitor launches a major feature or pricing change\n- Quarterly competitive review\n- Before a sales pitch where you need battle card data\n- When entering a new market segment\n\n---\n\n## Teardown Workflow\n\nFollow these steps in sequence to produce a complete teardown:\n\n1. **Define competitors** — List 2–4 competitors to analyze. Confirm which is the primary focus.\n2. **Collect data** — Use `references\u002Fdata-collection-guide.md` to gather raw signals from at least 3 sources per competitor (website, reviews, job postings, SEO, social).  \n   _Validation checkpoint: Before proceeding, confirm you have pricing data, at least 20 reviews, and job posting counts for each competitor._\n3. **Score using rubric** — Apply the 12-dimension rubric below to produce a numeric scorecard for each competitor and your own product.  \n   _Validation checkpoint: Every dimension should have a score and at least one supporting evidence note._\n4. **Generate outputs** — Populate the templates in `references\u002Fanalysis-templates.md` (Feature Matrix, Pricing Analysis, SWOT, Positioning Map, UX Audit).\n5. **Build action plan** — Translate findings into the Action Items template (quick wins \u002F medium-term \u002F strategic).\n6. **Package for stakeholders** — Assemble the Stakeholder Presentation using outputs from steps 3–5.\n\n---\n\n## Data Collection Guide\n\n> Full executable scripts for each source are in `references\u002Fdata-collection-guide.md`. Summaries of what to capture are below.\n\n### 1. Website Analysis\n\nKey things to capture:\n- Pricing tiers and price points\n- Feature lists per tier\n- Primary CTA and messaging\n- Case studies \u002F customer logos (signals ICP)\n- Integration logos\n- Trust signals (certifications, compliance badges)\n\n### 2. App Store Reviews\n\nReview sentiment categories:\n- **Praise** → what users love (defend \u002F strengthen these)\n- **Feature requests** → unmet needs (opportunity gaps)\n- **Bugs** → quality signals\n- **UX complaints** → friction points you can beat them on\n\n**Sample App Store query (iTunes Search API):**\n```\nGET https:\u002F\u002Fitunes.apple.com\u002Fsearch?term=\u003Ccompetitor_name>&entity=software&limit=1\n# Extract trackId, then:\nGET https:\u002F\u002Fitunes.apple.com\u002Frss\u002Fcustomerreviews\u002Fid=\u003CtrackId>\u002FsortBy=mostRecent\u002Fjson?l=en&limit=50\n```\nParse `entry[].content.label` for review text and `entry[].im:rating.label` for star rating.\n\n### 3. Job Postings (Team Size & Tech Stack Signals)\n\nSignals from job postings:\n- **Engineering volume** → scaling vs. consolidating\n- **Specific tech mentions** → stack (React\u002FVue, Postgres\u002FMongo, AWS\u002FGCP)\n- **Sales\u002FCS ratio** → product-led vs. sales-led motion\n- **Data\u002FML roles** → upcoming AI features\n- **Compliance roles** → regulatory expansion\n\n### 4. SEO Analysis\n\nSEO signals to capture:\n- Top 20 organic keywords (intent: informational \u002F navigational \u002F commercial)\n- Domain Authority \u002F backlink count\n- Blog publishing cadence and topics\n- Which pages rank (product pages vs. blog vs. docs)\n\n### 5. Social Media Sentiment\n\nCapture recent mentions via Twitter\u002FX API v2, Reddit, or LinkedIn. Look for recurring praise, complaints, and feature requests. See `references\u002Fdata-collection-guide.md` for API query examples.\n\n---\n\n## Scoring Rubric (12 Dimensions, 1-5)\n\n| # | Dimension | 1 (Weak) | 3 (Average) | 5 (Best-in-class) |\n|---|-----------|----------|-------------|-------------------|\n| 1 | **Features** | Core only, many gaps | Solid coverage | Comprehensive + unique |\n| 2 | **Pricing** | Confusing \u002F overpriced | Market-rate, clear | Transparent, flexible, fair |\n| 3 | **UX** | Confusing, high friction | Functional | Delightful, minimal friction |\n| 4 | **Performance** | Slow, unreliable | Acceptable | Fast, high uptime |\n| 5 | **Docs** | Sparse, outdated | Decent coverage | Comprehensive, searchable |\n| 6 | **Support** | Email only, slow | Chat + email | 24\u002F7, great response |\n| 7 | **Integrations** | 0-5 integrations | 6-25 | 26+ or deep ecosystem |\n| 8 | **Security** | No mentions | SOC2 claimed | SOC2 Type II, ISO 27001 |\n| 9 | **Scalability** | No enterprise tier | Mid-market ready | Enterprise-grade |\n| 10 | **Brand** | Generic, unmemorable | Decent positioning | Strong, differentiated |\n| 11 | **Community** | None | Forum \u002F Slack | Active, vibrant community |\n| 12 | **Innovation** | No recent releases | Quarterly | Frequent, meaningful |\n\n**Example completed row** (Competitor: Acme Corp, Dimension 3 – UX):\n\n| Dimension | Acme Corp Score | Evidence |\n|-----------|----------------|---------|\n| UX | 2 | App Store reviews cite \"confusing navigation\" (38 mentions); onboarding requires 7 steps before TTFV; no onboarding wizard; CC required at signup. |\n\nApply this pattern to all 12 dimensions for each competitor.\n\n---\n\n## Templates\n\n> Full template markdown is in `references\u002Fanalysis-templates.md`. Abbreviated reference below.\n\n### Feature Comparison Matrix\n\nRows: core features, pricing tiers, platform capabilities (web, iOS, Android, API).  \nColumns: your product + up to 3 competitors.  \nScore each cell 1–5. Sum to get total out of 60.  \n**Score legend:** 5=Best-in-class, 4=Strong, 3=Average, 2=Below average, 1=Weak\u002FMissing\n\n### Pricing Analysis\n\nCapture per competitor: model type (per-seat \u002F usage-based \u002F flat rate \u002F freemium), entry\u002Fmid\u002Fenterprise price points, free trial length.  \nSummarize: price leader, value leader, premium positioning, your position, and 2–3 pricing opportunity bullets.\n\n### SWOT Analysis\n\nFor each competitor: 3–5 bullets per quadrant (Strengths, Weaknesses, Opportunities for us, Threats to us). Anchor every bullet to a data signal (review quote, job posting count, pricing page, etc.).\n\n### Positioning Map\n\n2x2 axes (e.g., Simple ↔ Complex \u002F Low Value ↔ High Value). Place each competitor and your product. Bubble size = market share or funding. See `references\u002Fanalysis-templates.md` for ASCII and editable versions.\n\n### UX Audit Checklist\n\nOnboarding: TTFV (minutes), steps to activation, CC-required, onboarding wizard quality.  \nKey workflows: steps, friction points, comparative score (yours vs. theirs).  \nMobile: iOS\u002FAndroid ratings, feature parity, top complaint and praise.  \nNavigation: global search, keyboard shortcuts, in-app help.\n\n### Action Items\n\n| Horizon | Effort | Examples |\n|---------|--------|---------|\n| Quick wins (0–4 wks) | Low | Add review badges, publish comparison landing page |\n| Medium-term (1–3 mo) | Moderate | Launch free tier, improve onboarding TTFV, add top-requested integration |\n| Strategic (3–12 mo) | High | Enter new market, build API v2, achieve SOC2 Type II |\n\n### Stakeholder Presentation (7 slides)\n\n1. **Executive Summary** — Threat level (LOW\u002FMEDIUM\u002FHIGH\u002FCRITICAL), top strength, top opportunity, recommended action\n2. **Market Position** — 2x2 positioning map\n3. **Feature Scorecard** — 12-dimension radar or table, total scores\n4. **Pricing Analysis** — Comparison table + key insight\n5. **UX Highlights** — What they do better (3 bullets) vs. where we win (3 bullets)\n6. **Voice of Customer** — Top 3 review complaints (quoted or paraphrased)\n7. **Our Action Plan** — Quick wins, medium-term, strategic priorities; Appendix with raw data\n\n## Related Skills\n\n- **Product Strategist** (`product-team\u002Fproduct-strategist\u002F`) — Competitive insights feed OKR and strategy planning\n- **Landing Page Generator** (`product-team\u002Flanding-page-generator\u002F`) — Competitive positioning informs landing page messaging\n","# Competitive Teardown\n\n**Tier:** POWERFUL  \n**Category:** Product Team  \n**Domain:** Competitive Intelligence, Product Strategy, Market Analysis\n\n---\n\n## When to Use\n\n- Before a product strategy or roadmap session\n- When a competitor launches a major feature or pricing change\n- Quarterly competitive review\n- Before a sales pitch where you need battle card data\n- When entering a new market segment\n\n---\n\n## Teardown Workflow\n\nFollow these steps in sequence to produce a complete teardown:\n\n1. **Define competitors** — List 2–4 competitors to analyze. Confirm which is the primary focus.\n2. **Collect data** — Use `references\u002Fdata-collection-guide.md` to gather raw signals from at least 3 sources per competitor (website, reviews, job postings, SEO, social).  \n   _Validation checkpoint: Before proceeding, confirm you have pricing data, at least 20 reviews, and job posting counts for each competitor._\n3. **Score using rubric** — Apply the 12-dimension rubric below to produce a numeric scorecard for each competitor and your own product.  \n   _Validation checkpoint: Every dimension should have a score and at least one supporting evidence note._\n4. **Generate outputs** — Populate the templates in `references\u002Fanalysis-templates.md` (Feature Matrix, Pricing Analysis, SWOT, Positioning Map, UX Audit).\n5. **Build action plan** — Translate findings into the Action Items template (quick wins \u002F medium-term \u002F strategic).\n6. **Package for stakeholders** — Assemble the Stakeholder Presentation using outputs from steps 3–5.\n\n---\n\n## Data Collection Guide\n\n> Full executable scripts for each source are in `references\u002Fdata-collection-guide.md`. Summaries of what to capture are below.\n\n### 1. Website Analysis\n\nKey things to capture:\n- Pricing tiers and price points\n- Feature lists per tier\n- Primary CTA and messaging\n- Case studies \u002F customer logos (signals ICP)\n- Integration logos\n- Trust signals (certifications, compliance badges)\n\n### 2. App Store Reviews\n\nReview sentiment categories:\n- **Praise** → what users love (defend \u002F strengthen these)\n- **Feature requests** → unmet needs (opportunity gaps)\n- **Bugs** → quality signals\n- **UX complaints** → friction points you can beat them on\n\n**Sample App Store query (iTunes Search API):**\n```\nGET https:\u002F\u002Fitunes.apple.com\u002Fsearch?term=\u003Ccompetitor_name>&entity=software&limit=1\n# Extract trackId, then:\nGET https:\u002F\u002Fitunes.apple.com\u002Frss\u002Fcustomerreviews\u002Fid=\u003CtrackId>\u002FsortBy=mostRecent\u002Fjson?l=en&limit=50\n```\nParse `entry[].content.label` for review text and `entry[].im:rating.label` for star rating.\n\n### 3. Job Postings (Team Size & Tech Stack Signals)\n\nSignals from job postings:\n- **Engineering volume** → scaling vs. consolidating\n- **Specific tech mentions** → stack (React\u002FVue, Postgres\u002FMongo, AWS\u002FGCP)\n- **Sales\u002FCS ratio** → product-led vs. sales-led motion\n- **Data\u002FML roles** → upcoming AI features\n- **Compliance roles** → regulatory expansion\n\n### 4. SEO Analysis\n\nSEO signals to capture:\n- Top 20 organic keywords (intent: informational \u002F navigational \u002F commercial)\n- Domain Authority \u002F backlink count\n- Blog publishing cadence and topics\n- Which pages rank (product pages vs. blog vs. docs)\n\n### 5. Social Media Sentiment\n\nCapture recent mentions via Twitter\u002FX API v2, Reddit, or LinkedIn. Look for recurring praise, complaints, and feature requests. See `references\u002Fdata-collection-guide.md` for API query examples.\n\n---\n\n## Scoring Rubric (12 Dimensions, 1-5)\n\n| # | Dimension | 1 (Weak) | 3 (Average) | 5 (Best-in-class) |\n|---|-----------|----------|-------------|-------------------|\n| 1 | **Features** | Core only, many gaps | Solid coverage | Comprehensive + unique |\n| 2 | **Pricing** | Confusing \u002F overpriced | Market-rate, clear | Transparent, flexible, fair |\n| 3 | **UX** | Confusing, high friction | Functional | Delightful, minimal friction |\n| 4 | **Performance** | Slow, unreliable | Acceptable | Fast, high uptime |\n| 5 | **Docs** | Sparse, outdated | Decent coverage | Comprehensive, searchable |\n| 6 | **Support** | Email only, slow | Chat + email | 24\u002F7, great response |\n| 7 | **Integrations** | 0-5 integrations | 6-25 | 26+ or deep ecosystem |\n| 8 | **Security** | No mentions | SOC2 claimed | SOC2 Type II, ISO 27001 |\n| 9 | **Scalability** | No enterprise tier | Mid-market ready | Enterprise-grade |\n| 10 | **Brand** | Generic, unmemorable | Decent positioning | Strong, differentiated |\n| 11 | **Community** | None | Forum \u002F Slack | Active, vibrant community |\n| 12 | **Innovation** | No recent releases | Quarterly | Frequent, meaningful |\n\n**Example completed row** (Competitor: Acme Corp, Dimension 3 – UX):\n\n| Dimension | Acme Corp Score | Evidence |\n|-----------|----------------|---------|\n| UX | 2 | App Store reviews cite \"confusing navigation\" (38 mentions); onboarding requires 7 steps before TTFV; no onboarding wizard; CC required at signup. |\n\nApply this pattern to all 12 dimensions for each competitor.\n\n---\n\n## Templates\n\n> Full template markdown is in `references\u002Fanalysis-templates.md`. Abbreviated reference below.\n\n### Feature Comparison Matrix\n\nRows: core features, pricing tiers, platform capabilities (web, iOS, Android, API).  \nColumns: your product + up to 3 competitors.  \nScore each cell 1–5. Sum to get total out of 60.  \n**Score legend:** 5=Best-in-class, 4=Strong, 3=Average, 2=Below average, 1=Weak\u002FMissing\n\n### Pricing Analysis\n\nCapture per competitor: model type (per-seat \u002F usage-based \u002F flat rate \u002F freemium), entry\u002Fmid\u002Fenterprise price points, free trial length.  \nSummarize: price leader, value leader, premium positioning, your position, and 2–3 pricing opportunity bullets.\n\n### SWOT Analysis\n\nFor each competitor: 3–5 bullets per quadrant (Strengths, Weaknesses, Opportunities for us, Threats to us). Anchor every bullet to a data signal (review quote, job posting count, pricing page, etc.).\n\n### Positioning Map\n\n2x2 axes (e.g., Simple ↔ Complex \u002F Low Value ↔ High Value). Place each competitor and your product. Bubble size = market share or funding. See `references\u002Fanalysis-templates.md` for ASCII and editable versions.\n\n### UX Audit Checklist\n\nOnboarding: TTFV (minutes), steps to activation, CC-required, onboarding wizard quality.  \nKey workflows: steps, friction points, comparative score (yours vs. theirs).  \nMobile: iOS\u002FAndroid ratings, feature parity, top complaint and praise.  \nNavigation: global search, keyboard shortcuts, in-app help.\n\n### Action Items\n\n| Horizon | Effort | Examples |\n|---------|--------|---------|\n| Quick wins (0–4 wks) | Low | Add review badges, publish comparison landing page |\n| Medium-term (1–3 mo) | Moderate | Launch free tier, improve onboarding TTFV, add top-requested integration |\n| Strategic (3–12 mo) | High | Enter new market, build API v2, achieve SOC2 Type II |\n\n### Stakeholder Presentation (7 slides)\n\n1. **Executive Summary** — Threat level (LOW\u002FMEDIUM\u002FHIGH\u002FCRITICAL), top strength, top opportunity, recommended action\n2. **Market Position** — 2x2 positioning map\n3. **Feature Scorecard** — 12-dimension radar or table, total scores\n4. **Pricing Analysis** — Comparison table + key insight\n5. **UX Highlights** — What they do better (3 bullets) vs. where we win (3 bullets)\n6. **Voice of Customer** — Top 3 review complaints (quoted or paraphrased)\n7. **Our Action Plan** — Quick wins, medium-term, strategic priorities; Appendix with raw data\n\n## Related Skills\n\n- **Product Strategist** (`product-team\u002Fproduct-strategist\u002F`) — Competitive insights feed OKR and strategy planning\n- **Landing Page Generator** (`product-team\u002Flanding-page-generator\u002F`) — Competitive positioning informs landing page messaging\n",{"name":5,"description":7},"main","56d41613d1ca1e2b0614a19c3816ec97a6159ec2","product-team\u002Fskills\u002Fcompetitive-teardown","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 competitive-teardown",{"tool":35,"command":36},"bunx","bunx skills add msm47\u002FGitskil --skill competitive-teardown",{"tool":38,"command":39},"pnpm","pnpm dlx skills add msm47\u002FGitskil --skill competitive-teardown","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fproduct-team\u002Fskills\u002Fcompetitive-teardown\u002FSKILL.md",true,[43,49,53,57,61],{"path":44,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":47,"sourceHtmlUrl":48},"references\u002Fanalysis-templates.md","REFERENCE","参考文档",6674,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fproduct-team\u002Fskills\u002Fcompetitive-teardown\u002Freferences\u002Fanalysis-templates.md",{"path":50,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fcompetitive-analysis-frameworks.md",3286,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fproduct-team\u002Fskills\u002Fcompetitive-teardown\u002Freferences\u002Fcompetitive-analysis-frameworks.md",{"path":54,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fdata-collection-guide.md",4977,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fproduct-team\u002Fskills\u002Fcompetitive-teardown\u002Freferences\u002Fdata-collection-guide.md",{"path":58,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fscoring-rubric.md",5076,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fproduct-team\u002Fskills\u002Fcompetitive-teardown\u002Freferences\u002Fscoring-rubric.md",{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"scripts\u002Fcompetitive_matrix_builder.py","SCRIPT","脚本",10783,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fproduct-team\u002Fskills\u002Fcompetitive-teardown\u002Fscripts\u002Fcompetitive_matrix_builder.py",[68,75,82,89,96,103],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"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":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"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":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"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":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"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",[],[]]