<< All versions

Skill v25.4.3

currentLLM-judged scan90/100
ax-llm/ax/ax-java-playbook

1 files

──Details
PublishedOctober 20, 2026 at 01:06 AM
Content Hashsha256:5165d79a9aed5067...
Git SHA818d15b02d57
Bump Typepatch
Compare with v24.0.21
──Files
Files (1 file, 2.1 KB)
SKILL.md2.1 KBactive
SKILL.md · 48 lines · 2.1 KB

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


Ax Playbook For Java

This skill helps an agent write Java code with the generated Ax package dev.axllm:ax. 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: Java.
  • Package: dev.axllm:ax.
  • 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

java
AxGen program = Ax.ax("question:string -> answer:string");
AxPlaybook pb = Ax.playbook(program, java.util.Map.of("studentAI", llm));
pb.evolve(examples, metricFn, java.util.Map.of());

Relevant API Surface

  • Optimizers: Ax.optimize, Ax.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.21All versions