rl-env-mvp
Skill4 starsChanged 27 days agoNo licenceView on GitHub
Scaffold a minimal, readable RL environment for GRPO, PPO or RLOO — task source, prompt, rollout, verifier, reward, eval and a pre-training probe — and prove it works before any policy is trained. Use when starting an RL/RLVR project from scratch, when the user asks for an "RL environment", "RL harness", "RLVR setup", "reward function and verifier", or "get an RL loop running on this task", and whenever a task, model, reward, dataset and algorithm need turning into something a human can read, edit and start tuning. Covers the path from zero to a first fine-tune; it does not tune training itself, and preference methods (DPO, KTO, ORPO) are out of scope.
In this repository40 other files it gives its agents.
- AGENTS.mdAGENTS.md
- block-diagramSkill
- brainstormSkill
- buildSkill
- call-treeSkill
- checkpoint-commitsSkill
- code-proofSkill
- code-tidySkill
- codifySkill
- coding-standardsSkill
- consistencySkill
- escalateSkill
- experimentSkill
- explainSkill
- hparam-priorsSkill
- minimal-coverSkill
- ml_loggingSkill
- notesSkill
- outlineSkill
- plan-docSkill
- prior-workSkill
- project-briefSkill
- proof-of-valueSkill
- recapSkill
- reflectSkill
- repo-layoutSkill
- reportSkill
- run-triageSkill
- schema-diagramSkill
- sequence-diagramSkill
- sft-env-mvpSkill
- skill-auditSkill
- skills-repo-accessSkill
- spec-docSkill
- sprint-tasksSkill
- test-planSkill
- tldrSkill
- tune-loopSkill
- tune-preflightSkill
- tune-reportSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 4 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.