MCPInstall

run-train

Rigor Train skill for deep learning research repositories. Use when a documented or selected training command should be run conservatively for startup verification, short-run verification, full kickoff, or resume, with command, config, seed, log, checkpoint, status, and metric evidence written to standardized trainoutputs/. Do not use for environment setup, exploratory sweeps, speculative idea implementation, or end-to-end orchestration.

Installs
337.8K
Last 24h
+1.3K
Trending rank
#241
Security
Warn

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/lllllllama/rigorpilot-skills --skill run-train
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads run-train automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

Security audits

Independent scans of the skill's instructions and bundled files.

Gen Agent Trust Hub WarnMEDIUM ·The skill executes deep learning training commands and manages evidence outputs. It uses dynamic code loading to import shared utilities and parses training logs for progress tracking, which presents a surface for indirect prompt injection.
Socket PassNo alerts
Snyk PassLOW ·Risk: LOW · No issues

SKILL.md

The instructions your agent reads when the skill is triggered.

run-train

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

Use the shared operating principles in ../ai-research-reproduction/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, ../ai-research-reproduction/references/deep-learning-experiment-principles.md, scripts/run_training.py, and scripts/write_outputs.py.

FAQ

What does the run-train skill do?

Rigor Train skill for deep learning research repositories. Use when a documented or selected training command should be run conservatively for startup verification, short-run verification, full kickoff, or resume, with command, config, seed, log, checkpoint, status, and metric evidence written to standardized trainoutputs/. Do not use for environment setup, exploratory sweeps, speculative idea implementation, or end-to-end orchestration.

How do I install run-train?

Run npx skills add https://github.com/lllllllama/rigorpilot-skills --skill run-train in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/run-train/ (personal) or .claude/skills/run-train/ (project).

Which AI agents can use run-train?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is run-train safe to install?

Security partners have reviewed it: Gen Agent Trust Hub flagged items to review; Socket passed; Snyk passed. As with any skill, read the SKILL.md and bundled scripts before installing.

Who maintains run-train?

It is published by lllllllama in lllllllama/rigorpilot-skills. It has 337,751 recorded installs.

More from lllllllama/rigorpilot-skills

View all →

paper-context-resolver

lllllllama/rigorpilot-skills

Rigor Paper Context helper for README-first deep learning repo reproduction. Use only when the README and repository files leave a narrow reproduction-critical gap and the task is to resolve a specific paper detail such as dataset split, preprocessing, evaluation protocol, checkpoint mapping, or runtime assumption from primary paper sources while recording conflicts. Do not use for general paper summary, repo scanning, environment setup, command execution, title-only paper lookup, or replacing README guidance by default.

Education & Science478.3K installs

repo-intake-and-plan

lllllllama/rigorpilot-skills

Rigor Intake helper for README-first deep learning repo reproduction. Use when the task is specifically to scan a repository, read the README and common project files, extract documented commands, classify inference, evaluation, and training candidates, and return the smallest trustworthy reproduction plan to the main orchestrator. Do not use for environment setup, asset download, command execution, final reporting, paper lookup, or end-to-end orchestration.

minimal-run-and-audit

lllllllama/rigorpilot-skills

Rigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized reprooutputs/ files, including patch notes when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end-to-end orchestration by itself.

Security477.4K installs

env-and-assets-bootstrap

lllllllama/rigorpilot-skills

Rigor Setup skill for README-first deep learning repo reproduction. Use when the task is specifically to prepare a conservative conda-first environment, checkpoint and dataset path assumptions, cache location hints, and setup notes before any run on a README-documented repository. Do not use for repo scanning, full orchestration, paper interpretation, final run reporting, or generic environment setup that is not tied to a specific reproduction target.

Docs & Writing477.3K installs

ai-research-explore

lllllllama/rigorpilot-skills

Rigor Explore compatible skill slug for meaningful and potentially novel deep learning research candidates. Use when the researcher has chosen the task family, dataset, benchmark, evaluation method, provided SOTA references, and wants candidate-only exploration on top of currentresearch with auditable repo understanding, idea gating, fair comparison, and governed experiments written to exploreoutputs/. Do not use for README-first trusted reproduction, open-ended direction finding, narrow code-only or run-only exploration, passive repo analysis, verified novelty claims, or implicit experimentation.

analyze-project

lllllllama/rigorpilot-skills

Rigor Analyze / Rigor Audit read-only skill for deep learning research repositories. Use when the user wants to read and understand a repository, inspect model structure and training or inference entrypoints, review configs and insertion points, or flag suspicious implementation patterns without modifying code or running heavy jobs. Do not use for active command execution, broad refactoring, speculative code adaptation, or automatic bug fixing.

Popular testing & qa skills

View category →

tdd

mattpocock/skills

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

Testing & QA1.2M installs

grilling

mattpocock/skills

Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

Testing & QA996.2K installs

migrate-to-shoehorn

mattpocock/skills

Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.

Testing & QA484.1K installs

test-driven-development

obra/superpowers

Use when implementing any feature or bugfix, before writing implementation code

Testing & QA261.8K installs

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work

Testing & QA216.8K installs

qa

mattpocock/skills

Interactive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues. Explores the codebase in the background for context and domain language. Use when user wants to report bugs, do QA, file issues conversationally, or mentions "QA session".

Testing & QA198.7K installs