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.
Generates onboarding code snippets for Phoenix tracing integrations and wires them into the project onboarding UI.
Install Phoenix Integration Snippets
$ npx skills add Arize-ai/phoenix --skill phoenix-integration-snippets -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Arize-ai/phoenix phoenix-integration-snippets --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Arize-ai/phoenix.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/phoenix-integration-snippets .claude/skills/phoenix-integration-snippets && rm -rf skills-srcUse ~/.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/
Install the "phoenix-integration-snippets" agent skill from https://github.com/Arize-ai/phoenix/tree/main/.agents/skills/phoenix-integration-snippets into .claude/skills/phoenix-integration-snippets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "phoenix-integration-snippets", 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 install https://github.com/Arize-ai/phoenix/tree/main/.agents/skills/phoenix-integration-snippetsType 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.
$ npx skills add Arize-ai/phoenix --skill phoenix-integration-snippets -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Arize-ai/phoenix phoenix-integration-snippets --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Arize-ai/phoenix.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/phoenix-integration-snippets .agents/skills/phoenix-integration-snippets && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "phoenix-integration-snippets" agent skill from https://github.com/Arize-ai/phoenix/tree/main/.agents/skills/phoenix-integration-snippets into .agents/skills/phoenix-integration-snippets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "phoenix-integration-snippets", 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.
$ npx skills add Arize-ai/phoenix --skill phoenix-integration-snippets -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Arize-ai/phoenix phoenix-integration-snippets --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Arize-ai/phoenix.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/phoenix-integration-snippets .cursor/skills/phoenix-integration-snippets && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "phoenix-integration-snippets" agent skill from https://github.com/Arize-ai/phoenix/tree/main/.agents/skills/phoenix-integration-snippets into .cursor/skills/phoenix-integration-snippets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "phoenix-integration-snippets", 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 https://github.com/Arize-ai/phoenix.git --path .agents/skills/phoenix-integration-snippets--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Arize-ai/phoenix --skill phoenix-integration-snippets -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Arize-ai/phoenix phoenix-integration-snippets --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Arize-ai/phoenix.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/phoenix-integration-snippets .gemini/skills/phoenix-integration-snippets && rm -rf skills-srcUse ~/.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/
Install the "phoenix-integration-snippets" agent skill from https://github.com/Arize-ai/phoenix/tree/main/.agents/skills/phoenix-integration-snippets into .gemini/skills/phoenix-integration-snippets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "phoenix-integration-snippets", 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.
$ gh skill install Arize-ai/phoenix phoenix-integration-snippetsInstalls 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).
$ npx skills add Arize-ai/phoenix --skill phoenix-integration-snippets -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Arize-ai/phoenix.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/phoenix-integration-snippets .github/skills/phoenix-integration-snippets && rm -rf skills-srcUse ~/.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/
Install the "phoenix-integration-snippets" agent skill from https://github.com/Arize-ai/phoenix/tree/main/.agents/skills/phoenix-integration-snippets into .github/skills/phoenix-integration-snippets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "phoenix-integration-snippets", 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.
$ npx skills add Arize-ai/phoenix --skill phoenix-integration-snippets -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Arize-ai/phoenix phoenix-integration-snippets --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Arize-ai/phoenix.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/phoenix-integration-snippets .opencode/skills/phoenix-integration-snippets && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "phoenix-integration-snippets" agent skill from https://github.com/Arize-ai/phoenix/tree/main/.agents/skills/phoenix-integration-snippets into .opencode/skills/phoenix-integration-snippets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "phoenix-integration-snippets", 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-integration-snippets- GitHub stars
- 12k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 631 words
- Files
- 1
- Skills in repo
- 39
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Generates onboarding code snippets for Phoenix tracing integrations and wires them into the project onboarding UI.
- Works in 2 steps: Add implementation function → Register the integration
- Asked to create onboarding code
- SKILL.md covers Workflow, Snippet Format, Adding to the Onboarding UI and Testing
- Reaches github.com
What it does
Phoenix Integration Snippets is an agent skill from Arize-ai/phoenix. Generates onboarding code snippets for Phoenix tracing integrations and wires them into the project onboarding UI. Produces install dependencies and implementation sections for SDKs like OpenAI, LangChain, Vercel AI SDK, and others. Supports Python and TypeScript. Use when asked to create onboarding code, tracing setup snippets, quickstart examples, or getting-started code for a framework integration.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in AI & LLM Engineering, covering LLM observability and Building AI agents. It works with OpenAI, LangChain, Vercel AI SDK and Python. The repository describes itself as: AI Observability & Evaluation. The licence is Apache-2.0.
When your agent uses it
- Asked to create onboarding code
- Tracing setup snippets
- Quickstart examples
- Getting-started code for a framework integration
Example prompts
- “Use the phoenix-integration-snippets skill to generate onboarding code snippets for Phoenix tracing integrations and wires them into the project…”
- “/phoenix-integration-snippets”
Requirements
- Python 3
Workflow steps
2 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 52f76fc. 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 typescript).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
github.com
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.
Context cost
Phoenix Integration Snippets loads about 1.4k tokens when it runs. Until then it costs about 108 tokens; SKILL.md has 631 words of instructions outside code blocks.
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 Arize-ai/phoenix at commit 52f76fc, republished under its Apache-2.0 licence (© Arize-ai). 631 words, ~1,450 tokens.
Download SKILL.mdSave it as
.claude/skills/phoenix-integration-snippets/SKILL.md (or your agent's skills folder).- name
- phoenix-integration-snippets
- description
- Generates onboarding code snippets for Phoenix tracing integrations and wires them into the project onboarding UI. Produces install dependencies and implementation sections for SDKs like OpenAI, LangChain, Vercel AI SDK, and others. Supports Python and TypeScript. Use when asked to create onboarding code, tracing setup snippets, quickstart examples, or getting-started code for a framework integration.
- license
- Apache-2.0
- metadata.author
- oss@arize.com
- metadata.version
- 2.0.1
- metadata.languages
- Python, TypeScript
- metadata.internal
- true
Phoenix Integration Snippets
Generate onboarding snippets (install + implementation) for Phoenix tracing integrations and add them to the project onboarding UI.
Workflow
Copy this checklist and track progress:
- [ ] 1. Research: read integration docs and OpenInference repo
- [ ] 2. Determine language support (Python, TypeScript, or both)
- [ ] 3. Generate snippets following the format below
- [ ] 4. Test every language variant against Phoenix
- [ ] 5. Wire into the onboarding UI
- [ ] 6. Report results with links to trace pagesStep 1: Research. Read the relevant file in docs/phoenix/integrations/ for the framework. Also check the OpenInference repo for example code: https://github.com/Arize-ai/openinference
Step 4: Test. See Testing below. Only proceed to wiring into the UI when traces are confirmed.
Step 5: Wire into the onboarding UI. After adding docsHref and githubHref, verify every URL returns HTTP 200 before committing. For GitHub links, prefer the OpenInference repo (https://github.com/Arize-ai/openinference/tree/main/...).
Step 6: Report. Provide clickable links to the Phoenix project pages (e.g., http://localhost:6006/projects/<base64-id>/traces).
Snippet Format
Each snippet has two parts:
Packages: Array of package names. Order: phoenix-otel first, then instrumentation package, then SDK.
Do not assume the framework package bundles its model provider SDK. In a clean env, verify the exact imports used by the snippet; if the framework's OpenAI/Gemini/etc. adapter requires a separate SDK package, include it explicitly in packages.
Implementation: Working, copy-pasteable code that produces at least one trace. 10-20 lines, meaningful example prompt, no print/log statements.
Adding to the Onboarding UI
1. Add implementation function
Directory: js/app/src/components/project/integrationSnippets/ — read existing files to match conventions.
Whether a snippet passes an endpoint depends on what consumes it. Either way the value comes from PHOENIX_COLLECTOR_ENDPOINT, which the onboarding UI displays alongside the snippet.
register()-based snippets — do NOT passendpoint/url. Bothregisterfunctions readPHOENIX_COLLECTOR_ENDPOINTand derive the OTLP target from it.Verbatim exporters — anything that POSTs to exactly the URL it is handed, such as
@mastra/arize'sArizeExporteror a bareOTLPTraceExporter, MUST receive the full OTLP URL explicitly, built from the same variable:typescript endpoint: `${process.env.PHOENIX_COLLECTOR_ENDPOINT ?? "http://localhost:6006"}/v1/traces`,These exporters do not read the environment and do not append the OTLP path. Omitting the endpoint or passing a bare base URL loses every span, with no error.
Python: Use auto_instrument=True — no manual instrumentor calls. SDK imports must come after register().
Exception: if the framework emits native OpenTelemetry spans and uses a mutating span processor, start with register(...) so Phoenix becomes the global provider the framework will use. Then add the mutating processor so it replaces Phoenix's default processor, and add the Phoenix exporter back after it.
TypeScript: ESM imports are hoisted so import ordering doesn't matter. await provider.forceFlush() is required in short-lived scripts.
Show full SKILL.md (251 more words)Show less
2. Register the integration
File: js/app/src/pages/project/integrationRegistry.tsx
Import your function and add an entry to ONBOARDING_INTEGRATIONS. Pass snippet functions as direct references (they match the getImplementationCode type in integrationDefinitions.ts).
Testing
Test snippets as written — the exact code the user will see in the onboarding UI. If any modification is required to make a snippet work, that is a bug.
Isolated test environments
Create a fresh environment per integration with only the packages from that snippet's packages array. This prevents false positives from cross-contamination (e.g., an installed openinference-instrumentation-openai producing extra traces when testing a LangChain snippet).
Set PHOENIX_COLLECTOR_ENDPOINT and run the snippet code verbatim.
Use a fresh Phoenix project name per test run. Reusing an existing project can mask failures by making old traces look like the new snippet worked.
Validation checklist
For each snippet, verify:
- No export errors (no
405, noFailed to export span batch) - Traces appear in Phoenix under the expected project name
- Trace kind and structure match expectations (e.g., LangChain shows
chainspans, not just barellmspans) - Only one top-level trace per invocation (multiple top-level traces suggest instrumentor cross-contamination)
When a snippet doesn't work as-is
If you must modify the snippet code to get traces flowing, do not silently work around it and continue. Instead:
- Fix the snippet if the change is small and clearly correct (e.g., a typo, missing import)
- Flag to the user if the fix requires a design decision (e.g., the SDK doesn't support env-var-based config, or auto-instrumentation doesn't work for this framework)
© Arize-ai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/phoenix-integration-snippets of Arize-ai/phoenix.
Open the folder on GitHubat commit 52f76fc
Compare with similar skills
Phoenix Integration Snippets 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Phoenix Integration Snippets this skillArize-ai/phoenix | 12k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Failproof AI SDK IntegrationFailproofAI/failproofai | 5.3k | — | ~6k | Automated safety check: Pass | Custom licence | |
| Add Example AgentGetBindu/Bindu | 10k | — | ~1.1k | Automated safety check: Notes | Custom licence | |
| AI Observability Langchain PythonJwuthri/Tracely-ai | 1.5k | — | ~2.2k | Automated safety check: Pass | MIT | |
| Tool Designagentailor/fullstack-langgraph-nextjs-agent | 132 | — | ~3.2k | Automated safety check: Pass | MIT | |
| Langchain Dependencieslangchain-ai/langchain-skills | 1.3k | — | ~3.6k | Automated safety check: Pass | MIT |
Similar skills
Add Example Agent
GetBindu/Bindu
Add a new self-contained example agent under examples/. An agent skill from GetBindu/Bindu.
AI Observability Langchain Python
Jwuthri/Tracely-ai
PostHog AI Observability integration for LangChain (Python). An agent skill from Jwuthri/Tracely-ai.
Tool Design
agentailor/fullstack-langgraph-nextjs-agent
Design and verify tools that AI agents can actually use — for any framework or language (MCP servers, LangChain/LangGraph, function-calling, raw JSON schema; TypeScript, Python, or otherwise).
- Official
Langchain Dependencies
langchain-ai/langchain-skills
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.
Langgraph Testing Evaluation
soba-labs/langchain-agent-skills
A skill your agent uses when you need to test or evaluate LangGraph/LangChain agents: writing unit or integration tests, generating test scaffolds, mocking LLM/tool behavior, running trajectory…
More from Arize-ai/phoenix
All 39 skills in this repoHarbor Exec
Arize-ai/phoenix
A skill your agent uses when working with Harbor's harbor exec CLI workflow: compiling files, directories, or globs into Harbor tasks; running map jobs; configuring artifacts and existence-only…
Mintlify
Arize-ai/phoenix
Build and maintain documentation sites with Mintlify. An agent skill from Arize-ai/phoenix.
Phoenix Frontend
Arize-ai/phoenix
Frontend development guidelines for the Phoenix AI observability platform.
Phoenix Graphql
Arize-ai/phoenix
Write efficient GraphQL queries against the Phoenix API. An agent skill from Arize-ai/phoenix.
Phoenix Server
Arize-ai/phoenix
Backend development guide for the Phoenix AI observability platform (Strawberry GraphQL, SQLAlchemy async, FastAPI).
Phoenix Storybook
Arize-ai/phoenix
Conventions for creating, modifying, and reviewing production-faithful Storybook stories in the Phoenix frontend (js/app/stories, js/app/.storybook).
Related
Categories
Questions about Phoenix Integration Snippets
What does Phoenix Integration Snippets do?
Generates onboarding code snippets for Phoenix tracing integrations and wires them into the project onboarding UI. Phoenix Integration Snippets is an agent skill from Arize-ai/phoenix. Generates onboarding code snippets for Phoenix tracing integrations and wires them into the project onboarding UI.
When should I use Phoenix Integration Snippets?
Phoenix Integration Snippets fits situations like: asked to create onboarding code; tracing setup snippets; quickstart examples; getting-started code for a framework integration.
How do I install Phoenix Integration Snippets in Claude Code?
Run `npx skills add Arize-ai/phoenix --skill phoenix-integration-snippets -a claude-code`. Or copy the skill folder (.agents/skills/phoenix-integration-snippets in Arize-ai/phoenix) into .claude/skills/phoenix-integration-snippets in your project. Claude Code loads it when a task matches its description.
How do I install Phoenix Integration Snippets in Codex?
Run `npx skills add Arize-ai/phoenix --skill phoenix-integration-snippets -a codex`. Or copy the skill folder (.agents/skills/phoenix-integration-snippets in Arize-ai/phoenix) into .agents/skills/phoenix-integration-snippets in your project. Codex loads it when a task matches its description.
Can I use Phoenix Integration Snippets 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 Arize-ai/phoenix --skill phoenix-integration-snippets -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-integration-snippets, .gemini/skills/phoenix-integration-snippets, .github/skills/phoenix-integration-snippets and .opencode/skills/phoenix-integration-snippets in your project.
What does Phoenix Integration Snippets need to run?
SKILL.md names no scripts, command-line tools or credentials: Phoenix Integration Snippets is instructions for the agent only. Our summary lists: Python 3.
Does Phoenix Integration Snippets access the network?
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Phoenix Integration Snippets 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 Integration Snippets use?
Phoenix Integration Snippets 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 Integration Snippets use?
About 1.4k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Phoenix Integration Snippets?
Skills that share tags, products or a category with Phoenix Integration Snippets: Failproof AI SDK Integration (FailproofAI/failproofai, 5.3k stars), Add Example Agent (GetBindu/Bindu, 10k stars), AI Observability Langchain Python (Jwuthri/Tracely-ai, 1.5k stars) and Tool Design (agentailor/fullstack-langgraph-nextjs-agent, 132 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Phoenix Integration Snippets?
Arize-ai (a GitHub organization) maintains it in Arize-ai/phoenix, which has 11,764 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on October 9, 2026.
Source: Arize-ai/phoenix on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.