Skip to main content

ax-cpp-playbook

Use when writing C++ 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.

来源信息

仓库
ax-llm/ax
最近来源活动
2026年10月15日 09:33
检测到的 SKILL.md 语言
英语
星标
2,967
分支
198

安装方式

默认使用会先检查来源的 Prompt;你也可以切换为直接命令,或下载本地副本。

检查来源文件

决定是否安装前,请先阅读 SKILL.md,以及 SkillsMP 当前展示的配套文件。

正在显示 SKILL.md

SKILL.md
来源说明 · 只读预览
name
ax-cpp-playbook
description
Use when writing C++ 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.4.1
# Ax Playbook For C++ 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(). - 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: 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 ```cpp 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::playbook`, `axllm::AxPlaybook`, `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.
在 GitHub 查看