yaojingang/yao-open-skills is a public collection of reusable AI skills for research, decision-making, business analysis, learning, and document creation. It serves people who want repeatable, maintainable AI workflows instead of isolated prompts, and catalogued add-ons are published skills from this collection.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add yaojingang/yao-open-skills --skill yao-demand-skillgit clone --depth 1 https://github.com/yaojingang/yao-open-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/yaojingang/yao-open-skills/yao-demand-skill)<a href="https://agentmods.dev/skills/yaojingang/yao-open-skills/yao-demand-skill"><img src="https://agentmods.dev/badge/skills/yaojingang/yao-open-skills/yao-demand-skill/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/yaojingang/yao-open-skills/yao-demand-skill"><img src="https://agentmods.dev/badge/skills/yaojingang/yao-open-skills/yao-demand-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00113 | $0.01100 |
| Opus 5 | $0.00056 | $0.00550 |
| Sonnet 5 | $0.00023 | $0.00220 |
| Haiku 4.5 | $0.00011 | $0.00110 |
Grade A, and why
yao-demand-skill scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.
What ships with it
41 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/interface.yaml 779 B
- evals/README.md 451 B
- evals/resource_boundary_check.py 1.4 KB runs code
- evals/trigger_cases.json 1.2 KB
- evals/trigger_eval.py 1.5 KB runs code
- manifest.json 1.4 KB
- README.md 4.5 KB
- references/evidence-policy.md 4.1 KB
- references/kami-white-report-layout.md 11 KB
- references/report-contract.md 10 KB
- references/triangle-model.md 6.8 KB
- references/workflow.md 6.0 KB
- reports/artifact-design-profile.md 2.1 KB
- reports/humanoid-home-robot-demand-diagnosis/humanoid-home-robot-demand-diagnosis.docx 24 KB
- reports/humanoid-home-robot-demand-diagnosis/humanoid-home-robot-demand-diagnosis.html 101 KB
- reports/humanoid-home-robot-demand-diagnosis/humanoid-home-robot-demand-diagnosis.md 38 KB
- reports/humanoid-home-robot-demand-diagnosis/humanoid-home-robot-demand-diagnosis.pdf 500 KB
- reports/humanoid-home-robot-demand-diagnosis/humanoid-home-robot-demand-diagnosis.report.json 54 KB
- reports/iteration-directions.md 470 B
- reports/latest-visual-demo/ai-meeting-demand-diagnosis.docx 9.8 KB
- reports/latest-visual-demo/ai-meeting-demand-diagnosis.html 70 KB
- reports/latest-visual-demo/ai-meeting-demand-diagnosis.md 19 KB
- reports/latest-visual-demo/ai-meeting-demand-diagnosis.pdf 407 KB
- reports/nio-es8-demand-diagnosis/nio-es8-demand-diagnosis.docx 51 KB
- reports/nio-es8-demand-diagnosis/nio-es8-demand-diagnosis.html 90 KB
- reports/nio-es8-demand-diagnosis/nio-es8-demand-diagnosis.md 28 KB
- reports/nio-es8-demand-diagnosis/nio-es8-demand-diagnosis.pdf 478 KB
- reports/nio-es8-demand-diagnosis/nio-es8-demand-diagnosis.report.json 46 KB
- reports/output-risk-profile.md 2.2 KB
- reports/prompt-quality-profile.md 1.8 KB
- reports/rendered-sample/sample-ai-meeting-tool.docx 10.0 KB
- reports/rendered-sample/sample-ai-meeting-tool.html 72 KB
- reports/rendered-sample/sample-ai-meeting-tool.md 20 KB
- reports/rendered-sample/sample-ai-meeting-tool.pdf 421 KB
- reports/sample-ai-meeting-tool.report.json 27 KB
- reports/source-synthesis.md 2.1 KB
- reports/visual-diagnostic-report-iteration-plan.md 14 KB
- scripts/render_report.py 99 KB runs code
- scripts/score_triangle.py 4.6 KB runs code
- scripts/validate_report.py 9.6 KB runs code
- templates/report.schema.json 8.6 KB
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 67 lines · 113 tokens per session scan A d0e77da59b36
yao-demand-skill is a skill published in the GitHub repository yaojingang/yao-open-skills (1,311 stars, last pushed 14d ago), licensed MIT. It adds 113 tokens to every session and 1,100 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…