rlxp-dr-probe

Plan one-parameter-at-a-time domain-randomization probes for incumbent reinforcement-learning policies.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you safely assess whether an incumbent reinforcement-learning policy can tolerate domain randomization before you widen training or deployment ranges.

Core Features & Use Cases

  • Controlled Probe Planning: Breaks a parameter space into one-parameter-at-a-time probe jobs so you can isolate what actually hurts performance.
  • Evidence-Based Robustness Assessment: Summarizes local evaluation results into a conservative view of which randomized settings remain feasible.
  • Use Case: A policy performs well at nominal settings but fails under noise or simulation variation, so you use this Skill to map narrow safe ranges before proposing broader DR training.

Quick Start

Ask the assistant to plan a controlled domain-randomization probe for your incumbent policy using your approved evaluation template, safe bounds, and task contract.

Frequently Asked Questions about rlxp-dr-probe

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

FAQPage Schema
How do I test reinforcement learning policy robustness against domain randomization?

To test reinforcement learning policy robustness, you plan controlled domain-randomization probes that break the parameter space into one-factor-at-a-time jobs to isolate which randomized settings degrade nominal performance.

What is a controlled domain-randomization probe for an RL policy?

A controlled domain-randomization probe is a targeted evaluation that systematically varies simulation parameters one at a time to map safe operating ranges for an incumbent reinforcement-learning policy before deployment.

Do I need local evaluation evidence to start planning domain-randomization probes?

Yes, you need local evaluation evidence, approved probe bounds, guardrail thresholds, and dry-run helper workflows, because this Skill plans probes conservatively and keeps planning separate from launching.

Why does my reinforcement learning policy fail under simulation noise but pass nominal settings?

Your policy likely lacks robustness to randomized simulation variations, requiring a controlled probe to identify which specific noise parameters exceed your policy's tolerance and narrow the safe operating ranges.

What's the best way to isolate which randomization parameters hurt RL policy performance?

The best way to isolate harmful randomization parameters is executing one-parameter-at-a-time probe jobs, which evaluate each domain randomization factor independently to pinpoint exact failure thresholds.

When should I not use controlled domain-randomization probes?

You should not use controlled domain-randomization probes if nominal performance is unacceptable, because these probes are designed for task-scoped robustness checks only after baseline performance is verified.