About this skill

Problem

If a project needs Arize Phoenix, directly handling call conventions, parameter setup, or integration points can couple business code to external service details. This skill introduces arize-phoenix-wrap as a thin wrapper layer, useful when you want a consistent entry point and less duplicated glue code.

How It Works and Limits

Based on SKILL.md, it is positioned as an Arize Phoenix wrapper. Its core role is not to replace Phoenix, but to provide a wrapping layer around it. In practice, focus on:
- Entry-point consolidation: route Phoenix calls through one wrapper module instead of scattered logic.
- Version alignment: the declared version is 1.0.0, so confirm compatibility with the Arize Phoenix version in use.
- Capability boundary: the source does not list concrete APIs, so actual behavior depends on the wrapped Phoenix interface; do not assume extra evaluation, visualization, or deployment features.

It fits projects that already use Phoenix and want a simpler integration path. If Phoenix is not already in place, verify the target platform and permissions first.

Screenshots

Use Cases

Report traces to Phoenix from an LLM app with less SDK init and parameter boilerplate
Standardize Phoenix reporting across multiple microservices via a shared wrapper layer
Attach Phoenix tracing to a local LLM pipeline during debugging without writing setup code
Onboard new engineers by exposing a Phoenix wrapper before they read the raw API docs

Best For

Backend engineers adding observability to LLM apps who want a low-friction Phoenix hookup
Platform engineers maintaining multiple AI services who need a single Phoenix reporting path
Research engineers running local LLM eval pipelines who need quick trace attachment
New engineers onboarding into a codebase with Phoenix dependencies who want a wrapper first