rlxp-queue-batch

Summarize ready, running, completed, and blocked jobs from RLXP batch manifests.

1|Updated May 14, 2026
One-click install
npx skills add https://github.com/junhyekh/rlxp --skill rlxp-queue-batch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rlxp-queue-batch
Source: https://github.com/junhyekh/rlxp/tree/main/plugins/rl-experiment-assistant/skills/rlxp-queue-batch
Command: npx skills add https://github.com/junhyekh/rlxp --skill rlxp-queue-batch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps multi-run RLXP experiment batches resumable and visible so jobs do not drift across candidates, seeds, or phases.

Core Features & Use Cases

  • Reports ready, running, completed, and blocked jobs from a local queue manifest.
  • Marks jobs complete when expected outputs already exist and identifies what can launch next.
  • Useful for smoke tests, short trials, promoted runs, and incumbent validation across isolated workspaces.

Quick Start

Ask the assistant to inspect the queue manifest and return the current ready, running, completed, and blocked jobs without launching training.

Frequently Asked Questions about rlxp-queue-batch

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

FAQPage Schema
How do I track RL experiment batch jobs without launching training?

You can track RL experiment batch jobs without launching training by inspecting a local queue manifest to report ready, running, completed, and blocked jobs. This requires manifest state, contract approval, isolated job workspaces, and dry-run gating before any launch path.

What is a dry-run gated queue manifest for RL batches?

A dry-run gated queue manifest is a local state file that tracks RLXP batch jobs across candidates, seeds, and phases. It keeps multi-run batches resumable and visible so jobs do not drift, ensuring no training launches until dry-run gating and contract approval are verified.

How do I identify which RL jobs are ready to launch next from a batch?

To identify which RL jobs are ready to launch next, inspect the queue manifest to mark jobs complete when expected outputs already exist. The manifest then summarizes blocked jobs and highlights what can launch next across smoke, short-trial, promoted, and incumbent-validation queues.

Can I use queue batch tracking for smoke tests and incumbent validation in task-scoped RL repositories?

Yes, you can use queue batch tracking for smoke tests, short trials, promoted runs, and incumbent validation in task-scoped RL repositories. It operates across isolated job workspaces to keep multi-run RLXP experiment batches visible and resumable.

Why are my RLXP batch jobs showing as blocked in the queue manifest?

RLXP batch jobs show as blocked in the queue manifest when prerequisites like contract approval, isolated job workspaces, or expected outputs from prior phases are not met. The tracking system prevents launch paths until dry-run gating validates the required manifest state.