Skip to main content
The template includes two coding-agent skills for changing and testing a live agent:
  • /improve-agent. Your coding agent derives probes from the agent’s instructions, judges responses, and edits until they pass. Autonomous.
  • /extend-agent. You drive this one: add a tool, refine a prompt, or fix a bug.
/improve-agent edits agents/<slug>.py. /extend-agent can also update registration, quick prompts, and dependencies when the requested change requires them. The local container reloads code edits before the next probe.

​
Improve: autonomous probe-and-judge

Open your coding agent in the agent-platform directory and run:
The coding agent reads the target agent’s INSTRUCTIONS and typically derives 8-12 probes across four categories: golden path, edge cases, tool selection, and adversarial. For each probe, it calls the live container, reads tool calls from the logs, and judges PASS or FAIL against what the instructions promise. For every failure, it changes one lever: instructions, tools, context provider, model, or num_history_runs. It re-runs failed probes and spot-checks previously passing probes for regressions.

​
Extend: user-driven changes

When you have a specific change in mind, run:
The coding agent asks what to change. You describe a tool to add, a prompt to refine, or a bug to fix. The agno-docs MCP grounds toolkit and API changes. Each iteration makes and verifies one small change.

​
When to run each

​
Next

Run your platform on Railway →