Observability Use when writing Python code with `axllm` for agent tracing, usage accounting, action logs, runtime diagnostics, replay, and production debugging. python skills skill-agent-observability packages/python/skills/ax-python-agent-observability/SKILL.md skill Observability

AxAgent Observability For Python

Use when writing Python code with axllm for agent tracing, usage accounting, action logs, runtime diagnostics, replay, and production debugging.

Install

Install only this skill for Python:

Shell
npx skills add https://ax-llm.github.io/ax/python/ --skill 'ax-python-agent-observability'

Published skill file: ax-python-agent-observability/SKILL.md.

Source

Skill Instructions

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

  • Inspect agent traces, runtime envelopes, usage, or action logs.
  • Attach callbacks for model/tool activity and runtime progress.
  • Debug agent loops through generated package state and examples.

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 agent

helper = agent("question:string -> answer:string")
out = helper.forward(llm, {"question": "How should I proceed?"})

Relevant API Surface

  • Agents And RLM: agent, AxAgent
  • Runtime Profiles: ProcessCodeRuntime, RuntimeCapabilities, RuntimeEnvelope, javascript-quickjs, python-pyodide

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