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-business-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-business-skill)<a href="https://agentmods.dev/skills/yaojingang/yao-open-skills/yao-business-skill"><img src="https://agentmods.dev/badge/skills/yaojingang/yao-open-skills/yao-business-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-business-skill"><img src="https://agentmods.dev/badge/skills/yaojingang/yao-open-skills/yao-business-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.00073 | $0.00671 |
| Opus 5 | $0.00036 | $0.00336 |
| Sonnet 5 | $0.00015 | $0.00134 |
| Haiku 4.5 | $0.00007 | $0.00067 |
Grade A, and why
yao-business-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 13d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Yao Business Skill
Evidence-based business model analysis. Separate facts, estimates, hypotheses, and recommendations.
Use This Skill For
- turning a new idea into
3-5viable business model options - diagnosing an existing product, website, or company
- comparing direct competitors and cross-industry analogs
- proposing business model upgrades with formulas, risks, and validation
- studying a mature company to separate reusable from environment-specific patterns
Do Not Route Here
- generic marketing ideation without business model analysis
- standalone legal, tax, accounting, or valuation advice
- pure financial model builds that do not need business model diagnosis
- gray or illegal monetization design; those belong only in risk recognition and avoidance
Workflow
- Choose the branch:
idea_to_model,model_diagnosis, orcompany_case_study. - Build a
market_environmentprofile before recommending pricing, channels, or sales motion. - Gather evidence by tier and mark what is confirmed, estimated, assumed, or unknown.
- Analyze the current or proposed model, including AI as cost driver and monetization lever.
- Produce branch-appropriate JSON, HTML, and a short narrative summary.
Branch Rules
- For new ideas, generate
3-5options and include one lower-friction, one higher-margin, and one higher-barrier path. - For existing products, map current monetization, competitors, analogs, upgrade ideas, and environment fit.
- For mature companies, separate environment advantages from reusable patterns so the reader does not copy context-specific advantages blindly.
Output Contract
- Always distinguish
fact,estimate,hypothesis, andrecommendation. - Every revenue line or new monetization path needs formula, low/base/high range, and confidence.
- When competitor benchmarking applies, target at least
10direct competitors and10cross-industry analogs; if not possible, explain the gap. - Include a
market_environment_fitsection and anAI leverage and AI disruptionsection. - Final artifacts are a concise narrative, a structured JSON payload, and an HTML report.
What ships with it
22 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 695 B
- manifest.json 498 B
- references/chart-playbook.md 2.6 KB
- references/market-environment.md 3.6 KB
- references/report-contract.md 2.8 KB
- references/scenario-playbooks.md 2.7 KB
- references/source-foundation.md 3.4 KB
- reports/hubspot-formal-input.json 58 KB
- reports/hubspot-formal-report.html 161 KB
- reports/hubspot-formal-report.json 77 KB
- reports/sample-assembly-input.json 9.4 KB
- reports/sample-assembly-output.html 105 KB
- reports/sample-assembly-output.json 22 KB
- reports/sample-model-diagnosis.html 92 KB
- reports/sample-model-diagnosis.json 28 KB
- reports/source-synthesis.md 1.8 KB
- scripts/assemble_report.py 28 KB runs code
- scripts/render_report.py 1.8 KB runs code
- scripts/score_metrics.py 7.6 KB runs code
- scripts/validate_report.py 9.6 KB runs code
- templates/report-skeleton.html 83 KB
- templates/report.schema.json 17 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.
- 13d ago First seen · 58 lines · 73 tokens per session scan A 91d77776806d
yao-business-skill is a skill published in the GitHub repository yaojingang/yao-open-skills (1,314 stars, last pushed 15d ago), licensed MIT. It adds 73 tokens to every session and 671 once invoked, about $0.0004 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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…