agentleFS
Sign inStart free
freemtyfreemty/labmate/skills/analyze-experiment/SKILL.md

analyze-experiment

Skill25 starsChanged 2 months agoMITView on GitHub

Use when an experiment has completed and its results need interpretation, comparison, or durable findings. Triggers on "analyze results", "分析实验", "interpret experiment", "what did exp find", "run analysis".

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read pipeline state, the experiment README/config, result files, and any existing summary.

    line 12
  2. Distinctive:

    Run the experiment's analysis script when present.

    line 14
  3. Very specific:

    Follow ../../references/agent-routing.md for the domain-expert role.

    line 16

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

Analyze Experiment

Separate measurement from interpretation. Preserve raw outputs; write claims only at the level supported by the experiment contract.

  1. Read pipeline state, the experiment README/config, result files, and any existing summary.
  2. Run the experiment's analysis script when present. Treat output as measurement, not explanation.
  3. Follow ../../references/agent-routing.md for the domain-expert role. Provide hypothesis, baseline, metrics, seeds, exclusions, and results. Require labels for evidence, inference, and unresolved questions.
  4. Merge reviewed interpretation into the experiment README and exp/summary.md; update pipeline state to analysis.
  5. Report the quantitative result, causal interpretation, limitations, and next discriminating experiment.

Generate slides only when requested. Route research talks through research-slides so its default Speculative Decoding reference profile and rendered QA apply.

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.

Check your setup, free