auto-research

Orchestrate NeMo-RL research campaigns with git and TSV experiment logging.

Updated May 23, 2026
One-click install
npx skills add https://github.com/yo-steven/skills-exploration-20260522 --skill auto-research-yo-steven
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-research
Source: https://github.com/yo-steven/skills-exploration-20260522/tree/main/skills/NeMo-RL/auto-research
Command: npx skills add https://github.com/yo-steven/skills-exploration-20260522 --skill auto-research-yo-steven

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the problem of turning vague research goals for NeMo-RL/NeMo-gym into a disciplined, reproducible sequence of experiments that actively tests hypotheses and records results.

Core Features & Use Cases

  • End-to-end experiment lifecycle guidance: translates an objective into monitored stop rules, prepares baselines, executes iterative runs, and decides keep/discard/crash for each idea.
  • Reproducibility with git + TSV ledger: branches per hypothesis, commits minimal changes, and logs authoritative metrics, command provenance, resource signals, and outcomes in a TSV schema.
  • Practical operational guardrails: preserves unrelated user work, selects the right launcher/environment (local vs Slurm vs Kubernetes), and uses session-memory handoffs to maintain continuity across long campaigns.

Quick Start

Use the auto-research skill to run directed hypothesis testing in this repo for your chosen NeMo-RL or NeMo-gym recipe and metric, while writing all results to the research TSV ledger.

Frequently Asked Questions about auto-research

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate NeMo-RL experiments for directed hypothesis testing?

To automate NeMo-RL experiments for directed hypothesis testing, this Skill iteratively plans, runs, and evaluates runs while applying objective metrics with explicit stop rules. It orchestrates the entire lifecycle from baseline creation to final evaluation.

What is the best way to ensure reproducibility in NeMo-gym recipe workflows?

Reproducibility in NeMo-gym recipe workflows is ensured by using deliberate git branching per hypothesis, committing minimal changes, and logging authoritative metrics and command provenance in a durable TSV ledger.

How does metric tracking work during autonomous reinforcement learning campaigns?

Metric tracking during autonomous reinforcement learning campaigns works by extracting authoritative metrics like validation accuracy or reward, evaluating them against monitored stop rules, and recording outcomes in a TSV schema.

Can I use uv for reproducible command execution in NeMo-RL experiment automation?

Yes, you can use uv for reproducible command execution in NeMo-RL experiment automation. The Skill executes iterative runs via uv to maintain strict command provenance and reproducible environments.

Does this approach support distributed environments like Slurm or Kubernetes for experiment automation?

Experiment automation supports distributed environments by selecting the right launcher for your infrastructure, including local, Slurm, or Kubernetes, while preserving existing user work and applying operational guardrails.

How do I maintain session continuity across long reinforcement learning research campaigns?

You maintain session continuity across long reinforcement learning research campaigns using checkpointed session-memory handoffs. This preserves state and context across iterative planning, running, and evaluating experiments.