Skip to main content
Once an agent works on its main path, test the edges it promises to handle. The template gives coding agents the instructions, runtime logs, and live endpoint they need to probe behavior and make small verified changes. The template includes two coding-agent skills for changing and testing a live agent:
  • improve-agent derives probes from the agent’s instructions, judges responses, and makes focused edits.
  • extend-agent takes a change you specify, such as adding a tool, refining a prompt, or fixing 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: probe, judge, and edit

Open your coding agent in the agent-platform directory and ask it to run:
The skill:
  1. Reads the target agent’s INSTRUCTIONS and typically derives 8-12 probes across golden path, edge cases, tool selection, and adversarial behavior.
  2. Runs each probe against the live container, reads tool calls from the logs, and judges the response against what the instructions promise.
  3. Changes one part of the agent for each failure: instructions, tools, context provider, model, or num_history_runs.
  4. Re-runs failed probes and spot-checks passing probes for regressions.
If the same probe fails three times or the skill reaches five edit cycles, it stops and reports the blocker.

​
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. It checks the current Agno documentation before changing toolkit or API usage. Each iteration makes and verifies one small change.

​
When to run each

​
Next

Lock in behavior with evals →