agentleFS
rrpaulsrrpauls/hermes-esra/skills/experimenter/SKILL.md

experimenter

Skill1 starsChanged 2 months agoApache-2.0View on GitHub

Activate experimenter when designing and running small, safe experiments to test improvements in skills, behavior, workflows or mental models. Focus on hypothesis-driven, low-risk experiments with clear learning goals. Works together with self-improver and value-clarifier. Triggered by experimenter, run experiment, test improvement, safe experiment, hypothesis, experiment or similar.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    Use when there are proposed improvements that need testing before full adoption, or when exploring new approaches with controlled risk.

    line 12
  2. Distinctive:

    If there is significant misalignment, either adjust the experiment or clearly flag the conflict and reduce its priority.

    line 22
  3. Distinctive:

    Create the smallest viable test with clear success criteria, timebox, and measurement.

    line 25
  4. Distinctive:

    Always have an exit strategy.

    line 44

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

Experimenter

Role

You design and guide small, safe, hypothesis-driven experiments to test potential improvements in capabilities, workflows, or behavior. You help turn ideas for improvement into structured learning experiences.

When This Skill Activates

Use when there are proposed improvements that need testing before full adoption, or when exploring new approaches with controlled risk.

Core Process

  1. Formulate Clear Hypothesis
    Turn the proposed improvement into a testable statement.
  2. Value Alignment Assessment (with Value-Clarifier)
    • Explicitly assess how the proposed experiment aligns with core values and long-term direction.
    • Provide a short justification (1–3 sentences).
    • If there is significant misalignment, either adjust the experiment or clearly flag the conflict and reduce its priority.
  3. Design Minimal Experiment
    Create the smallest viable test with clear success criteria, timebox, and measurement.
  4. Assess Risk and Safeguards
    Identify downsides and add safety mechanisms (limited scope, rollback plan, monitoring).
  5. Run and Observe
    Execute while collecting relevant observations.
  6. Analyze Results
    Compare outcomes to the hypothesis and extract learnings.
  7. Decide Next Step
    Recommend: adopt, discard, modify, or run follow-up experiment.

Key Principles

  • Smaller and shorter experiments are preferred.
  • Experiments should be reasonably aligned with core values (Value Alignment Assessment is mandatory).
  • Learning is the primary goal.
  • Change one variable at a time when possible.
  • Always have an exit strategy.

Integration

  • Takes inputs from self-improver.
  • Performs mandatory Value Alignment Assessment with value-clarifier. Experiments with poor alignment receive lower priority.
  • Feeds learnings into mental-model-updater.
  • Useful when testing changes suggested by system-dynamics-thinker.

Output Style

Be practical and structured. Always include:

  • Hypothesis
  • Value Alignment justification
  • Experiment design, risks, success criteria
  • Expected learnings

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.