agentleFS
OpenRaiserOpenRaiser/NanoResearch/skills/nanoresearch-experiment/SKILL.md

nanoresearch-experiment

Skill1.3k starsChanged 8 months agoMITView on GitHub

Generate a Python code skeleton from an experiment blueprint

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:

    Create configuration files for each ablation group

    line 25
  2. Distinctive:

    Add a main entry point that accepts a config and runs the full train-evaluate pipeline

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

Experiment Skill

Purpose

Take the experiment blueprint and produce a runnable Python code skeleton that implements the proposed method, baselines, training loops, evaluation harness, and ablation configurations.

Tools Required

None. This skill operates entirely through LLM code generation based on the experiment blueprint.

Input

  • experiment_blueprint: Path to papers/experiment_blueprint.json produced by the planning skill

Process

  1. Parse the experiment blueprint for datasets, baselines, metrics, and ablation groups
  2. Generate the project directory structure (data loaders, models, training, evaluation, configs)
  3. Produce data loading and preprocessing code for each specified dataset
  4. Implement model architecture stubs for the proposed method and each baseline
  5. Generate training loop with logging, checkpointing, and early stopping
  6. Implement the evaluation harness computing all specified metrics
  7. Create configuration files for each ablation group
  8. Add a main entry point that accepts a config and runs the full train-evaluate pipeline

Output

Produces experiments/ directory containing:

  • data/: Data loading and preprocessing modules
  • models/: Model architecture implementations (proposed method and baselines)
  • training/: Training loop and optimization utilities
  • evaluation/: Metric computation and result aggregation
  • configs/: YAML configuration files for each experiment and ablation variant
  • run.py: Main entry point for launching experiments
  • requirements.txt: Python dependencies

Download now (ZIP)

Trending

More talk lately.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 1 mentionMay 2026: 1 mentionJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 1 mentionOct 2026: 3 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the OpenRaiser/NanoResearch repository that our weekly crawl found: only 6 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Who's talking about OpenRaiser/NanoResearch

The biggest 5 of 6 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 6

Talked about on GitHub (6 times).

On GitHub · 6

1 more on GitHub

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

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.