agentleFS
shangyiyshangyiy/life-kit/skills/core/optionality/SKILL.md

optionality

Skill10 starsChanged 6 days agoMITView on GitHub

Find the real choices you have and judge what each is worth. Use when weighing a decision, path, or offer, especially one that seems to have only one way out, or on /optionality.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    When waiting provides useful information before an irreversible commitment, while the downside remains bounded and the upside remains …

    line 43
  2. Distinctive:

    Boundaries: Only the person deciding can judge what loss they could bear.

    line 69

≈ “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

/optionality

Find the real choices you have and judge what each is worth.

People often accept a path because they think it is the only one. The five principles say what a choice is and what gives it worth; the paragraphs after them say how to put them to use.

Principles

  1. A choice is a right, not a duty. It gives you the ability to take a path without requiring you to take it. Its value is the difference it makes compared with not having it, including the other choices it preserves or closes. Once exercised, it becomes a commitment to that path and its consequences.
  2. The downside must be bounded. Count two costs apart. Keeping a choice open costs money, time, attention, and what you give up by not committing elsewhere; sometimes keeping it pays you instead, as a job with a salary does. Exercising it costs whatever you cannot get back once you act. An apparent option is not truly optional if exercising it locks you into obligations or future losses you cannot bear. Sunk costs may make walking away harder psychologically, but only unavoidable future costs and commitments should affect the forward decision.
  3. The ceiling is the upside you can realistically capture. It depends on how often and how much good opportunities arise, and on whether you can reach, recognize, qualify for, and act on them. Keep the size of an opportunity apart from your ability to capture it: a huge upside with no plausible path to it means nothing. Skills, capital, credentials, relationships, and access raise the ceiling and build up over time, so the same path can be worth much more later. You can improve your odds, not control the outcome.
  4. The value of keeping a choice open can increase under uncertainty. When waiting provides useful information before an irreversible commitment, while the downside remains bounded and the upside remains reachable, preserving the choice can be worth more than committing now. Uncertainty alone does not make a path valuable.
  5. Time both feeds and drains a choice. Waiting can add information, skills, and resources that make a choice more valuable. But opportunities can expire, access can disappear, and the cost of keeping a choice open can grow. Compare what waiting may add with what it may consume; when the choice loses value faster than you learn or prepare, act or let it go before the window closes. Holding a choice is not by itself a reason to use it.

How to apply. Scale the depth of analysis to the stakes: use a lightweight check of cost and reversibility for small choices, and reserve scenarios (a bad, a typical, and a good outcome with rough odds) for decisions with material downside or significant upside. Find what is already open, including walking away. Doing nothing, waiting, and keeping the current state are choices too, but they are not free: windows and offers expire. Count only real choices: one that has been checked and is available, will still be there if the trouble that would make you need it happens, and is one you would use in some outcome you can picture. Mark any fact not yet checked as unknown, and do not count a choice that rests on one until it is checked. Then ask, for each path, what you could still do after taking it: wait, stop partway, expand, or switch. Build a missing choice with a limited first commitment. An average alone is not enough: consider whether plausible downside scenarios are survivable, not just whether the expected outcome looks attractive.

Boundaries. Only the person deciding can judge what loss they could bear; lay out the trade-off and do not decide it for them.

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.