expect-loss — quality + safety report

In the Skillier index (local__expect-loss) · scanned 2026-06-03 · engine: builtin+triage

A
Quality
96/100
Safety

✓ Clean — no heuristic safety flags surfaced.

Heuristic flags from the builtin scanner, which is known to over-flag (it trips on legitimate env-reading integrations, security skills, and library .eval calls). This is NOT an authoritative malicious verdict — re-scan with SkillSpector for the authoritative result. Run the authoritative scan →

Skillproof quality grade A

📇 This skill is in the Skillier index (curated · deduped · quality-filtered). Install Skillier to route & load it into your AI client.

Quality notes

No example
low · quality · body
→ Add at least one worked example (input → expected action/output).
Ambiguous/hedging language (×4)
low · quality · body
→ Replace hedges with direct imperatives ('Do X', 'Never Y').

About this skill

Force a brutal pre-commitment reframe whenever the user is staring at a founder go/no-go, a VC pitch prep, a moonshot launch, a career-bet decision, or any unprecedented venture where they keep asking "what are our odds?" Trigger eagerly on phrases like "what's our chance of success", "investors…

📄 Read the SKILL.md
---
name: expect-loss
description: Force a brutal pre-commitment reframe whenever the user is staring at a founder go/no-go, a VC pitch prep, a moonshot launch, a career-bet decision, or any unprecedented venture where they keep asking "what are our odds?" Trigger eagerly on phrases like "what's our chance of success", "investors will ask about market size", "is the risk-adjusted return good", "what if it fails", "we need to prove we'll win", "should I quit to do this", "convince me the math works", "what's the probability we make it", "everyone says it's crazy", or any pitch deck that opens with "why we will succeed". Also fires when a founder is hunting for permission, when a deck is engineering false confidence, when a roadmap presumes success as the base case, or when an advisor is rank-ordering opportunities by risk-adjusted ROI. The reframe: assume loss as the base case, then decide based on whether the mission matters enough to do anyway. Trigger eagerly even when the user does not name Musk or the framework.
stacks_with:
  - eat-glass-stare-into-abyss
  - probabilistic-fatalism
---

# Expect Loss

> "When something is important enough, you do it even if the odds are not in your favor."
> — Elon Musk, *The Book of Elon* (Chapter: I Expected to Lose Everything)

## What this skill captures

Musk started SpaceX and Tesla each expecting less than 10 percent odds of success — "Maybe 1 percent, I don't know. Frankly, I wasn't wrong." He did not pick space because it had the best risk-adjusted return; he says rockets and cars "would be the dumbest things you could possibly do" on that basis. He picked them because they were important to fix and nobody else was crazy enough to try. When friends warned "you're going to lose the money you invest," he replied: "Well, that was my expectation anyway, so I don't really mind!"

This skill kills the "convince me we'll win" loop. It forces the user to pre-accept loss as the base case, then decide on importance — not expected value. The value: you stop building elaborate fictions of probable success, stop hunting for permission, and stop letting risk-adjusted-ROI math veto missions that matter. You either care enough to do it anyway, or you don't. That clarity is the whole point.

## When to use this skill

- Founder is doing go/no-go on starting a company that has never been done before.
- VC pitch prep where the deck is engineering false confidence about market certainty.
- Career pivot — quitting a safe job for an unproven bet.
- Anyone asking "what's our probability of success?" as if a number changes whether the work matters.
- Advisor or board pressuring a founder to abandon a moonshot because the risk-adjusted return is bad.
- Any plan whose base case is "we succeed" with no honest "and if we lose everything, was it still worth doing?" answer.

## The how-to

1. **State the real odds out loud — and assume loss is the base case.**
   > "When I started them, I guessed both SpaceX and Tesla each had a probability of less than 10 percent to succeed."
   > — *The Book of Elon*
   Stop hiding behind optimistic forecasts. Name a number under 10 percent if the venture is unprecedented. If you cannot live with that number, do not start.

2. **Throw out risk-adjusted ROI as the decision criterion.**
   > "If one were to do a risk-adjusted rate of return estimate on opportunities, building rockets and building cars would be pretty close to the bottom of the list. They would be the dumbest things you could possibly do."
   > — *The Book of Elon*
   The whole point of an unprecedented venture is that the spreadsheet says no. If the spreadsheet decides, the mission dies before it starts.

3. **Pre-commit to the loss before you commit to the work.**
   > "Their premise for talking me out of it was, 'You're going to lose the money you invest.' I replied, 'Well, that was my expectation anyway, so I don't really mind!'"
   > — *The Book of Elon*
   Write down: "I expect to lose [the money / the years / the reputation]. I am doing this anyway because ___." If the "because" is weak, you are not ready.

4. **Decide on importance, not on probability.**
   > "I don't look at ideas and ask, 'What is the rank-ordered list of best business opportunities from a financial standpoint?' I look for problems that are important to fix for people now and for the future to be good."
   > — *The Book of Elon*
   Importance is the input. Probability is irrelevant once you have accepted the loss.

5. **A small chance beats no chance — but only when the mission requires the attempt.**
   > "A small chance of success is better than no chance of success. So I started SpaceX in mid-2002, expecting to fail."
   > — *The Book of Elon*
   The justification is not "we'll probably win." It is "if nobody attempts this, it does not happen at all."

6. **Refuse to be miserable about the odds you just accepted.**
   > "My theory is you'd rather be optimistic and wrong about the future than pessimistic and right. If you're pessimistic, you're going to be miserable. Might as well enjoy the journey."
   > — *The Book of Elon*
   Expected loss is the cold input. Operational optimism is the daily fuel. Hold both.

7. **If you would not risk your own money, do not ask investors to risk theirs.**
   > "Don't ask investors to invest their money if you're not prepared to invest your money. It doesn't seem right to me to ask other people to invest if you don't also invest. I'd rather lose my money than any of my friends' money or investors' money."
   > — *The Book of Elon*
   The honesty test: are you putting your own capital, years, and reputation on the line first? If not, you have not actually accepted the loss — you have outsourced it.

## Common failure modes

- **Engineering false confidence in the pitch.** Decks that promise high probability of success on unprecedented bets are lying. Investors who fall for them are the wrong investors. Tell the truth about the odds and let the mission do the selling.
- **Letting risk-adjusted ROI veto the mission.** "The math doesn't pencil" is not a reason to abandon something important — it is the definition of an unprecedented venture. Musk: "They would be the dumbest things you could possibly do."
- **Hunting for permission.** Asking ten friends whether you should start the company is a stalling tactic. Musk's friends made him watch a reel of rocket failures. He started anyway.
- **Pretending you are not betting everything.** If the honest base case is loss, say so — to yourself, to your spouse, to your investors. Hidden assumptions of success poison every later decision.
- **Confusing pessimism about odds with pessimism about effort.** Expect loss on the outcome. Run hot on the work. The two are not in conflict.

## When NOT to use this skill

- The venture has clear precedent, a known market, and a working playbook — pretending the odds are 10 percent is theater, not honesty.
- Decisions where failure is catastrophic and irreversible for others (life-safety hardware, fiduciary duty over client funds). Expected-loss reframing is for *your own* capital, time, and reputation — not for risks you are silently transferring to people who did not consent.
- Routine product iteration inside an established company. The skill is for unprecedented commitments, not for shipping the next feature.
- When the user has already committed and is now executing. At that point the question is "how do we win?", not "should we have tried?"

## Source

The Book of Elon by Eric Jorgenson (2026, Scribe Media). Chapter: "I Expected to Lose Everything" (in "Building SpaceX").
Scan or optimize your own skill →

Want a live grade + an embeddable README badge? Run your skill through the free scanner.

Graded independently by Skillproof — nothing to sell the author. Quality is mechanical + corpus-grounded; safety flags are heuristic (builtin+triage), not a malicious verdict.