metaclaw-evolving-agent — Claude Code skill: deploy MetaClaw
This skill walks you through deploying MetaClaw, a proxy agent that injects learned skills into conversations and trains on live sessions.
npx skills add reason-machines/trending-skills --skill metaclaw-evolving-agent -a claude-codeWhat metaclaw-evolving-agent does
MetaClaw sits in front of your LLM as an OpenAI-compatible proxy. Clients point at http://localhost:<port>, and the agent intercepts each turn, pulls relevant skills into the system prompt, and stores the exchange in an experience buffer. The skill covers installation, the metaclaw setup wizard, and three run modes: skills injection alone, immediate RL training, or madmax, where a scheduler pushes weight updates into idle and sleep windows.
You get guidance on ~/.metaclaw/config.yaml, the environment variables, and the Python API — MetaClawAgent, SkillStore, SkillInjector, ExperienceBuffer, RLTrainer, RewardModel. The skills_only mode needs no GPU. RL training wants METACLAW_TINKER_API_KEY, or METACLAW_MINT_API_KEY when the backend is mint. Meeting detection in the scheduler reads OAuth credentials from GOOGLE_CALENDAR_CREDENTIALS_PATH.
Set METACLAW_LLM_API_KEY before anything else. Without it the proxy has no upstream model to forward to, and metaclaw start gets you nowhere. Installation runs from the local repo with pip install -e . plus extras: [rl], [evolve], [scheduler].
What it helps with
- stand up a proxy agent in front of an existing LLM endpoint
- inject retrieved skills into the system prompt each turn
- record conversation turns into an experience buffer for training
- run batched GRPO training without a local GPU
- defer weight updates to sleep hours and idle time
Example prompts for the agent
- Run
metaclaw setup, then start MetaClaw inskills_onlymode - Start
metaclaw startin madmax mode so training waits for idle time - Add a
code-review-checklistskill toSkillStoreand inject it into queries
How to install metaclaw-evolving-agent
1Skills CLI (Vercel)
npx skills add reason-machines/trending-skills --skill metaclaw-evolving-agent -a claude-code2Manually: put the files in place
~/.claude/skills/metaclaw-evolving-agent/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/metaclaw-evolving-agent/
1Skills CLI (Vercel)
npx skills add reason-machines/trending-skills --skill metaclaw-evolving-agent -a codex2Manually: put the files in place
.agents/skills/metaclaw-evolving-agent/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add reason-machines/trending-skills --skill metaclaw-evolving-agent -a cursor2Manually: put the files in place
.cursor/skills/metaclaw-evolving-agent/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install reason-machines/trending-skills metaclaw-evolving-agent2Manually: put the files in place
.github/skills/metaclaw-evolving-agent/SKILL.md1Skills CLI (Vercel)
npx skills add reason-machines/trending-skills --skill metaclaw-evolving-agent -a gemini-cli2Platform CLI
gemini skills install https://github.com/reason-machines/trending-skills --path skills/metaclaw-evolving-agentManually: put the files in place
.devin/skills/metaclaw-evolving-agent/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add reason-machines/trending-skills --skill metaclaw-evolving-agent -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about metaclaw-evolving-agent
How do I install metaclaw-evolving-agent in Claude Code?
Run npx skills add reason-machines/trending-skills --skill metaclaw-evolving-agent -a claude-code. The skill lands in ~/.claude/skills/metaclaw-evolving-agent/SKILL.md.
What does metaclaw-evolving-agent do?
It handles MetaClaw deployment and configuration: the setup wizard, the three operating modes, environment variables, and Python API examples for skill injection and RL training.
What does MetaClaw need for RL mode?
A METACLAW_TINKER_API_KEY, or METACLAW_MINT_API_KEY if the backend is mint. Training fires once the experience buffer holds a full batch.