<< All versions

Skill v25.0.0

currentAutomated scan100/100
ax-llm/ax/ax-python-playbook

3 files

──Details
PublishedOctober 2, 2026 at 05:49 AM
Content Hashsha256:8f880349c4e9bff1...
Git SHAedec2476e945
Bump Typepatch
Compare with v24.0.18
──Files
Files (1 file, 2.1 KB)
SKILL.md2.1 KBactive
SKILL.md · 49 lines · 2.1 KB

name: "ax-python-playbook" description: "Use when writing Python code with axllm for the playbook() context-engineering surface, agent-bound verified evolution, run-end learning, online updates, and rendering a playbook into a program." version: "25.0.0"


Ax Playbook For Python

This skill helps an agent write Python 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

  • Grow an evolving context playbook for a program or agent stage with playbook().
  • Attach a seed playbook to an agent and learn bounded avoidance rules from run-end failure signals.
  • Use the agent-bound playbook evolve method to mine grounded weaknesses with verification and exact rollback.
  • Refine a playbook online from live feedback or offline from labeled examples.
  • Render or persist a playbook and inject it into a program context.

Package Facts

  • Language: Python.
  • 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, python-pyodide.

Core Pattern

python
from axllm import ax, playbook
program = ax("question:string -> answer:string")
pb = playbook(program, {"studentAI": llm})
pb.evolve(examples, metric_fn)

Relevant API Surface

  • 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.
← v24.0.18All versions