rl-framework-implementer

Implements reinforcement-learning training paths with framework selection, dependency planning, and bounded smoke tests.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a clarified AutoRL task into runnable code is risky: choosing the wrong RL framework, installing dependencies without approval, or launching full training prematurely can waste compute and break reproducibility. This Skill converts evidence-backed task artifacts into a concrete, approval-gated implementation path. ## Core Features & Use Cases - Framework Selection: Chooses between reusing an existing local framework, adding a maintained RL library (Stable-Baselines3, CleanRL, Tianshou, RLlib), cloning a reference repo into third_party/, or writing a minimal native implementation, with rationale recorded in implementation_plan.md. - Dependency & Approval Gating: Writes dependency_plan.md with exact commands, version/commit pins, risks, and rollback notes before any pip install, git clone, or large download. - Bounded Verification: Runs only the smoke tests allowed by the execution boundary (generate_only, dry_run, or runtime_allowed) and reports results in smoke_test_report.md. - Use Case: Given a task card, evidence report, and decision packet for a Gymnasium-based PPO task, the Skill inspects the workspace, selects Stable-Baselines3, writes env adapter, training and evaluation entrypoints, and runs a one-step dry-run smoke test without starting full training. ## Quick Start Use the rl-framework-implementer skill to set up the RL framework and implement the training path for the task defined in runs/<task-id>/task_card.md.

Frequently Asked Questions about rl-framework-implementer

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

FAQPage Schema
How do I implement an RL training pipeline from a task specification?

Provide a task card, evidence report, and decision packet under runs/<task-id>/. The Skill inspects the workspace, selects a framework route, writes environment adapters, training and evaluation entrypoints, and runs bounded smoke tests, producing implementation_plan.md and smoke_test_report.md.

Which RL framework should I use for a Gymnasium environment?

For standard Gymnasium tasks, Stable-Baselines3 offers fast PPO/SAC/TD3/DQN baselines, while CleanRL suits readable single-file implementations. The Skill prefers existing project frameworks first, then evidence-backed libraries, and records the rationale in implementation_plan.md.

Can the Skill install packages or clone repositories automatically?

No. pip install, conda install, git clone, and large downloads always require explicit approval. The Skill first writes dependency_plan.md listing exact commands, version pins, risks, and rollback notes, then waits for approval before executing.

What is the difference between generate_only, dry_run, and runtime_allowed?

generate_only permits only static checks and file generation. dry_run allows imports, environment construction, and one-step rollouts with existing dependencies. runtime_allowed additionally permits short smoke training, but never full experiments without separate approval.

When should I write a native RL implementation instead of using a library?

Choose native code when the environment and algorithm are simple, dependency or network policy blocks installs, or project conventions already provide most infrastructure. The Skill documents this route and alternatives considered in implementation_plan.md.