skills/expected-value/SKILL.md
Calculates probability-weighted averages of all possible outcomes to enable rational decisions under uncertainty. Covers scenario identification, probability estimation, payoff quantification, and risk-adjusted interpretation. Use when comparing risky options (investments, product bets, strategic choices), prioritizing projects by expected return, assessing whether to take a gamble, or when user mentions expected value, EV calculation, risk-adjusted return, probability-weighted outcomes, or decision tree.
npx skillsauth add lyndonkl/claude expected-valueInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
EV = Σ (Probability of outcome x Value of outcome)
EV = (p₁ × v₁) + (p₂ × v₂) + ... + (pₙ × vₙ)
where probabilities must sum to 1.0
Example: Launch feature with 60% chance of $100k revenue, 40% chance of -$20k sunk cost. EV = (0.6 x $100k) + (0.4 x -$20k) = $60k - $8k = $52k (positive EV, rational to launch if risk tolerance allows)
Copy this checklist and track your progress:
Expected Value Analysis Progress:
- [ ] Step 1: Define decision and alternatives
- [ ] Step 2: Identify possible outcomes
- [ ] Step 3: Estimate probabilities
- [ ] Step 4: Estimate payoffs (values)
- [ ] Step 5: Calculate expected values
- [ ] Step 6: Interpret and adjust for risk preferences
Step 1: Define decision and alternatives
What decision are you making? What are the mutually exclusive options? See resources/template.md.
Step 2: Identify possible outcomes
For each alternative, what could happen? List scenarios from best case to worst case. See resources/template.md.
Step 3: Estimate probabilities
What's the probability of each outcome? Use base rates, reference classes, expert judgment, data. See resources/methodology.md.
Step 4: Estimate payoffs (values)
What's the value (gain or loss) of each outcome? Quantify in dollars, time, utility. See resources/methodology.md.
Step 5: Calculate expected values
Multiply probabilities by payoffs, sum across outcomes for each alternative. See resources/template.md.
Step 6: Interpret and adjust for risk preferences
Choose option with highest EV? Or adjust for risk aversion, non-monetary factors, strategic value. See resources/methodology.md.
Validate using resources/evaluators/rubric_expected_value.json. Minimum standard: Average score ≥ 3.5.
Pattern 1: Investment Decision (Discrete Outcomes)
Pattern 2: Portfolio Allocation (Multiple Options)
Pattern 3: Sequential Decision (Decision Tree)
Pattern 4: Continuous Distribution (Monte Carlo)
Pattern 5: Competitive Game (Payoff Matrix)
Probabilities should sum to 1.0: Listed outcomes need to be exhaustive (cover all possibilities) and mutually exclusive (no overlap). Verify: p1 + p2 + ... + pn = 1.0.
Adjust for risk on one-shot, high-stakes decisions: EV is a long-run average. For rare, irreversible decisions, factor in risk aversion. A 1% chance of $1B (EV = $10M) does not mean betting the house is rational.
Quantify uncertainty, don't hide it: Probabilities and payoffs are estimates. Use ranges, sensitivity analysis, or distributions rather than pretending false precision.
Consider non-monetary value: Some outcomes have utility not captured by money (reputation, learning, optionality, morale). Convert to a common scale or use multi-attribute utility.
Ground probabilities in data: Use base rates, reference classes, data, and expert forecasts rather than gut feel. Check calibration: are "70% confident" predictions right 70% of the time?
Account for correlated outcomes: If outcomes are not independent (e.g., economic downturn affects all portfolio companies), correlation reduces diversification benefit.
Time value of money: Discount future cash flows to present value. EV should use NPV, not nominal values.
Consider option value: In sequential decisions, fold-back induction finds optimal strategy. Factor in the option to stop early, pivot, or wait for more information.
Common pitfalls:
Key formulas:
Expected Value: EV = Σ (pᵢ × vᵢ) where p = probability, v = value
Expected Utility (for risk aversion): EU = Σ (pᵢ × U(vᵢ)) where U = utility function
Net Present Value: NPV = Σ (CF_t / (1+r)^t) where CF = cash flow, r = discount rate, t = time period
Variance (risk measure): Var = Σ (pᵢ × (vᵢ - EV)²)
Standard Deviation: σ = √Var
Coefficient of Variation (risk/return ratio): CV = σ / EV (lower = better risk-adjusted return)
Breakeven probability: p* where EV = 0. Solve: p* × v_success + (1-p*) × v_failure = 0.
Decision rules:
Sensitivity analysis questions:
Key resources:
Inputs required:
Outputs produced:
expected-value-analysis.md: Decision framing, outcome scenarios with probabilities and payoffs, EV calculations, sensitivity analysis, recommendation with risk considerationstesting
Cluster a conference's event records into a small set of coarse themes with finer sub-clusters, an explicit outlier bucket, and soft (multi-membership) affinities — using the hybrid embed-then-label pipeline (embed abstracts, reduce, density-cluster, then LLM-label the clusters) when embedding libraries are available, and an LLM-reasoned hierarchical fallback when they are not. Embeddings do the grouping; the LLM only names the groups. Conference-agnostic. Use when turning structured event records into a navigable theme map for preference elicitation and scheduling, when you need 6-8 reasonable themes rather than 20 muddy ones, or when overlapping talks must belong to more than one theme. Trigger keywords - theme clustering, cluster talks, embed then label, soft membership, outlier talks, conference themes, topic map.
development
Build a personal conference schedule as a constraint-optimization problem — hard constraints (no time overlap, room-to-room travel time, capacity/registration, the attendee's own must-attends and blackouts) plus a user-owned weighted objective trading interest against breadth, pacing (maximize contiguous free time), and serendipity. Surfaces unbreakable conflicts (two high-value overlapping talks the model cannot rank) as decisions for the human rather than silently picking, and reports what each choice traded away. Conference-agnostic. Use to turn a preference profile plus a theme map into a day-by-day plan, to resolve overlapping sessions, or to balance a packed vs paced schedule. Trigger keywords - schedule optimization, conference schedule, constraint optimization, overlapping talks, contiguous free time, conflict surfacing, packed vs paced.
development
Parse a heterogeneous conference program (markdown, HTML, PDF-derived text, or JSON) into normalized event records with per-field confidence scores and independent classification axes (topic, depth, format, prerequisites, recorded, capacity). Detects the program's format before extracting, treats every inferred field as uncertain (present vs inferred vs missing), and flags thin or missing abstracts so downstream enrichment can target them. Conference-agnostic. Use when ingesting a conference or event schedule into a structured store, normalizing a talk/session list, or extracting per-session metadata with calibrated confidence. Trigger keywords - program ingestion, parse schedule, session extraction, event records, conference program, talk metadata, per-field confidence.
development
Build a personalized preference profile from a small number of well-chosen, cluster-grounded questions instead of a long survey. Represents the person's interests as an uncertainty region over the theme map, picks the single highest-information-gain choice-based question (contrasting real talks from different clusters), balances exploiting known interests against exploring uncertain ones, deliberately injects outlier probes to fight selection bias, and stops as soon as the schedule would be stable. Also elicits the user-owned objective weights and hard constraints. Interactive — runs where it can actually ask the person. Conference-agnostic. Use to turn a theme map into a preference profile, to decide what to ask a conference attendee, or to elicit scheduling priorities. Trigger keywords - preference elicitation, ask few questions, information gain, choice-based questions, selection bias probe, objective weights, attendee preferences.