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

experimentation

Skill10 starsChanged 6 days agoMITView on GitHub

When thinking cannot settle something, run a small, cheap, reversible test, learn from the result, and adjust. Use when a question stays open after thinking it through, or on /experimentation.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 5

    Distinctive

    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 thinking cannot settle something, run a small, cheap, reversible test, learn from the result, and adjust.

    line 13
  2. Distinctive:

    Learn from the test on purpose: Before the test, define what you are trying to learn: state what result would change your decision and when …

    line 23
  3. Distinctive:

    Optional extension: when fear blocks action: When fear rather than missing information is blocking action, make the feared outcome …

    line 28
  4. Distinctive:

    Do not test when existing knowledge can settle the question or there is no time to learn from the result.

    line 36
  5. Distinctive:

    Do not transfer experimental risk to others without their knowledge and agreement.

    line 38

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “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

/experimentation

When thinking cannot settle something, run a small, cheap, reversible test, learn from the result, and adjust.

Principles

  1. Keep the test small, cheap, and reversible, so a wrong guess costs little and leaves room for the next test. Make it easy to stop or undo, and risk only what you can afford to lose. Start with the smallest test that could teach something, and try several paths cheaply instead of making one large bet.
  2. Learn from the test on purpose. Before the test, define what you are trying to learn: state what result would change your decision and when you will stop. After the test, let the evidence change your next action, including when the result is inconclusive.

Optional extension: when fear blocks action. When fear rather than missing information is blocking action, make the feared outcome concrete: what could go wrong, how could you prevent it, and how could you recover? Then choose a bounded first step. Research is the right move when missing information is the real blocker. A useful check is whether additional thinking can realistically resolve the uncertainty; if not, try a bounded experiment.

Boundaries.

  • Do not test when existing knowledge can settle the question or there is no time to learn from the result.
  • Do not transfer experimental risk to others without their knowledge and agreement; keep unavoidable risk small and let them decline.

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.