Official agent skill

Phoenix Tracing

OpenInference semantic conventions and instrumentation for Phoenix AI observability.

OfficialApache-2.0Auto-check passedAI & LLM Engineering

Install Phoenix Tracing

skills CLI

$ npx skills add github/awesome-copilot --skill phoenix-tracing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install github/awesome-copilot phoenix-tracing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/phoenix-tracing .claude/skills/phoenix-tracing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "phoenix-tracing" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/phoenix-tracing into .claude/skills/phoenix-tracing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "phoenix-tracing", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/github/awesome-copilot/tree/main/skills/phoenix-tracing

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add github/awesome-copilot --skill phoenix-tracing -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install github/awesome-copilot phoenix-tracing --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/phoenix-tracing .agents/skills/phoenix-tracing && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "phoenix-tracing" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/phoenix-tracing into .agents/skills/phoenix-tracing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "phoenix-tracing", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add github/awesome-copilot --skill phoenix-tracing -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install github/awesome-copilot phoenix-tracing --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/phoenix-tracing .cursor/skills/phoenix-tracing && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "phoenix-tracing" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/phoenix-tracing into .cursor/skills/phoenix-tracing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "phoenix-tracing", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/github/awesome-copilot.git --path skills/phoenix-tracing

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add github/awesome-copilot --skill phoenix-tracing -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install github/awesome-copilot phoenix-tracing --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/phoenix-tracing .gemini/skills/phoenix-tracing && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "phoenix-tracing" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/phoenix-tracing into .gemini/skills/phoenix-tracing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "phoenix-tracing", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install github/awesome-copilot phoenix-tracing

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add github/awesome-copilot --skill phoenix-tracing -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/phoenix-tracing .github/skills/phoenix-tracing && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "phoenix-tracing" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/phoenix-tracing into .github/skills/phoenix-tracing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "phoenix-tracing", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add github/awesome-copilot --skill phoenix-tracing -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install github/awesome-copilot phoenix-tracing --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/phoenix-tracing .opencode/skills/phoenix-tracing && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "phoenix-tracing" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/phoenix-tracing into .opencode/skills/phoenix-tracing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "phoenix-tracing", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: phoenix-tracing
GitHub stars: 40k
Used in: 3 other repos
Token cost: ~1.6k tokens
SKILL.md length: 350 words
Files: 32 (incl. references)
Skills in repo: 417
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

OpenInference semantic conventions and instrumentation for Phoenix AI observability.

Works in 7 steps: Setup (START HERE) → Instrumentation → Span Types (with full attribute schemas) → …
Implementing LLM tracing
SKILL.md covers When to Apply, Reference Categories, Quick Reference and Common Workflows, plus 2 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Phoenix Tracing is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. OpenInference semantic conventions and instrumentation for Phoenix AI observability. Use when implementing LLM tracing, creating custom spans, or deploying to production.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 32 other files, including reference files (for example `README.md`, `references/annotations-overview.md` and `references/annotations-python.md`). Compatibility notes: Requires Phoenix server. Python skills need arize-phoenix-otel; TypeScript skills need @arizeai/phoenix-otel.

It sits in AI & LLM Engineering, covering LLM observability and Observability. It works with Python and TypeScript. The repository describes itself as: Community-contributed instructions, agents, skills, and configurations to help you make the most of GitHub Copilot. The licence is Apache-2.0.

When your agent uses it

Implementing LLM tracing
Creating custom spans
Deploying to production

Example prompts

“/phoenix-tracing”

Requirements

Python 3
Compatibility (from SKILL.md): Requires Phoenix server. Python skills need arize-phoenix-otel; TypeScript skills need @arizeai/phoenix-otel.

Workflow steps

7 steps, taken from the step headings in SKILL.md.

Setup (START HERE)
Instrumentation
Span Types (with full attribute schemas)
Organization
Enrichment
Production (CRITICAL)
Feedback

What it can do on your machine

Read from SKILL.md and the folder at commit 727ff2e. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
- arize-phoenix.readthedocs.io
- docs.arize.com
- github.com
- arize-ai.github.io
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Requires Phoenix server. Python skills need arize-phoenix-otel; TypeScript skills need @arizeai/phoenix-otel.
From compatibility in the SKILL.md frontmatter.

Context cost

Phoenix Tracing loads about 1.6k tokens when it runs, and up to ~22k if it reads all its reference files. Until then it costs about 47 tokens; SKILL.md has 350 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~47
When it runs · the whole SKILL.md, loaded when a task matches: ~1.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~22k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from github/awesome-copilot at commit 727ff2e, republished under its Apache-2.0 licence (© github). 350 words, ~1,608 tokens.

Download SKILL.mdSave it as .claude/skills/phoenix-tracing/SKILL.md (or your agent's skills folder). This skill also uses 31 other files; get the full folder from GitHub.

name: phoenix-tracing
description: OpenInference semantic conventions and instrumentation for Phoenix AI observability. Use when implementing LLM tracing, creating custom spans, or deploying to production.
compatibility: Requires Phoenix server. Python skills need arize-phoenix-otel; TypeScript skills need @arizeai/phoenix-otel.
license: Apache-2.0
metadata.author: oss@arize.com
metadata.version: 1.0.0
metadata.languages: Python, TypeScript

Phoenix Tracing

Comprehensive guide for instrumenting LLM applications with OpenInference tracing in Phoenix. Contains reference files covering setup, instrumentation, span types, and production deployment.

When to Apply

Reference these guidelines when:

Setting up Phoenix tracing (Python or TypeScript)
Creating custom spans for LLM operations
Adding attributes following OpenInference conventions
Deploying tracing to production
Querying and analyzing trace data

Reference Categories

Priority	Category	Description	Prefix
1	Setup	Installation and configuration	`setup-*`
2	Instrumentation	Auto and manual tracing	`instrumentation-*`
3	Span Types	9 span kinds with attributes	`span-*`
4	Organization	Projects and sessions	`projects-`, `sessions-`
5	Enrichment	Custom metadata	`metadata-*`
6	Production	Batch processing, masking	`production-*`
7	Feedback	Annotations and evaluation	`annotations-*`

Quick Reference

1. Setup (START HERE)

setup-python - Install arize-phoenix-otel, configure endpoint
setup-typescript - Install @arizeai/phoenix-otel, configure endpoint

2. Instrumentation

instrumentation-auto-python - Auto-instrument OpenAI, LangChain, etc.
instrumentation-auto-typescript - Auto-instrument supported frameworks
instrumentation-manual-python - Custom spans with decorators
instrumentation-manual-typescript - Custom spans with wrappers

3. Span Types (with full attribute schemas)

span-llm - LLM API calls (model, tokens, messages, cost)
span-chain - Multi-step workflows and pipelines
span-retriever - Document retrieval (documents, scores)
span-tool - Function/API calls (name, parameters)
span-agent - Multi-step reasoning agents
span-embedding - Vector generation
span-reranker - Document re-ranking
span-guardrail - Safety checks
span-evaluator - LLM evaluation

4. Organization

projects-python / projects-typescript - Group traces by application
sessions-python / sessions-typescript - Track conversations

5. Enrichment

metadata-python / metadata-typescript - Custom attributes

Show full SKILL.md (139 more words)Show less

6. Production (CRITICAL)

production-python / production-typescript - Batch processing, PII masking

7. Feedback

annotations-overview - Feedback concepts
annotations-python / annotations-typescript - Add feedback to spans

Reference Files

fundamentals-overview - Traces, spans, attributes basics
fundamentals-required-attributes - Required fields per span type
fundamentals-universal-attributes - Common attributes (user.id, session.id)
fundamentals-flattening - JSON flattening rules

Common Workflows

Quick Start: setup-{lang} → instrumentation-auto-{lang} → Check Phoenix
Custom Spans: setup-{lang} → instrumentation-manual-{lang} → span-{type}
Session Tracking: sessions-{lang} for conversation grouping patterns
Production: production-{lang} for batching, masking, and deployment

How to Use This Skill

Navigation Patterns:

bash

# By category prefix
references/setup-*              # Installation and configuration
references/instrumentation-*    # Auto and manual tracing
references/span-*               # Span type specifications
references/sessions-*           # Session tracking
references/production-*         # Production deployment
references/fundamentals-*       # Core concepts
references/attributes-*         # Attribute specifications

# By language
references/*-python.md          # Python implementations
references/*-typescript.md      # TypeScript implementations

Reading Order:

Start with setup-{lang} for your language
Choose instrumentation-auto-{lang} OR instrumentation-manual-{lang}
Reference span-{type} files as needed for specific operations
See fundamentals-* files for attribute specifications

References

Phoenix Documentation:

Python API Documentation:

Python OTEL Package - arize-phoenix-otel API reference
Python Client Package - arize-phoenix-client API reference

TypeScript API Documentation:

TypeScript Packages - @arizeai/phoenix-otel, @arizeai/phoenix-client, and other TypeScript packages

Files

SKILL.md and 31 other files (references) in skills/phoenix-tracing of github/awesome-copilot.

SKILL.md
README.md
references/annotations-overview.md
references/annotations-python.md
references/annotations-typescript.md
references/fundamentals-flattening.md
references/fundamentals-overview.md
references/fundamentals-required-attributes.md
references/fundamentals-universal-attributes.md
references/instrumentation-auto-python.md
references/instrumentation-auto-typescript.md
references/instrumentation-manual-python.md
references/instrumentation-manual-typescript.md
references/metadata-python.md
references/metadata-typescript.md
references/production-python.md
references/production-typescript.md
references/projects-python.md
references/projects-typescript.md
references/sessions-python.md
… and 12 more

Open the folder on GitHubat commit 727ff2e

Used in 3 other repositories

We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 3 other GitHub owners. This page covers the copy in github/awesome-copilot, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Phoenix Tracing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Phoenix Tracing compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Phoenix Tracing this skillgithub/awesome-copilot	40k	3 repos	~1.6k	Automated safety check: Pass	Apache-2.0	today
Failproof AI SDK IntegrationFailproofAI/failproofai	5.3k	—	~6k	Automated safety check: Pass	Custom licence	yesterday
Logfire Instrumentationpydantic/skills	140	—	~6.1k	Automated safety check: Pass	MIT	6 days ago
Langchain Dependencieslangchain-ai/langchain-skills	1.3k	1 repos	~3.6k	Automated safety check: Pass	MIT	2 days ago
Opik External Integrationscomet-ml/opik	22k	—	~1.3k	Automated safety check: Pass	Apache-2.0	today
Opik SDK Integrationscomet-ml/opik	22k	—	~1.4k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Failproof AI SDK Integration
FailproofAI/failproofai
Helps instrument a custom Python or TypeScript agent to record events for Failproof AI, verify what gets written, and run an evaluator worker that scores the runs.
5.3k GitHub stars~6k tokensUpdated yesterday
AI & LLM EngineeringAuto-check passed
Logfire Instrumentation
pydantic/skills
Official
Add Pydantic Logfire observability to application code — traces, logs, metrics, and AI/agent spans.
140 GitHub stars~6.1k tokensUpdated 6 days ago
AI & LLM EngineeringAuto-check passed
Langchain Dependencies
langchain-ai/langchain-skills
Official
INVOKE THIS SKILL when setting up a new project or when asked about package versions, installation, or dependency management for LangChain, LangGraph, LangSmith, or Deep Agents.
1.3k GitHub starsUsed in 1 repo~3.6k tokens
AI & LLM EngineeringAuto-check passed
Opik External Integrations
comet-ml/opik
Builds Opik tracing integrations that live outside the Opik repository, either as standalone opik-* packages or as contributions into projects such as LiteLLM or Dify.
22k GitHub stars~1.3k tokensUpdated today
AI & LLM EngineeringAuto-check passed
Opik SDK Integrations
comet-ml/opik
Builds, updates and verifies integrations inside the Opik Python and TypeScript SDKs so users can trace a framework or provider with one call.
22k GitHub stars~1.4k tokensUpdated today
AI & LLM EngineeringAuto-check passed
Phoenix Integration Snippets
Arize-ai/phoenix
Generates onboarding code snippets for Phoenix tracing integrations and wires them into the project onboarding UI.
12k GitHub stars~1.4k tokensUpdated today
AI & LLM EngineeringAuto-check passed

Questions about Phoenix Tracing

What does Phoenix Tracing do?

OpenInference semantic conventions and instrumentation for Phoenix AI observability. Phoenix Tracing is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. OpenInference semantic conventions and instrumentation for Phoenix AI observability.

When should I use Phoenix Tracing?

Phoenix Tracing fits situations like: implementing LLM tracing; creating custom spans; deploying to production.

How do I install Phoenix Tracing in Claude Code?

Run `npx skills add github/awesome-copilot --skill phoenix-tracing -a claude-code`. Or copy the skill folder (skills/phoenix-tracing in github/awesome-copilot) into .claude/skills/phoenix-tracing in your project. Claude Code loads it when a task matches its description.

How do I install Phoenix Tracing in Codex?

Run `npx skills add github/awesome-copilot --skill phoenix-tracing -a codex`. Or copy the skill folder (skills/phoenix-tracing in github/awesome-copilot) into .agents/skills/phoenix-tracing in your project. Codex loads it when a task matches its description.

Can I use Phoenix Tracing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add github/awesome-copilot --skill phoenix-tracing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/phoenix-tracing, .gemini/skills/phoenix-tracing, .github/skills/phoenix-tracing and .opencode/skills/phoenix-tracing in your project.

What does Phoenix Tracing need to run?

SKILL.md names no scripts, command-line tools or credentials: Phoenix Tracing is instructions for the agent only. Our summary lists: Python 3. Compatibility (from SKILL.md): Requires Phoenix server. Python skills need arize-phoenix-otel; TypeScript skills need @arizeai/phoenix-otel..

Does Phoenix Tracing access the network?

SKILL.md names 4 domains. As links in the text: arize-phoenix.readthedocs.io, docs.arize.com, github.com and arize-ai.github.io. This is read from the text; nothing was executed.

Is Phoenix Tracing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Phoenix Tracing use?

Phoenix Tracing is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Phoenix Tracing use?

About 1.6k tokens (SKILL.md is roughly 6.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 20k tokens, read only when the agent opens those files.

What are the alternatives to Phoenix Tracing?

Skills that share tags, products or a category with Phoenix Tracing: Failproof AI SDK Integration (FailproofAI/failproofai, 5.3k stars), Logfire Instrumentation (pydantic/skills, 140 stars), Langchain Dependencies (langchain-ai/langchain-skills, 1.3k stars) and Opik External Integrations (comet-ml/opik, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Phoenix Tracing?

github (a GitHub organization, an official publisher) maintains it in github/awesome-copilot, which has 39,748 GitHub stars. The repository holds 417 skills in this directory. The repository was last updated on October 7, 2026.

Source: github/awesome-copilot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Phoenix Tracing

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Compatibility

Context cost

Safety

SKILL.md

Phoenix Tracing

When to Apply

Reference Categories

Quick Reference

1. Setup (START HERE)

2. Instrumentation

3. Span Types (with full attribute schemas)

4. Organization

5. Enrichment

6. Production (CRITICAL)

7. Feedback

Reference Files

Common Workflows

How to Use This Skill

References

Files

Used in 3 other repositories

Compare with similar skills

Similar skills

More from github/awesome-copilot

Related

Questions about Phoenix Tracing