arize-instrumentation
INVOKE THIS SKILL when adding Arize AX tracing to an application. Follow the Agent-Assisted Tracing two-phase flow: analyze the codebase (read-only), then implement instrumentation after user confirmation. When the app uses LLM tool/function calling, add manual CHAIN + TOOL spans so traces show each tool's input and output. Leverages https://arize.com/docs/ax/alyx/tracing-assistant and https://arize.com/docs/PROMPT.md.
npx skills add majiayu000/claude-skill-registry --skill arize-instrumentation --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Arize Instrumentation Skill Use this skill when the user wants to **add Arize AX tracing** to their application. Follow the **two-phase, agent-assisted flow** from the [Agent-Assisted Tracing Setup](https://arize.com/docs/ax/alyx/tracing-assistant) and the [Arize AX Tracing — Agent Setup Prompt](https://arize.com/docs/PROMPT.md). ## Quick start (for the user) If the user asks you to "set up tracing" or "instrument my app with Arize", you can start with: > Follow the instructions from https://arize.com/docs/PROMPT.md and ask me questions as needed. Then execute the two phases below. ## Core principles - **Prefer inspection over mutation** — understand the codebase before changing it. - **Do not change business logic** — tracing is purely additive. - **Use auto-instrumentation where available** — add manual spans only for custom logic not covered by integrations. - **Follow existing code style** and project conventions. - **Keep output concise and production-focused** — do not generate extra documentation or summary files. ## Phase 1: Analysis (read-only) **Do not write any code or create any files during this phase.** ### Steps 1. **Check dependency manifests** to detect stack: -
- Quick start (for the user)
- Core principles
- Phase 1: Analysis (read-only)
- Steps
- What to identify
- Phase 1 output
- Integration routing and docs
- Phase 2: Implementation
- Implementation rules
- Enriching traces: manual spans for tool use and agent loops
- Why doesn't the auto-instrumentor do this?
- Verification
- Leveraging the Tracing Assistant (MCP)
- Reference links
What does the arize-instrumentation skill do?
INVOKE THIS SKILL when adding Arize AX tracing to an application. Follow the Agent-Assisted Tracing two-phase flow: analyze the codebase (read-only), then implement instrumentation after user confirmation. When the app uses LLM tool/function calling, add manual CHAIN + TOOL spans so traces show each tool's input and output. Leverages https://arize.com/docs/ax/alyx/tracing-assistant and https://arize.com/docs/PROMPT.md.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill arize-instrumentation --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.