autorl-skill-workflow-v2

Orchestrates file-backed AutoRL workflows from environment intake through guarded training and evaluation.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/Lingjie-wang/autoRL --skill autorl-skill-workflow-v2-lingjie-wang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autorl-skill-workflow-v2
Source: https://github.com/Lingjie-wang/autoRL/tree/main/autorl-skill-workflow-v2
Command: npx skills add https://github.com/Lingjie-wang/autoRL --skill autorl-skill-workflow-v2-lingjie-wang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Running reinforcement learning experiments with an AI agent often lacks structure: environments are unverified, training launches without approval, results are not reproducible, and state is lost on interruption. This Skill provides a deterministic, file-backed state machine that coordinates environment onboarding, evidence retrieval, training implementation, supervised execution, and result packaging with explicit approval gates. ## Core Features & Use Cases - Dual Workflow Profiles: Supports application_delivery (turn custom environment code into a verified, runnable training package) and research_iteration (reproduce and improve a baseline under a frozen comparison protocol). - Guarded Experiment Execution: Enforces an authority model separating build, experiment, control, and dependency permissions, so full training only launches with an exact run-plan approval digest. - Recoverable State Machine: Uses append-only hash-chained JSON events, compare-and-swap state transitions, and validation scripts so runs can resume safely after interruption. - Bounded Subagent Coordination: Spawns scoped child workers for environment onboarding, verification, evidence retrieval, training builds, and telemetry supervision, with the main orchestrator validating every artifact. - Use Case: A researcher provides a custom Gym environment and asks for a PPO training pipeline. The Skill verifies the environment contract, gathers evidence, builds checkpointable training code, runs a smoke test, and packages the verified deliverable without launching unauthorized full training. ## Quick Start Ask the agent to initialize an AutoRL run with the application_delivery profile for your custom environment and produce a verified training package with dry_run build authority.

Frequently Asked Questions about autorl-skill-workflow-v2

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

FAQPage Schema
How do I run a guarded RL training workflow with an AI agent?

Initialize a run with the statectl.py CLI, selecting either the application_delivery or research_iteration profile. The workflow progresses through intake, environment verification, strategy freezing, training build, and approved launch, with each stage artifact validated before the next stage consumes it.

What is the difference between application_delivery and research_iteration profiles?

application_delivery turns custom environment code into a verified, runnable training package and stops after code verification by default. research_iteration reproduces a baseline under a frozen comparison protocol, supervises approved training, and derives bounded child runs for improvement hypotheses.

Can the workflow launch full RL training automatically?

No. Full training requires experiment_authority set to exact_run_approved, bound to the digest of the run plan, budget, seeds, environment, code, and config. Smoke-level permissions never imply full-training permission, and any change to the plan invalidates the approval.

How does the workflow recover after an interruption or crash?

Every state mutation appends a hash-chained event and uses compare-and-swap versioning. On resume, validate_run.py checks the event chain and artifact digests, then reconciles process heartbeat, launch tokens, and checkpoints, failing closed rather than blindly relaunching.

What are the limitations of the supervised training control loop?

Monitoring agents only observe and propose actions; a deterministic guard script authorizes them, and actuators apply only unexpired allow authorizations at safe boundaries. No live code patching, reward changes, or actions absent from the frozen control contract are permitted.