agentleFS
MOUCHILI-techMOUCHILI-tech/miroswarm/.claude/skills/experiment-runner/SKILL.md

experiment-runner

Skill0 starsChanged 6 months agoMITView on GitHub

Use this skill when creating or modifying any experiment script, ablation study, or batch simulation run for MiroSwarm. Triggers include adding a new experiment file under experiments/, sweeping hyperparameters, running multi-seed comparisons, or producing data for the final report. Enforces reproducibility, consistent file layout, and statistical rigor.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. wangyi0403/dl-research-workflow★ 4same name
    2. raomaster/skills★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every experiment must be reproducible from git checkout + one command.

    line 8
  2. Very specific:

    Never overwrite data: If the output dir exists and is non-empty, refuse to run unless --force is passed.

    line 51
  3. Very specific:

    Print progress: Use tqdm over the seed loop so the user sees live progress.

    line 52
  4. Very specific:

    After an experiment completes, generate a paired plot under figures/<exp_name>/ showing mean ± std per condition, plus a small results …

    line 57
  5. Distinctive:

    When comparing conditions, always:

    line 63
  6. Distinctive:

    Use a non-parametric test (Mann-Whitney U) for pairwise comparisons.

    line 65
  7. Distinctive:

    Never claim "X is better than Y" without citing the test result.

    line 67
  8. Distinctive:

    If estimate > $5, ask the user before running.

    line 73

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

MiroSwarm Experiment Protocol

Every experiment must be reproducible from git checkout + one command.

Required structure for every experiment script

# experiments/<exp_name>.py

from src.simulator import Simulator
from src.config import default_config
import json, csv
from pathlib import Path
import argparse

def run(seed: int, condition: str, out_dir: Path):
    cfg = default_config()
    cfg.condition = condition  # 'hybrid' | 'gradient' | 'homogeneous' | 'no_memory'
    cfg.seed = seed
    sim = Simulator(cfg)
    metrics = sim.run()
    # write metrics to CSV
    ...

if __name__ == "__main__":
    parser = argparse.ArgumentParser()
    parser.add_argument("--seeds", type=int, default=20)
    parser.add_argument("--out", type=str, default="data/<exp_name>")
    args = parser.parse_args()
    out = Path(args.out)
    out.mkdir(parents=True, exist_ok=True)

    for condition in ["hybrid", "gradient", "homogeneous", "no_memory"]:
        for seed in range(args.seeds):
            run(seed, condition, out)

    # write meta.json with full config + git SHA + timestamp
    ...

Mandatory rules

  1. Minimum 20 seeds per condition. Statistical claims need replicates.
  2. One CSV per (condition, seed) with columns: t, mean_dist_to_source, success, connectivity, ....
  3. meta.json at the experiment root containing: full config dict, git SHA (git rev-parse HEAD), Python version, package versions (pip freeze), timestamp, command line.
  4. Never overwrite data. If the output dir exists and is non-empty, refuse to run unless --force is passed.
  5. Print progress. Use tqdm over the seed loop so the user sees live progress.
  6. Set the random seed at every level: numpy, Python random, and any LLM calls (where supported via the API's seed parameter).

Reporting results

After an experiment completes, generate a paired plot under figures/<exp_name>/ showing mean ± std per condition, plus a small results table in reports/<exp_name>.md with columns: condition, mean final-distance, success rate, mean wall-clock, n.

Statistical comparison

When comparing conditions, always:

  • Report mean ± std (not just mean).
  • Use a non-parametric test (Mann-Whitney U) for pairwise comparisons.
  • State sample size n explicitly in the figure caption.
  • Never claim "X is better than Y" without citing the test result.

LLM cost discipline

Hybrid runs cost real money. Before running a sweep:

  • Estimate cost: n_seeds × steps_per_seed × LLM_calls_per_step × cost_per_call.
  • If estimate > $5, ask the user before running.
  • Cache LLM responses by (persona, memory_hash, neighbor_summary_hash) so identical reasoning contexts don't re-bill.

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.