Write C++ axllm code implementing AxCodeRuntime loops and session flows.
npx skills add https://github.com/ax-llm/ax --skill ax-cpp-agent-rlm
Please help me install this Agent Skill. Skill: ax-cpp-agent-rlm Source: https://github.com/ax-llm/ax/tree/main/website/static/cpp/.well-known/agent-skills/ax-cpp-agent-rlm Command: npx skills add https://github.com/ax-llm/ax --skill ax-cpp-agent-rlm
This Skill helps developers write correct C++ integrations for Ax-generated agent runtime loops, session handling, and runtime envelopes without drifting into TypeScript-only patterns.
Ask for a C++ axllm implementation that uses the package examples and API docs to build an AxCodeRuntime session for an agent loop.
High-intent search queries and answers about installing and using this skill.
Implement C++ agent runtime loops by using the axllm package API to construct AxCodeRuntime sessions and wire executor loops that follow AxIR-aligned execution paths. You must supply package examples and capability manifests to guarantee the generated code matches native C++ contracts instead of TypeScript-only call shapes.
ProcessCodeRuntime supplies a concrete execution path within an AxCodeSession when an actor-code session needs to run against real network providers or local no-key checks. It operates inside a runtime envelope that keeps execution aligned with generated AxIR truth and provider-aware constraints.
Yes, you can apply optional runtime profiles to AxCodeRuntime sessions in C++ to configure provider-aware execution. The axllm package API supports these profiles to help native C++ agents run against specific network providers or local checks while maintaining AxIR alignment and generated package contracts.
Generated C++ agent code drifts into TypeScript-only call shapes when guardrails are not applied to keep packages aligned with AxIR. You must enforce capability manifests and use the generated package API to prevent incorrect call shapes that do not match native C++ integration requirements.
Before building C++ AxCodeRuntime sessions, you need package examples, capability manifests, and guardrails prepared. These inputs ensure the generated axllm package APIs align with AxIR and provide the correct contracts for native C++ integration of agent and session workflows without TypeScript drift.
The main limitation is the strict requirement to avoid TypeScript-only patterns; axllm native C++ agent loops must follow generated package contracts and AxIR truth. Without proper capability manifests and guardrails, provider-aware execution and session handling may fail to integrate correctly into the runtime envelope.
ax-llmGenerate Python code for the axllm package using native signatures and entrypoints.
ax-llmImplement Go runtime integrations for Ax code execution loops and agent sessions.
ax-llmBuild Java Ax agent runtime code for the dev.axllm:ax package.
ax-llmWrite Java Ax agent code using generated dev.axllm:ax APIs for typed LLM workflows.
