yao-demand-skill
Evaluate product demand from product links, product descriptions, PRDs, websites, app-store pages, white papers, sales decks, screenshots, or funding materials using the demand triangle model: lack, target object, and consumer ability. Use when asked for demand assessment, pre-investment product review, growth diagnosis, positioning validation, competitor-backed demand evidence, or a multi-format demand report. Do not use for pure market sizing, generic business-model design, UX-only review, legal/financial advice, or ad-copy ideation without demand evidence.
- License 许可
- MIT
- 最近更新
- 2026-10-14
- Stars
- ★ 1.3k
- Forks
- 145
01 前言 Front Matter
- name
- yao-demand-skill
- metadata
- { "mode": "production", "model": "Demand Triangle: lack + target object + consumer ability", "author": "Yao Team", "output": "Markdown, HTML, Word, PDF" }
- description
- Evaluate product demand from product links, product descriptions, PRDs, websites, app-store pages, white papers, sales decks, screenshots, or funding materials using the demand triangle model: lack, target object, and consumer ability. Use when asked for demand assessment, pre-investment product review, growth diagnosis, positioning validation, competitor-backed demand evidence, or a multi-format demand report. Do not use for pure market sizing, generic business-model design, UX-only review, legal/financial advice, or ad-copy ideation without demand evidence.
02 资源文件 41
- 参考文档agents/interface.yaml779 B
- 参考文档evals/README.md451 B
- 脚本evals/resource_boundary_check.py1.4 KB
- 参考文档evals/trigger_cases.json1.2 KB
- 脚本evals/trigger_eval.py1.5 KB
- 参考文档manifest.json1.4 KB
- 参考文档README.md4.5 KB
- 参考文档references/evidence-policy.md4.1 KB
- 参考文档references/kami-white-report-layout.md11.2 KB
- 参考文档references/report-contract.md10.1 KB
- 参考文档references/triangle-model.md6.8 KB
- 参考文档references/workflow.md6.0 KB
- 参考文档reports/artifact-design-profile.md2.1 KB
- 资产文件reports/humanoid-home-robot-demand-diagnosis/humanoid-home-robot-demand-diagnosis.docx23.9 KB
- 参考文档reports/humanoid-home-robot-demand-diagnosis/humanoid-home-robot-demand-diagnosis.html101.1 KB
- 参考文档reports/humanoid-home-robot-demand-diagnosis/humanoid-home-robot-demand-diagnosis.md38.2 KB
- 资产文件reports/humanoid-home-robot-demand-diagnosis/humanoid-home-robot-demand-diagnosis.pdf500.1 KB
- 参考文档reports/humanoid-home-robot-demand-diagnosis/humanoid-home-robot-demand-diagnosis.report.json53.9 KB
- 参考文档reports/iteration-directions.md470 B
- 资产文件reports/latest-visual-demo/ai-meeting-demand-diagnosis.docx9.8 KB
- 参考文档reports/latest-visual-demo/ai-meeting-demand-diagnosis.html69.7 KB
- 参考文档reports/latest-visual-demo/ai-meeting-demand-diagnosis.md19.1 KB
- 资产文件reports/latest-visual-demo/ai-meeting-demand-diagnosis.pdf407.2 KB
- 资产文件reports/nio-es8-demand-diagnosis/nio-es8-demand-diagnosis.docx51.1 KB
- 参考文档reports/nio-es8-demand-diagnosis/nio-es8-demand-diagnosis.html90.2 KB
- 参考文档reports/nio-es8-demand-diagnosis/nio-es8-demand-diagnosis.md28.0 KB
- 资产文件reports/nio-es8-demand-diagnosis/nio-es8-demand-diagnosis.pdf478.0 KB
- 参考文档reports/nio-es8-demand-diagnosis/nio-es8-demand-diagnosis.report.json46.0 KB
- 参考文档reports/output-risk-profile.md2.2 KB
- 参考文档reports/prompt-quality-profile.md1.8 KB
- 资产文件reports/rendered-sample/sample-ai-meeting-tool.docx10.0 KB
- 参考文档reports/rendered-sample/sample-ai-meeting-tool.html71.8 KB
- 参考文档reports/rendered-sample/sample-ai-meeting-tool.md19.6 KB
- 资产文件reports/rendered-sample/sample-ai-meeting-tool.pdf421.0 KB
- 参考文档reports/sample-ai-meeting-tool.report.json26.7 KB
- 参考文档reports/source-synthesis.md2.1 KB
- 参考文档reports/visual-diagnostic-report-iteration-plan.md14.1 KB
- 脚本scripts/render_report.py98.9 KB
- 脚本scripts/score_triangle.py4.6 KB
- 脚本scripts/validate_report.py9.6 KB
- 参考文档templates/report.schema.json8.6 KB
03 SKILL.md 正文
Yao Demand Skill
Evidence-backed demand assessment for products, services, apps, SaaS, AI tools, consumer goods, education products, and early-stage ventures.
Use This Skill For
- assessing whether a product has a solid demand foundation before building, investing, launching, or scaling
- diagnosing weak conversion, weak retention, vague positioning, pricing friction, trust friction, or adoption barriers
- comparing direct competitors, indirect substitutes, current user workarounds, and the option of not buying
- producing a visual demand diagnosis report with citations, scores, red flags, 10+ chart modules, experiments, forecasts, and four final formats
Do Not Route Here
- pure TAM/SAM/SOM market sizing without product-demand diagnosis
- generic monetization or business-model option design; use a business-model skill instead
- UX heuristic review without demand, JTBD, or adoption evidence
- legal, financial, medical, or investment advice as a final decision
- manipulative marketing designed to shame, scare, addict, or exploit vulnerable users
Workflow
- Confirm the product input. Accept a URL, text description, PRD, website copy, docs, screenshot, app-store page, sales material, or funding deck. Ask only one concise question if no product substance is available.
- Build the product canvas: product definition, user, scenario, features, price, promise, business model, market, source list, and unresolved assumptions.
- Plan evidence. Prioritize official sources, third-party validation, user feedback, competitor/substitute evidence, and time-sensitive market or regulatory facts.
- Research only evidence that can support or challenge demand. Current product, price, competitor, market, legal, or regulatory facts must be verified with sources and dates.
- Segment users by JTBD, trigger scenario, buying role, current alternatives, and adoption blockers.
- Analyze the three demand triangle dimensions:
lack,target_object, andconsumer_ability. Include evidence, counter-evidence, assumptions, and improvement paths. - Score each dimension from
0to10, then calculate total score with the geometric short-board formula and confidence adjustment. - Produce visual diagnostics: at least 10 chart modules, each with one or two insight sentences, one recommendation, confidence, and evidence or assumption binding.
- Produce recommendations, forecast scenarios, and a final 30/60/90 day action plan: positioning, product, pricing, onboarding, trust, channel, and validation experiments.
- Run QA: citation coverage, time consistency, evidence diversity, at least three counter-signals, score explainability, chart completeness, ethics, and layout readiness.
- Write a structured report JSON, then use
scripts/render_report.pyto create Markdown, HTML, Word, and PDF outputs.
Output Contract
- Always produce the final report in four formats:
.md,.html,.docx, and.pdf. - Use one canonical
report.jsonas the rendering source when possible, so the four outputs remain consistent. - HTML must include a top follow menu bar that stays pinned while the page scrolls, with quiet anchor navigation.
- Formal reports must follow a
summary -> visual diagnostics -> deep analysis -> final planstructure. - Formal reports must include at least 10 chart modules. HTML/PDF render them as inline SVG. Markdown and Word must include chart-equivalent tables or images.
- All report backgrounds are pure white. Borrow Kami's editorial hierarchy, ink-blue accent, table discipline, typography, spacing, and production checks, but override Kami's parchment background.
- Every key factual claim must either cite a source ID or be labeled as an assumption.
- Every score must include evidence, reasoning, uncertainty, and a concrete improvement path.
- Forecasts must be scenario-based and labeled with assumptions and confidence. Do not present uncertain adoption outcomes as deterministic predictions.
Reference Map
- Read
references/workflow.mdbefore starting an assessment. - Read
references/evidence-policy.mdbefore using sources, citations, or current facts. - Read
references/triangle-model.mdbefore scoring. - Read
references/report-contract.mdbefore writing the report JSON or final narrative. - Read
references/kami-white-report-layout.mdbefore rendering the four output formats. - Use
templates/report.schema.jsonas the report JSON target. - Use
scripts/score_triangle.pyto calculate or verify weighted scores. - Use
scripts/validate_report.pybefore rendering. - Use
scripts/render_report.pyto generate Markdown, HTML, Word, and PDF.
04 同仓库更多 Skills
yao-weread-skill
当用户需要分析微信读书阅读历史、生成读书报告、可视化阅读统计、笔记、书架、词云、热力图、雷达图,或导出精排 HTML 报告时使用。也适用于创建 AI 创业者示例阅读报告。不用于通用图书推荐,或不生成报告的原始微信读书 API 查询。
yao-websecurity-skill
Use when auditing an authorized website, SaaS, API, AI app, local code path, GitHub repo, staging URL, or owned runtime for security risks, vulnerability checklist scoring, static review, dynamic review, active validation, or Chinese security reports.
yao-tutorial-skill
Create standalone beginner tutorial packages from a topic or supplied references, with adaptive research, course-style outline design, chapter visuals, and Markdown/DOCX/PDF/HTML exports. Use for textbook-like tutorials, course guides, teaching documents, or long beginner guides; not for quick answers, link summaries, pure diagrams, or file conversion.
yao-positioning-skill
Generate evidence-aware positioning reports for personal IPs, courses, products, services, brands, or companies by combining positioning theory, course-marketing analysis, user intent, competitor research, market demand, and verifiable advantages. Use when users ask for 定位、差异化分析、优势分析、心智定位、品类定位、竞品定位研究、定位报告或再定位建议. Do not use for slogan-only copywriting, generic marketing ideas, standalone market research without a positioning recommendation, or brand knowledge-base construction.
yao-open-skills-sync
Manage the yao-open-skills public collection. Use this skill whenever the user wants to evaluate whether a local skill should be open sourced, import a local skill into the yao-open-skills repository, register which skills are already public, track GitHub sync status, or update the collection README and catalog after adding or refreshing a skill.
yao-naval-almanack-skill
Improve career choices, service/productization, reusable income/ownership, long-term partnerships, attention allocation, and desire/social-comparison tradeoffs using Naval principles, even without naming Naval. 中文:工作选择、找专长、重复交付产品化、长期合作、忙却无积累、目标取舍、同龄人比较。Also explain, verify, and apply 《纳瓦尔宝典》, Naval Ravikant, or quotes. Use for substantive advice; skip generic planning/editing, coding, arithmetic, vague anxiety, trading, clinical care, and passing name mentions. Honor explicit opt-outs.