agentleFS
imran-sayed-proimran-sayed-pro/claude-skills/expected-value-calculator/SKILL.md

expected-value-calculator

Skill0 starsChanged 4 months agoMITView on GitHub

Use this skill whenever a user needs help choosing between options or making a decision. Triggers include: "help me decide between X and Y", "help me make a decision from the following options", "should I choose X or Y", "which option should I pick", "help me decide", "I can't decide between", or any scenario where someone presents 2 or more choices and wants a structured recommendation. Use this skill even when the user does not explicitly say "expected value" - if they are facing a decision with multiple options, this skill applies. Works for financial decisions, career choices, product bets, medical decisions, negotiations, and everyday tradeoffs.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Only ask a clarifying question if a key input is completely unknown and would substantially change the answer.

    line 33
  2. Distinctive:

    Use consistent units across all options: dollars for financial decisions, or a 1-10 utility scale for life/career decisions.

    line 46
  3. Distinctive:

    Always use this exact structure:

    line 53
  4. Distinctive:

    Use honest probabilities, not optimistic ones

    line 91
  5. Distinctive:

    If EV difference between options is small (less than 10%), note it and weight qualitative judgment more heavily

    line 93
  6. Distinctive:

    Never fake precision; round numbers and flag uncertain estimates

    line 94
  7. Distinctive:

    Only one option presented: Reframe as "take it vs.

    line 100
  8. Distinctive:

    All options have negative EV: Say so plainly and invoke Naval's Rule - the answer is no

    line 105

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Expected Value Decision Calculator

A structured framework for evaluating decisions under uncertainty using expected value (EV) analysis. Combines quantitative rigor with qualitative judgment to produce a clear, decisive recommendation.


Step 1: Understand the Decision

Extract from the user message:

  1. The core decision: What is being decided? (one sentence)
  2. The options: List all options explicitly - at minimum 2, often 3+
  3. The stakes: What does the person stand to gain or lose?
  4. Context: Any constraints or values that should rule options in or out?

Make reasonable assumptions for missing pieces, state them clearly, and proceed. Only ask a clarifying question if a key input is completely unknown and would substantially change the answer.


Step 2: Structure the EV Analysis

For each option:

  • Identify the best case outcome (perfect execution, everything works)
  • Identify the worst case outcome (complete failure)
  • Estimate probability of success honestly - use base rates, not optimism
  • Calculate: EV = (best case value x P(success)) + (worst case value x P(failure))

Use consistent units across all options: dollars for financial decisions, or a 1-10 utility scale for life/career decisions.


Step 3: Deliver the Output

Always use this exact structure:

Decision: [WHAT YOU ARE DECIDING - one crisp sentence]

Options:

  1. [OPTION A]
  2. [OPTION B]
  3. [OPTION C - add more if needed]

For each option, present this block:

Option [N]: [Name]

  • Best case outcome: What happens if it works perfectly?
  • Worst case outcome: What happens if it fails completely?
  • Probability of success: State the % and briefly justify it. Be honest, not optimistic.
  • Expected Value: (best case value x probability of success) + (worst case value x probability of failure) = EV

Repeat for every option.

Then present the EV Summary Table with columns: Option | Best Case | Worst Case | P(Success) | Expected Value

Then apply Naval's Rule: Naval's Rule: "If you can't decide, the answer is no." Is any option a clear yes? If the highest-EV option still feels uncertain or marginal, say so explicitly and name what is blocking clarity.

Then give the Verdict: State which option has the highest EV - or whether all options should be rejected. One short decisive paragraph. If rejecting all options, explain why and suggest what a better alternative might look like.


Tone and Style

  • Be direct and confident
  • Show the math explicitly - never skip the EV calculation
  • Use honest probabilities, not optimistic ones
  • Plain language unless the user uses jargon
  • If EV difference between options is small (less than 10%), note it and weight qualitative judgment more heavily
  • Never fake precision; round numbers and flag uncertain estimates

Edge Cases

  • Only one option presented: Reframe as "take it vs. reject it / status quo"
  • Purely emotional decision: Still run the EV, but note that qualitative factors dominate
  • Irreversible decisions: Flag this and apply extra weight to the worst case
  • Repeated decisions (a recurring bet): Use cumulative EV logic
  • Missing probabilities: Use base rates from analogous situations and state the assumption clearly
  • All options have negative EV: Say so plainly and invoke Naval's Rule - the answer is no

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.