Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
lllllllama avatar

Run Train

  • 405 installs
  • 513 repo stars
  • Updated July 26, 2026
  • lllllllama/ai-paper-reproduction-skill

This is a copy of run-train by lllllllama - installs and ranking accrue to the original listing.

run-train is a Rigor Train agent skill that executes selected deep-learning training commands and writes standardized train_outputs/ evidence for developers reproducing published ML experiments with configs, seeds, and c

About

run-train is the Rigor Train agent skill in lllllllama/ai-paper-reproduction-skill that executes a pre-selected training command conservatively and normalizes resulting evidence into train_outputs/. It supports startup verification, short-run verification, full training kickoff, and resume modes while recording commands, configs, seeds, logs, checkpoints, status, and metrics. The skill explicitly excludes environment setup, exploratory sweeps, speculative code changes, and end-to-end orchestration—it executes one bounded training run with reproducibility context preserved. Outputs include SUMMARY.md, COMMANDS.md, LOG.md, SCIENTIFIC_CHANGELOG.md, COMPARABILITY_REPORT.md, and status.json. Developers reach for run-train when a paper-reproduction repo already has a chosen training command and needs structured, auditable training evidence rather than ad-hoc log files.

  • Bootstraps paper-matched training configs
  • Hooks datasets and experiment logging
  • Tracks checkpoints and metrics
  • Supports reproduction benchmarking
  • Automates repeat experiment runs

Run Train by the numbers

  • 405 all-time installs (skills.sh)
  • +10 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/lllllllama/ai-paper-reproduction-skill --skill run-train

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs405
repo stars513
Last updatedJuly 26, 2026
Repositorylllllllama/ai-paper-reproduction-skill

How do you run ML training with reproducible evidence?

Launch and monitor training jobs that reproduce published ML experiments, including configs, datasets, checkpoints, and logging for benchmark validation.

Who is it for?

ML researchers and engineers reproducing published deep-learning papers who need conservative training execution with standardized, auditable output artifacts.

Skip if: Skip run-train when the task is environment setup, hyperparameter sweeps, inference-only evaluation, or choosing which training command to run without a pre-selected command.

When should I use this skill?

User has a selected training command and wants startup verification, short-run validation, full kickoff, or resume with structured train_outputs/ reporting.

What you get

train_outputs/ folder with SUMMARY.md, COMMANDS.md, LOG.md, SCIENTIFIC_CHANGELOG.md, COMPARABILITY_REPORT.md, and status.json.

  • train_outputs/SUMMARY.md
  • train_outputs/status.json
  • train_outputs/COMMANDS.md

By the numbers

  • 6 standardized output files written to train_outputs/
  • 4 run modes: startup verification, short-run verification, full kickoff, resume
  • Uses scripts/run_training.py and scripts/write_outputs.py from the skill bundle

Files

SKILL.mdMarkdownGitHub ↗

run-train

Use this as the Rigor Train skill. The installed slug remains run-train for compatibility.

Use the shared operating principles in ../../references/agent-operating-principles.md; this skill should keep training evidence bounded while leaving repository-specific monitoring details to the model.

When to apply

  • When the training command has already been selected and should be executed conservatively.
  • When the researcher wants startup verification, short-run verification, full training kickoff, or resume handling.
  • When the run needs structured training status, checkpoint, and metric reporting.

When not to apply

  • When the main task is environment setup or asset download.
  • When the researcher wants inference-only or evaluation-only execution.
  • When the task is speculative exploration, multi-variant sweeps, or autonomous idea implementation.
  • When the user still needs repository intake or paper gap resolution.

Clear boundaries

  • This skill executes a selected training command and normalizes the resulting evidence.
  • It does not choose the overall research goal on its own.
  • It does not own exploratory branching or speculative code adaptation.
  • It should record partial, blocked, resumed, and kicked-off states clearly.
  • It should preserve reproducibility context such as configs, seeds,

checkpoints, logs, metrics, and runtime assumptions when available.

Input expectations

  • selected training goal
  • runnable training command
  • environment and asset assumptions
  • run mode such as startup verification, short-run verification, full kickoff, or resume

Output expectations

  • train_outputs/SUMMARY.md
  • train_outputs/COMMANDS.md
  • train_outputs/LOG.md
  • train_outputs/SCIENTIFIC_CHANGELOG.md
  • train_outputs/COMPARABILITY_REPORT.md
  • train_outputs/status.json

Notes

Use references/training-policy.md, ../../references/deep-learning-experiment-principles.md, scripts/run_training.py, and scripts/write_outputs.py.

Related skills

How it compares

Pick run-train over generic shell execution when you need bounded ML training runs with standardized train_outputs/ evidence for paper reproduction audits.

FAQ

What files does run-train produce?

run-train produces six files under train_outputs/: SUMMARY.md, COMMANDS.md, LOG.md, SCIENTIFIC_CHANGELOG.md, COMPARABILITY_REPORT.md, and status.json. These capture commands, configs, seeds, checkpoints, and metric evidence.

Which run modes does run-train support?

run-train supports startup verification, short-run verification, full training kickoff, and resume handling. Each mode executes the selected command conservatively and records partial, blocked, resumed, or kicked-off states in status.json.

When should you not use run-train?

Do not use run-train for environment setup, asset downloads, inference-only runs, hyperparameter sweeps, or tasks that still require repository intake or paper gap resolution before choosing a training command.

Data Science & MLllmresearchautomation

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.