OpenRaiser/NanoResearch / skills/nanoresearch-experiment
nanoresearch-experiment
VerifiedGenerate a Python code skeleton from an experiment blueprint
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.7 KB |
SKILL.md
View on GitHub---
name: nanoresearch-experiment
description: Generate a Python code skeleton from an experiment blueprint
version: 0.1.0
---
# 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
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |