autorl-mini-orchestrator

Orchestrates a two-stage AutoRL workflow with main-thread clarification and a retrieval subagent.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Testing multi-agent handoffs for reinforcement learning research workflows is hard to control: clarification, evidence retrieval, and validation often get mixed into one thread, making it impossible to verify that artifacts pass cleanly between agents. This Skill runs a minimal, gated AutoRL skill-chain test so you can confirm the handoff works before scaling up. ## Core Features & Use Cases - Gated two-stage workflow: Clarifies the RL task in the main thread into task_card.md, validates it against a clarification gate, then delegates evidence retrieval to a single child agent that produces evidence_report.md. - Strict orchestration boundaries: The main agent never performs retrieval, cloning, dependency installation, or training, and child agents cannot spawn further subagents. - Auditable artifact chain: Every run produces task_card.md, clarification_log.md, evidence_report.md, and a final orchestrator_report.md with gate results, blockers, and next actions. - Use Case: You want to verify that your AutoRL skill chain (task clarifier plus evidence retrieval) hands off correctly between a main agent and one subagent, with explicit pass/fail gates and a written report for each run. ## Quick Start Use the autorl-mini-orchestrator skill to clarify my RL task in the main thread, then run evidence retrieval in a child agent and write the orchestrator report.

Frequently Asked Questions about autorl-mini-orchestrator

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

FAQPage Schema
How do I test an AutoRL multi-agent handoff workflow?

Run this orchestrator with an explicit RL task request. It clarifies the task in the main thread into task_card.md, validates it against a clarification gate, spawns one retrieval subagent to write evidence_report.md, then records all gate results in orchestrator_report.md.

How does the orchestrator validate the task card before retrieval?

Validation checks that task_card.md exists, handoff_status is ready, ambiguity_score is at most 0.15, and required fields like task_mode, environment type, RL task, algorithm direction, success criteria, and runtime boundary are present. Retrieval only starts after the gate passes.

What happens if subagents are unavailable during the workflow?

The orchestrator stops before retrieval with orchestration_status set to blocked_before_retrieval and writes an orchestrator_report.md explaining the blocker. It never silently runs evidence retrieval in the main thread.

Can the retrieval subagent clone repositories or run training?

No. The retrieval subagent is restricted to evidence retrieval and synthesis only. It must not clone repositories, install dependencies, copy third-party code, run training, or spawn additional subagents; violations fail the retrieval gate.

What artifacts does the mini orchestration run produce?

Each run directory contains task_card.md, clarification_log.md, evidence_report.md, orchestrator_report.md, and the filled retrieval prompt under subagent_prompts/. The orchestrator report records gate results, artifact paths, blockers, and the recommended next action.