Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Decision tree analysis for complex decision-making across all domains. Use when user needs to evaluate multiple options with uncertain outcomes, assess risk/reward scenarios, or structure choices systematically. Applicable to business, investment, personal decisions, operations, career choices, product strategy, and any situation requiring structured evaluation. Triggers include decision tree, should I, what if, evaluate options, compare alternatives, risk analysis.
Decision tree analysis for complex decision-making across all domains. Use when user needs to evaluate multiple options with uncertain outcomes, assess risk/reward scenarios, or structure choices systematically. Applicable to business, investment, personal decisions, operations, career choices, product strategy, and any situation requiring structured evaluation. Triggers include decision tree, should I, what if, evaluate options, compare alternatives, risk analysis.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Decision tree analysis: a visual tool for making decisions with probabilities and expected value.
β Good for: Business decisions (investments, hiring, product launches) Personal choices (career, relocation, purchases) Trading & investing (position sizing, entry/exit) Operational decisions (expansion, outsourcing) Any situation with measurable consequences β Not suitable for: Decisions with true uncertainty (black swans) Fast tactical choices Purely emotional/ethical questions
Decision tree = tree-like structure where: Decision nodes (squares) β your actions Chance nodes (circles) β random events End nodes (triangles) β final outcomes Process: Define options β all possible actions Define outcomes β what can happen after each action Estimate probabilities β how likely is each outcome (0-100%) Estimate values β utility/reward for each outcome (money, points, utility units) Calculate EV β expected value = Ξ£ (probability Γ value) Choose β option with highest EV
EV = Ξ£ (probability_i Γ value_i) Example: Outcome A: 70% probability, +$100 β 0.7 Γ 100 = $70 Outcome B: 30% probability, -$50 β 0.3 Γ (-50) = -$15 EV = $70 + (-$15) = $55
Decision: Go to party or stay home?
Party: +9 utility (fun) Home: +3 utility (comfort) Carrying jacket unnecessarily: -2 utility Being cold: -10 utility Probability cold: 70% Probability warm: 30%
Decision ββ Go to party β ββ Take jacket β β ββ Cold (70%) β 9 utility (party) β β ββ Warm (30%) β 9 - 2 = 7 utility (carried unnecessarily) β β EV = 0.7 Γ 9 + 0.3 Γ 7 = 8.4 β ββ Don't take jacket β ββ Cold (70%) β 9 - 10 = -1 utility (froze) β ββ Warm (30%) β 9 utility (perfect) β EV = 0.7 Γ (-1) + 0.3 Γ 9 = 2.0 ββ Stay home ββ EV = 3.0 (always) Conclusion: Go and take jacket (EV = 8.4) > stay home (EV = 3.0) > go without jacket (EV = 2.0)
Decision: Launch new product?
Success probability: 40% Failure probability: 60% Profit if success: $500K Loss if failure: $200K Don't launch: $0
Launch product ββ Success (40%) β +$500K ββ Failure (60%) β -$200K EV = (0.4 Γ 500K) + (0.6 Γ -200K) = 200K - 120K = +$80K Don't launch ββ EV = $0 Conclusion: Launch (EV = +$80K) is better than not launching ($0).
Decision: Enter position or wait?
Probability of rise: 60% Probability of fall: 40% Position size: $1000 Target: +10% ($100 profit) Stop-loss: -5% ($50 loss)
Enter position ββ Rise (60%) β +$100 ββ Fall (40%) β -$50 EV = (0.6 Γ 100) + (0.4 Γ -50) = 60 - 20 = +$40 Wait ββ No position β $0 EV = $0 Conclusion: Entering position has positive EV (+$40), better than waiting ($0).
β οΈ Critical points: Subjective estimates β probabilities often "finger in the air" Doesn't account for risk appetite β ignores psychology (loss aversion) Simplified model β reality is more complex Unstable β small data changes can drastically alter the tree May be inaccurate β other methods exist that are more precise (random forests) But: The method is valuable for structuring thinking, even if numbers are approximate.
Ask: What are the action options? What are possible outcomes? What are values/utility for each outcome? How do we measure value? (money, utility units, happiness points)
Help estimate through: Historical data (if available) Comparable situations Expert judgment (user experience) Subjective assessment (if no data)
Draw tree in markdown: Decision ββ Option A β ββ Outcome A1 (X%) β Value Y β ββ Outcome A2 (Z%) β Value W ββ Option B ββ Outcome B1 (100%) β Value V
For each option: EV_A = (X% Γ Y) + (Z% Γ W) EV_B = V
Option with highest EV = best choice (rationally). But add context: Risk tolerance (can user handle worst case) Time horizon (when is result needed) Other factors (reputational risk, emotions, ethics)
Position Sizing: Options: 5%, 10%, 20% of capital Outcomes: Profit/loss with different probabilities Value: Absolute profit in $ Entry Timing: Options: Enter now, wait for -5%, wait for -10% Outcomes: Price goes up/down Value: Opportunity cost vs better entry price
Product Launch: Options: Launch / don't launch Outcomes: Success / failure Value: Revenue, market share, costs Hiring Decision: Options: Hire candidate A / candidate B / don't hire Outcomes: Successful onboarding / quit after X months Value: Productivity, costs, opportunity cost
Career Change: Options: Stay / change job / start business Outcomes: Success / failure in new role Value: Salary, satisfaction, growth, risk Real Estate: Options: Buy house A / house B / continue renting Outcomes: Price increase / decrease / personal situation changes Value: Net worth, monthly costs, quality of life
Capacity Planning: Options: Expand production / outsource / status quo Outcomes: Demand increases / decreases Value: Profit, utilization, fixed costs Vendor Selection: Options: Vendor A / Vendor B / in-house Outcomes: Quality, reliability, failures Value: Total cost of ownership
Use scripts/decision_tree.py for automated EV calculations: python3 scripts/decision_tree.py --interactive Or via JSON: python3 scripts/decision_tree.py --json tree.json JSON format: { "decision": "Launch product?", "options": [ { "name": "Launch", "outcomes": [ {"name": "Success", "probability": 0.4, "value": 500000}, {"name": "Failure", "probability": 0.6, "value": -200000} ] }, { "name": "Don't launch", "outcomes": [ {"name": "Status quo", "probability": 1.0, "value": 0} ] } ] } Output: π Decision Tree Analysis Decision: Launch product? Option 1: Launch ββ EV = $80,000.00 ββ Success (40.0%) β +$500,000.00 ββ Failure (60.0%) β -$200,000.00 Option 2: Don't launch ββ EV = $0.00 ββ Status quo (100.0%) β $0.00 β Recommendation: Launch (EV: $80,000.00)
Before giving recommendation, ensure: β All options covered β Probabilities sum to 100% for each branch β Values are realistic (not fantasies) β Worst case scenario is clear to user β Risk/reward ratio is explicit β Method limitations mentioned β Qualitative context added (not just EV)
β Simple β people understand trees intuitively β Visual β clear structure β Works with little data β can use expert estimates β White box β transparent logic β Worst/best case β extreme scenarios visible β Multiple decision-makers β can account for different interests
β Unstable β small data changes β large tree changes β Inaccurate β often more precise methods exist β Subjective β probability estimates "from the head" β Complex β becomes unwieldy with many outcomes β Doesn't account for risk preference β assumes risk neutrality
The method is valuable for structuring thinking, but numbers are often taken from thin air. What matters more is the process β forcing yourself to think through all branches and explicitly evaluate consequences. Don't sell the decision as "scientifically proven" β it's just a framework for conscious choice.
Decision trees in operations research Influence diagrams (more compact for complex decisions) Utility functions (accounting for risk aversion) Monte Carlo simulation (for greater accuracy) Real options analysis (for strategic decisions)
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.