rl-agentic-launch-jupiter

Launch agentic RL experiments on Jupiter with SkyRL, Harbor, and Daytona.

276|37|Updated Dec 5, 2025
One-click install
npx skills add https://github.com/open-thoughts/OpenThoughts-Agent --skill rl-agentic-launch-jupiter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rl-agentic-launch-jupiter
Source: https://github.com/open-thoughts/OpenThoughts-Agent/tree/main/.claude/skills/rl-agentic-launch-jupiter
Command: npx skills add https://github.com/open-thoughts/OpenThoughts-Agent --skill rl-agentic-launch-jupiter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Launch / relaunch agentic RL experiments on Jupiter using SkyRL, Harbor, and Daytona across multiple arm configurations.

Core Features & Use Cases

  • Supports dense 8B/32B arms and MoE Megatron configurations with a unified launch workflow.
  • Handles runtime/SIF selection, chain-restart conventions, and workspace conventions for Jupiter.
  • Use case: starting a new RL run or resuming a paused run on Jupiter with proper config.

Quick Start

Run the canonical launch command from the repo root to start or resume a SkyRL run on Jupiter.

Frequently Asked Questions about rl-agentic-launch-jupiter

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

FAQPage Schema
How do I launch agentic RL experiments on Jupiter?

To launch agentic RL experiments on Jupiter, run the canonical launch command from the repo root to orchestrate SkyRL, Harbor, and Daytona runs using proper YAML configs and the hpc.launch tool.

Can I resume a paused SkyRL run on Jupiter without losing configuration?

You can resume a paused SkyRL run on Jupiter using the unified launch workflow, which handles chain-restart conventions, per-arm config, model_path, and runtime SIF selection automatically.

Does this workflow support dense 8B and 32B Megatron configurations?

Yes, the launch workflow supports dense 8B/32B arms and MoE Megatron configurations, allowing you to manage per-arm config and model paths across multiple arm setups on Jupiter.

What resources do I need to access before starting Harbor or Daytona runs?

Starting Harbor or Daytona runs requires the hpc.launch tool, proper YAML configs, and access to Jupiter resources as described in the rl_experiments documentation.

Why are my SkyRL launches failing on Jupiter?

SkyRL launches on Jupiter fail when missing required YAML configs, lacking hpc.launch tool access, or not following workspace and runtime SIF selection conventions specified in rl_experiments documentation.