About pytorch-training-recipe
A skill for turning research ideas into staged PyTorch training recipes, aimed at researchers and practitioners who need checks before scaling experiments. It emphasizes data validation, reproducibility, and small-run verification.
Key features
- 01Experiment and data-pipeline planning
- 02Model and optimization choices
- 03First-run safety checks
- 04Metrics and failure-mode review
- 05Logging and checkpoint planning
- 06Staged scale-up plan
Use cases
- 01Designing a training experiment from a research idea
- 02Checking data splits for leakage
- 03Verifying a model with a tiny-batch run
- 04Preparing reproducible experiment records
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ jurgendn/ agent-skills --skill pytorch-training-recipeAfter installing, type/pytorch-training-recipein Claude Code to confirm it loaded.
Bundled filesreferences/training-recipe-details.md
Details
From the project READMEPyTorch Training Recipe
Translate a research idea into a training setup that can fail loudly, debug quickly, and scale only after correctness is verified.
For concrete implementation checklists and templates, read
references/training-recipe-details.md when needed.
Intake
Specify:
- task, dataset, and split protocol;
- model family and input/target format;
- loss and metrics;
- baseline or reproduction target;
- hardware/compute budget;
- framework preference: raw PyTorch or Lightning.
Workflow
- Define the experiment and claim it supports.
- Define the data pipeline, including leakage checks.
- Choose the simplest training stack that supports the experiment.
- Set optimization choices: optimizer, schedule, batch size, precision, clipping.
- Add first-run safety checks.
- Define metrics and error slices.
- Define logging, checkpoints, seeds, and config recording.
- Flag likely failure modes.
- Recommend a staged rollout from tiny sanity run to full experiment.
Non-Negotiable Checks
- Run a shape/dtype/device check.
- Verify loss is finite at initialization.
- Overfit a tiny batch.
- Run one deterministic seed twice if reproducibility matters.
- Compare against a simple baseline before scaling.
- Save config, commit, seed, and command with each run.
Rules
- Do not start with distributed training.
- Do not tune hyperparameters before the tiny-batch check passes.
- Do not trust a metric until its implementation is checked.
- Keep the first runnable version boring.
Output
Return:
- training recipe;
- data pipeline;
- model/loss/optimizer choices;
- minimal config;
- first-run checks;
- logging/checkpointing plan;
- likely failure modes;
- scale-up plan.
Comments
Markdown supported