Playbook Use when writing C++ code with `axllm` for the playbook() context-engineering surface, evolving task knowledge, online updates, and rendering a playbook into a program. cpp skills skill-playbook packages/cpp/skills/ax-cpp-playbook/SKILL.md skill Playbook

Ax Playbook For C++

Use when writing C++ code with axllm for the playbook() context-engineering surface, evolving task knowledge, online updates, and rendering a playbook into a program.

Install

Install only this skill for C++:

Shell
npx skills add https://ax-llm.github.io/ax/cpp/ --skill 'ax-cpp-playbook'

Published skill file: ax-cpp-playbook/SKILL.md.

Source

Skill Instructions

This skill helps an agent write C++ 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().
  • 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: C++.
  • 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

C++
auto program = axllm::ax("question:string -> answer:string");
auto pb = axllm::playbook(program, *llm);
pb.evolve(examples, metric_fn);

Relevant API Surface

  • Optimizers: axllm::optimize, axllm::AxBootstrapFewShot, axllm::AxGEPA, axllm::OptimizerEngine, axllm::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