What problem does it solve?
Writing GraphQL queries against the Phoenix API without schema knowledge leads to failed lookups, full introspection round trips, and inefficient queries. This Skill provides the schema entrypoints, entity field references, and query patterns needed to answer data questions or build integrations against Phoenix without introspecting the schema.
Core Features & Use Cases
- Schema entrypoints and lookup rules: Covers
node(id:) global lookups, Relay connections with filters, and the exact by-name/by-id helpers that exist, including which helpers do not exist (e.g. no getDatasetByName).
- Per-entity reference files: Detailed field references for projects, spans, traces, sessions, datasets, experiments, prompts, and annotations, loaded on demand.
- Efficiency and pagination patterns: Relay pagination, query variables, aliased batching, truncated span payloads, and the span/session filter DSL.
- Use Case: Ask which LLM spans errored in the last hour, and the Skill produces a filtered
Project.spans query with filterCondition: "span_kind == 'LLM' and status_code == 'ERROR'" ready to run via phoenix-gql or curl.
Quick Start
Ask the agent to write a GraphQL query that lists the 20 slowest root spans in a Phoenix project, and it will load this skill and return a ready-to-run query with variables and pagination handling.