[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75R09TSPM1M3SP4BGVWRTKD":3,"skill-same:01M75R09TSPM1M3SP4BGVWRTKD":55},{"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},"01M75R09TSPM1M3SP4BGVWRTKD","product-discovery",null,"Use when validating product opportunities, mapping assumptions, planning discovery sprints, or testing problem-solution fit before committing delivery resources.","TehutiRaEl\u002FTHEHIVE","TehutiRaEl","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F267495122?v=4","01M75N1QQQHT359S3XMYK7NPCB","01M75N1QRAW5P8P43HEHWMXCTE",0,"MIT","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fproduct-team\u002Fskills\u002Fproduct-discovery\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: product-discovery\ndescription: Use when validating product opportunities, mapping assumptions, planning discovery sprints, or testing problem-solution fit before committing delivery resources.\n---\n\n# Product Discovery\n\nRun structured discovery to identify high-value opportunities and de-risk product bets.\n\n## When To Use\n\nUse this skill for:\n- Opportunity Solution Tree facilitation\n- Assumption mapping and test planning\n- Problem validation interviews and evidence synthesis\n- Solution validation with prototypes\u002Fexperiments\n- Discovery sprint planning and outputs\n\n## Core Discovery Workflow\n\n1. Define desired outcome\n- Set one measurable outcome to improve.\n- Establish baseline and target horizon.\n\n2. Build Opportunity Solution Tree (OST)\n- Outcome -> opportunities -> solution ideas -> experiments\n- Keep opportunities grounded in user evidence, not internal opinions.\n\n3. Map assumptions\n- Identify desirability, viability, feasibility, and usability assumptions.\n- Score assumptions by risk and certainty.\n\nUse:\n```bash\npython3 scripts\u002Fassumption_mapper.py assumptions.csv\n```\n\n4. Validate the problem\n- Conduct interviews and behavior analysis.\n- Confirm frequency, severity, and willingness to solve.\n- Reject weak opportunities early.\n\n5. Validate the solution\n- Prototype before building.\n- Run concept, usability, and value tests.\n- Measure behavior, not only stated preference.\n\n6. Plan discovery sprint\n- 1-2 week cycle with explicit hypotheses\n- Daily evidence reviews\n- End with decision: proceed, pivot, or stop\n\n## Opportunity Solution Tree (Teresa Torres)\n\nStructure:\n- Outcome: metric you want to move\n- Opportunities: unmet customer needs\u002Fpains\n- Solutions: candidate interventions\n- Experiments: fastest learning actions\n\nQuality checks:\n- At least 3 distinct opportunities before converging.\n- At least 2 experiments per top opportunity.\n- Tie every branch to evidence source.\n\n## Assumption Mapping\n\nAssumption categories:\n- Desirability: users want this\n- Viability: business value exists\n- Feasibility: team can build\u002Foperate it\n- Usability: users can successfully use it\n\nPrioritization rule:\n- High risk + low certainty assumptions are tested first.\n\n## Problem Validation Techniques\n\n- Problem interviews focused on current behavior\n- Journey friction mapping\n- Support ticket and sales-call synthesis\n- Behavioral analytics triangulation\n\nEvidence threshold examples:\n- Same pain repeated across multiple target users\n- Observable workaround behavior\n- Measurable cost of current pain\n\n## Solution Validation Techniques\n\n- Concept tests (value proposition comprehension)\n- Prototype usability tests (task success\u002Ftime-to-complete)\n- Fake door or concierge tests (demand signal)\n- Limited beta cohorts (retention\u002Factivation signals)\n\n## Discovery Sprint Planning\n\nSuggested 10-day structure:\n- Day 1-2: Outcome + opportunity framing\n- Day 3-4: Assumption mapping + test design\n- Day 5-7: Problem and solution tests\n- Day 8-9: Evidence synthesis + decision options\n- Day 10: Stakeholder decision review\n\n## Tooling\n\n### `scripts\u002Fassumption_mapper.py`\n\nCLI utility that:\n- reads assumptions from CSV or inline input\n- scores risk\u002Fcertainty priority\n- emits prioritized test plan with suggested test types\n\nSee `references\u002Fdiscovery-frameworks.md` for framework details.\n","# Product Discovery\n\nRun structured discovery to identify high-value opportunities and de-risk product bets.\n\n## When To Use\n\nUse this skill for:\n- Opportunity Solution Tree facilitation\n- Assumption mapping and test planning\n- Problem validation interviews and evidence synthesis\n- Solution validation with prototypes\u002Fexperiments\n- Discovery sprint planning and outputs\n\n## Core Discovery Workflow\n\n1. Define desired outcome\n- Set one measurable outcome to improve.\n- Establish baseline and target horizon.\n\n2. Build Opportunity Solution Tree (OST)\n- Outcome -> opportunities -> solution ideas -> experiments\n- Keep opportunities grounded in user evidence, not internal opinions.\n\n3. Map assumptions\n- Identify desirability, viability, feasibility, and usability assumptions.\n- Score assumptions by risk and certainty.\n\nUse:\n```bash\npython3 scripts\u002Fassumption_mapper.py assumptions.csv\n```\n\n4. Validate the problem\n- Conduct interviews and behavior analysis.\n- Confirm frequency, severity, and willingness to solve.\n- Reject weak opportunities early.\n\n5. Validate the solution\n- Prototype before building.\n- Run concept, usability, and value tests.\n- Measure behavior, not only stated preference.\n\n6. Plan discovery sprint\n- 1-2 week cycle with explicit hypotheses\n- Daily evidence reviews\n- End with decision: proceed, pivot, or stop\n\n## Opportunity Solution Tree (Teresa Torres)\n\nStructure:\n- Outcome: metric you want to move\n- Opportunities: unmet customer needs\u002Fpains\n- Solutions: candidate interventions\n- Experiments: fastest learning actions\n\nQuality checks:\n- At least 3 distinct opportunities before converging.\n- At least 2 experiments per top opportunity.\n- Tie every branch to evidence source.\n\n## Assumption Mapping\n\nAssumption categories:\n- Desirability: users want this\n- Viability: business value exists\n- Feasibility: team can build\u002Foperate it\n- Usability: users can successfully use it\n\nPrioritization rule:\n- High risk + low certainty assumptions are tested first.\n\n## Problem Validation Techniques\n\n- Problem interviews focused on current behavior\n- Journey friction mapping\n- Support ticket and sales-call synthesis\n- Behavioral analytics triangulation\n\nEvidence threshold examples:\n- Same pain repeated across multiple target users\n- Observable workaround behavior\n- Measurable cost of current pain\n\n## Solution Validation Techniques\n\n- Concept tests (value proposition comprehension)\n- Prototype usability tests (task success\u002Ftime-to-complete)\n- Fake door or concierge tests (demand signal)\n- Limited beta cohorts (retention\u002Factivation signals)\n\n## Discovery Sprint Planning\n\nSuggested 10-day structure:\n- Day 1-2: Outcome + opportunity framing\n- Day 3-4: Assumption mapping + test design\n- Day 5-7: Problem and solution tests\n- Day 8-9: Evidence synthesis + decision options\n- Day 10: Stakeholder decision review\n\n## Tooling\n\n### `scripts\u002Fassumption_mapper.py`\n\nCLI utility that:\n- reads assumptions from CSV or inline input\n- scores risk\u002Fcertainty priority\n- emits prioritized test plan with suggested test types\n\nSee `references\u002Fdiscovery-frameworks.md` for framework details.\n",{"name":5,"description":7},"main","b4ebd6d8c3b36347a5d435bcb343a5fc1c6f08d1","skills-library\u002Fproduct-team\u002Fskills\u002Fproduct-discovery","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE","https:\u002F\u002Fgithub.com\u002FTehutiRaEl","2026-11-15 04:00:21",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add TehutiRaEl\u002FTHEHIVE --skill product-discovery",{"tool":35,"command":36},"bunx","bunx skills add TehutiRaEl\u002FTHEHIVE --skill product-discovery",{"tool":38,"command":39},"pnpm","pnpm dlx skills add TehutiRaEl\u002FTHEHIVE --skill product-discovery","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fproduct-team\u002Fskills\u002Fproduct-discovery\u002FSKILL.md",true,[43,49],{"path":44,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":47,"sourceHtmlUrl":48},"references\u002Fdiscovery-frameworks.md","REFERENCE","参考文档",1849,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fproduct-team\u002Fskills\u002Fproduct-discovery\u002Freferences\u002Fdiscovery-frameworks.md",{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"scripts\u002Fassumption_mapper.py","SCRIPT","脚本",4062,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fproduct-team\u002Fskills\u002Fproduct-discovery\u002Fscripts\u002Fassumption_mapper.py",[56,63,69,76,83,90],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":18},"01M76XP63XDM4PFPX8MMVYN9JX","preamble-gate","Use BEFORE doing any work in this repo — before the first file edit, commit, push, PR, branch operation, workflow dispatch, scheduled trigger or timer, agent\u002Fsubagent spawn, dependency install, or message sent to an outside service. Forces a plain-language preamble to the founder first: WHAT you are about to do, WHY, HOW, why it is NECESSARY, the PROJECTED IMPROVEMENT, and the COST and RISK — then, for consequential work (governance, security, money, CI\u002Ftriggers, rewriting history, multi-agent fan-out), waits for an explicit go-ahead. Read-only investigation (reading files, grep, git log\u002Fdiff, answering questions) is exempt. Applies to every AI that works in this repo, not just Claude. Founder rule, 2026-11-10, written after an unattended automation ran up cost and froze the hive. Not a substitute for wired-or-not (which governs how completion is CLAIMED); this governs what happens BEFORE work starts.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpreamble-gate\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":18},"01M75RAYXC1W361YR9NBXD59AM","visionary-recommender","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills\u002Fvisionary-recommender\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":18},"01M75RAQN9Q450RD57J2S6FSR4","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. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"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},"01M75RAG1XMCJMF30HFV5S79AK","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. Use when the user makes any research request that doesn't obviously match a more-specific specialist skill (e.g., \"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]\"). Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\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},"01M75RA8RK2JVWB8MYGRB65V75","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. Use when the user requests multi-source recency intelligence on a topic (e.g., '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]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\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},"01M75RA08RXYRFSTNC6EEEX4ZD","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. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). 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\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[]]