Agent Optimize Use when writing Rust code with `axllm` for agent optimization, verified agent-playbook evolution, evaluators, judges, optimizer artifacts, BootstrapFewShot, and GEPA. rust skills skill-agent-optimize packages/rust/skills/ax-rust-agent-optimize/SKILL.md skill Agent Optimize

AxAgent Optimize For Rust

Use when writing Rust code with axllm for agent optimization, verified agent-playbook evolution, evaluators, judges, optimizer artifacts, BootstrapFewShot, and GEPA.

Install

Install only this skill for Rust:

Shell
npx skills add https://ax-llm.github.io/ax/rust/ --skill 'ax-rust-agent-optimize'

Published skill file: ax-rust-agent-optimize/SKILL.md.

Source

Skill Instructions

This skill helps an agent write Rust code with the generated Ax package axllm. Use the generated package API, examples, and manifests; do not import TypeScript-only APIs unless you are editing the TypeScript package.

When To Use

  • Optimize an AxAgent or reusable program component.
  • Mine grounded weaknesses from failed agent tasks and keep only playbook proposals that pass the verification gate.
  • Create evaluator callbacks and persist optimizer artifacts.
  • Keep optimization runs bounded by explicit budgets and dataset rows.

Package Facts

  • Language: Rust.
  • Package: axllm.
  • Package API docs: API.md and axir-api.json.
  • Capability manifest: axir-capabilities.json.
  • Runnable examples: examples/.
  • Real network support: yes.
  • Scripted no-key transport support: yes.
  • Runtime profiles: javascript-quickjs.

Core Pattern

Rust
let engine = axllm::AxGEPA::new(reflection_client, options)?;
let result = engine.optimize(request, evaluator)?;

Relevant API Surface

  • Agents And RLM: agent, AxAgent
  • Optimizers: optimize, playbook, AxPlaybook, AxBootstrapFewShot, AxGEPA, OptimizerEngine, OptimizerEvaluator

Guardrails

  • Start from package examples for exact native syntax before inventing a new call shape.
  • Use provider-api examples only when the user explicitly has provider credentials available.
  • Use no-key examples for deterministic local checks and provider request mapping.
  • Treat AxIR as the source of generated package truth: if package docs disagree with source code, update the compiler and regenerate packages.
  • Do not copy repo-maintainer skills from tools/*/skills/ into user packages.
Docs