yao-crux-skill
Use when a user is stuck in a complex real-world situation with many conflicts, limited resources, unclear priorities, or asks to identify the principal contradiction, secondary contradictions, dominant aspect, breakthrough actions, monitoring thresholds, probability projection, and Markdown/Word/HT…
Install / Use
npx skills add yaojingang/yao-open-skills --skill yao-crux-skillInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
OperationsSupported Platforms
Our assessment of yao-crux-skill
yao-crux-skill scores 83/100 on our quality scale, 605th of 746 Operations skills we index.
Its SKILL.md is 9.9 KB long, split into 6 sections and no code examples: a thorough specification that gives an agent plenty to work with.
With 1,318 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 3 months ago, so yao-crux-skill is actively maintained.
- Our last check on 2026-11-07 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
yao-crux-skill compared with similar skills
All 4 of these similar skills score higher than yao-crux-skill; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| yao-crux-skill (this skill)by yaojingang | 83 | 1.3k | 3mo ago | SKILL.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| designby nextlevelbuilder | 100 | 149.0k | 6d ago | SKILL.md |
Frequently asked questions
- How do I install yao-crux-skill?
- Run
npx skills add yaojingang/yao-open-skills --skill yao-crux-skill. The install tabs above show the steps for each supported agent. - Which AI agents does yao-crux-skill work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is yao-crux-skill safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is yao-crux-skill still maintained?
- The repository was last updated about 3 months ago, so yao-crux-skill is actively maintained.
Skill content
View source on GitHubname: yao-crux-skill description: Use when a user is stuck in a complex real-world situation with many conflicts, limited resources, unclear priorities, or asks to identify the principal contradiction, secondary contradictions, dominant aspect, breakthrough actions, monitoring thresholds, probability projection, and Markdown/Word/HTML/PDF reports. Triggers on 矛盾论, 主要矛盾, 次要矛盾, 主次矛盾, 卡住了, 优先级混乱, 找关键问题, 资源有限, 冲突很多. Do not use for philosophy-only summaries, Mao text commentary with no live case, generic brainstorming with no diagnosis, or final licensed medical, legal, investment, or psychological-crisis advice. metadata: author: Yao Team maturity: production-scaffold public_release: sanitized
Yao Crux Skill
Use this skill to first clarify the user's current situation, then turn it into a principal-contradiction diagnosis, a secondary-contradiction watchlist, a focused action plan, and a four-format report bundle.
Use This Skill For
- ask concise follow-up questions before judging a user's current situation
- assess whether the user's current situation is clear enough for diagnosis before naming the principal contradiction
- produce a confirmable current-state snapshot with goal, facts, stage, resources, constraints, stakeholders, and repeated patterns
- identify goals, stage, constraints, facts, stakeholders, resources, and repeated conflict patterns
- rewrite messy symptoms as candidate contradictions in the form
力量A 与 力量B 的冲突 - run a first-principles layer scan so the principal contradiction can be an upstream, not-yet-visible constraint rather than the loudest symptom
- use the three plain principal-contradiction checks:
决定性,牵引性, and阶段性 - separate internal changeable structures from external hard conditions, then judge how external conditions act through internal structure
- use Bayesian-style evidence updates and Ockham-razor parsimony as supporting checks when candidate contradictions are close
- score principal and secondary contradictions by goal impact, causal leverage, stage urgency, resource constraint, changeability, spillover risk, and evidence strength
- identify the principal aspect inside the principal contradiction
- recommend 1-3 breakthrough actions that explicitly weaken or reverse the principal aspect, monitoring thresholds, review conditions, and probability projections after action
- make resource and attention allocation decisive when the principal contradiction is clear, typically concentrating 50%-70% of high-leverage resources on the main line
- include visual reasoning modules: analysis flow, iceberg model, contradiction decision matrix, resource allocation, and stage transition map
- write user-facing reports that explicitly use
主要矛盾and次要矛盾, while translating them with practical labels such as最关键的卡点and先不主攻,但要盯住 - export synchronized
markdown,html,docx, andpdfreports using the Kami-style layout rules in this package
Do Not Route Here
- generic explanation of
矛盾论with no concrete user case - historical, ideological, or textual commentary where no diagnosis or action report is needed
- broad brainstorming that does not require a principal/secondary contradiction conclusion
- final professional medical, legal, investment, safety-critical, or psychological-crisis advice
Default Workflow
- Read
references/intake-and-questioning.md; extract the user's target, stage, constraints, resources, facts, stakeholders, and previous attempts. - Run the current-state gate from
references/intake-and-questioning.mdorscripts/current_state_clarity.py; score clarity before diagnosis. - If clarity is
insufficient, do not name a principal contradiction. Ask no more than 3 decisive questions and stop. - If clarity is
workable, produce a provisional current-state snapshot, ask the missing questions, and label any contradiction read as provisional. - If clarity is
clear, restate the current-state snapshot and ask the user to confirm or correct it before deep diagnosis. - Run
references/safety-and-boundaries.md; hard constraints remain guardrails even when they are not the principal contradiction. - Read
references/theory-anchors.md; use决定性,牵引性, and阶段性as the plain-language front gate before detailed scoring. - Use the first-principles gate in
references/contradiction-model.md: separate visible symptoms from the hidden root variable that can explain several symptoms together. - Separate
内部可改变结构,外部硬条件, and外因通过内因起作用; do not mistake an external condition for the principal contradiction when an internal response path is available. - Build 3-7 candidate contradictions, including at least one upstream candidate if the visible symptoms share a common cause.
- Score candidates with the weighted model; use Bayesian-style updates to ask which explanation fits the evidence best.
- Apply Ockham razor only as a supporting tie-breaker: prefer the explanation that covers more symptoms with fewer extra assumptions.
- If the top contradiction is below
3.5/5or the evidence is too weak, return a provisional read and ask for the missing evidence instead of over-claiming. - Identify the principal contradiction, its principal aspect, secondary contradictions, defer reasons, monitor triggers, and review conditions.
- Tie each breakthrough action to the principal aspect: say whether it weakens the currently dominant side, strengthens the weaker side, or changes their relationship.
- Reallocate resources aggressively when evidence is sufficient: protect the main line, cap secondary contradictions, and keep only minimal stop-loss capacity for monitored risks.
- Build a canonical report input JSON using
templates/crux-report.schema.json, including visual and dynamic-stage fields when available. - Run
scripts/generate_report_bundle.py input_file.json output_dirfor synchronized Markdown, HTML, Word, PDF, and.report.jsonartifacts. - Check the bundle with
scripts/verify_report_bundle.py output_dirbefore claiming completion. - For HTML/PDF delivery, perform a visual pass on the conclusion, current-state tables, iceberg, decision matrix, and stage-transition sections. Reject the output if the content container width drifts away from the top navigation width, or if there is horizontal overflow, clipped legends, overlapping labels, empty chart space, or decorative imagery that does not explain the analysis.
Output Contract
- Lead with the conclusion: current principal contradiction, principal aspect, confidence, and first action.
- Before the conclusion, make sure the current-state snapshot is explicit enough; if not, lead with follow-up questions instead of a diagnosis.
- Default report headings must integrate the concepts and the practical translation:
主要矛盾(最关键的卡点),次要矛盾(先不主攻,但要盯住),主要矛盾判断过程. - The report must show the first-principles reasoning:
看得见的问题,上升一层,看不见的根部变量, and why the visible issue is not necessarily the principal contradiction. - The report must explain the principal contradiction through
决定性,牵引性, and阶段性before falling back to scores. - The report must separate
内部可改变结构from外部硬条件, then explain how external conditions act through internal structure. - The report must include the visual reasoning sections
一张图看懂:从表象到主要矛盾,时间、精力、资源应该怎么重新分配, and主要矛盾什么时候会转移. - HTML/PDF reports should render four inline SVG charts plus a photo-based iceberg module. The iceberg must use a real above-water/below-water iceberg image, not a flat glacier, abstract triangle, or decorative ice background. When the image is wide enough, place it as a full-width visual anchor, put
水面上and水面下explanation cards below it, and make当前主要矛盾a full-width long module. Markdown and DOCX can use readable text/table fallbacks. - Mark major facts and numbers as
observed,estimated, orassumed. - Keep the analysis dynamic: every principal contradiction conclusion needs a reversal condition and a review point.
- Treat secondary contradictions as monitored risks, not ignored problems.
- Keep action advice narrow: 1-3 actions with owner, deadline, resource, metric, and expected effect.
- Each action should name the principal aspect it changes.
- When diagnosis confidence is sufficient, resource allocation should be deliberately tilted rather than balanced: usually 50%-70% to the principal contradiction, 10%-25% to secondary-risk containment, and 10%-20% to monitoring/evidence.
- Include probability projection as a decision-support estimate, not a promise: baseline probability, expected action uplift, risk drag, scenario probabilities, and sensitivity notes.
- Reports default to Simplified Chinese and must stay synchronized across Markdown, HTML, Word, and PDF.
- The HTML/PDF layout should follow
references/kami-layout-guide.md: warm paper background, ink-blue accent, restrained hierarchy, compact tables, readable chart labels, no text overlap, and print-safe A4 rules.
Reference Map
references/intake-and-questioning.md: follow-up strategy and input contractreferences/theory-anchors.md: theory-to-rule anchors for principal contradiction, internal/external causes, principal aspect, and aggressive resource allocationreferences/contradiction-model.md: scoring model, principal aspect, secondary contradiction, and probability projection rulesreferences/report-contract.md: report sections and language standardreferences/report-export-pipeline.md: four-format generation workflow and verificationreferences/kami-layout-guide.md: Kami-derived layout rules for the report bundlereferences/safety-and-boundaries.md: high-risk and professional-boundary gatesreference-materials/README.md: downloadable background research and design materials for readerstemplates/crux-report.schema.json: canonical input/report shapescripts/generate_report_bundle.py: JSON to Markdown, HTML, DOCX, PDF, and report JSONscripts/current_state_clarity.py: current-state clarity gate and follow-up question selectorscripts/verify_report_bundle.py: generated artifact checks
Related Skills
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
design
149.0kComprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini, Atlas Cloud, or MuAPI AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
