arize-link
Generates deep links to the Arize UI for projects, traces, spans, sessions, datasets, experiments, labeling queues, evaluators, and annotation configs. Discovers organization and project IDs with the ax CLI and produces clickable URLs for sharing Arize resources with team members. Use when the user wants to link to or open a project, trace, span, session, dataset, experiment, evaluator, or annotation config in the Arize UI.
- Installs
- 3.1K
- Last 24h
- +15
- Trending rank
- #6960
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/arize-ai/arize-skills --skill arize-link- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads arize-link automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Arize Link
Generate deep links to the Arize UI for projects, traces, spans, sessions, datasets, experiments, labeling queues, evaluators, and annotation configs.
When to Use
- User wants a link to a project, trace, span, session, dataset, labeling queue, evaluator, or annotation config
- You have IDs from exported data or logs and need to link back to the UI
- User asks to "open" or "view" any of the above in Arize
Required Inputs
Collect from the user, context (exported trace data or parsed URLs), or the ax CLI:
| Always required | Resource-specific |
|---|---|
org_id (base64) | project_id + trace_id [+ span_id] — trace/span |
space_id (base64) | project_id + session_id — session |
dataset_id — dataset | |
dataset_id + experiment_id (one or more) — experiment or comparison | |
experiment_id — experiment with no dataset | |
queue_id — specific queue (omit for list) | |
evaluator_id [+ version] — evaluator |
Discover organization and project IDs
Prefer the CLI over asking the user for IDs that it can provide:
ax organizations list --output json
Use .organizations[].id for the organization ID. If more than one organization is returned, match the user-provided organization name or ask them to choose.
To discover a project ID, list projects in the relevant space:
ax projects list --space "{space_name_or_id}" --limit 100 --output json
Use the matching project's id; its space_id supplies the space ID required in the URL. The command accepts a space name or ID; if no space is known, run ax projects list --limit 100 --output json and select the matching project.
To discover experiment IDs, list the experiments on the dataset; each has an id and a dataset_id:
ax experiments list --dataset "{dataset_name_or_id}" --space "{space_name_or_id}" --output json
All path IDs must be base64-encoded (characters: A-Za-z0-9+/=). A raw numeric ID produces a valid-looking URL that 404s. If the user provides a number, ask them to copy the ID directly from their Arize browser URL (https://app.arize.com/organizations/{org_id}/spaces/{space_id}/…). If you have a raw internal ID (e.g. Organization:1:abC1), base64-encode it before inserting into the URL.
URL Templates
Base URL: https://app.arize.com (override for on-prem)
Project:
{base_url}/organizations/{org_id}/spaces/{space_id}/projects/{project_id}
Trace (add &selectedSpanId={span_id} to highlight a specific span):
{base_url}/organizations/{org_id}/spaces/{space_id}/projects/{project_id}?selectedTraceId={trace_id}&queryFilterA=&selectedTab=llmTracing&timeZoneA=America%2FLos_Angeles&startA={start_ms}&endA={end_ms}&envA=tracing&modelType=generative_llm
Session:
{base_url}/organizations/{org_id}/spaces/{space_id}/projects/{project_id}?selectedSessionId={session_id}&queryFilterA=&selectedTab=llmTracing&timeZoneA=America%2FLos_Angeles&startA={start_ms}&endA={end_ms}&envA=tracing&modelType=generative_llm
Dataset (selectedTab: examples or experiments):
{base_url}/organizations/{org_id}/spaces/{space_id}/datasets/{dataset_id}?selectedTab=examples
Experiment (repeat experimentId to compare experiments side by side):
{base_url}/organizations/{org_id}/spaces/{space_id}/datasets/{dataset_id}/experiments/compare?experimentId={experiment_id}
{base_url}/organizations/{org_id}/spaces/{space_id}/datasets/{dataset_id}/experiments/compare?experimentId={experiment_id_a}&experimentId={experiment_id_b}
Experiment with no dataset:
{base_url}/organizations/{org_id}/spaces/{space_id}/experiments/{experiment_id}
URL-encode experiment IDs (= → %3D, + → %2B, / → %2F).
Queue list / specific queue:
{base_url}/organizations/{org_id}/spaces/{space_id}/queues
{base_url}/organizations/{org_id}/spaces/{space_id}/queues/{queue_id}
Evaluator (omit ?version=… for latest):
{base_url}/organizations/{org_id}/spaces/{space_id}/evaluators/{evaluator_id}
{base_url}/organizations/{org_id}/spaces/{space_id}/evaluators/{evaluator_id}?version={version_url_encoded}
The version value must be URL-encoded (e.g., trailing = → %3D).
Annotation configs:
{base_url}/organizations/{org_id}/spaces/{space_id}/annotation-configs
Time Range
CRITICAL: startA and endA (epoch milliseconds) are required for trace/span/session links — omitting them defaults to the last 7 days and will show "no recent data" if the trace falls outside that window.
Priority order:
- User-provided URL — extract and reuse
startA/endAdirectly. - Span
start_time— pad ±1 day (or ±1 hour for a tighter window). - Fallback — last 90 days (
now - 90dtonow).
Prefer tight windows; 90-day windows load slowly.
Instructions
- Gather IDs from user, exported data, URL context, or the CLI. Use
ax organizations list --output jsonto obtainorg_id; useax projects listto obtainproject_idwhen needed. - Verify all path IDs are base64-encoded.
- Determine
startA/endAusing the priority order above for trace, span, and session links. - Substitute into the appropriate template and present as a clickable markdown link.
Troubleshooting
| Problem | Solution |
|---|---|
| "No data" / empty view | Trace outside time window — widen startA/endA (±1h → ±1d → 90d). |
| 404 | ID wrong or not base64. Re-check org_id with ax organizations list --output json, project_id with ax projects list, and space_id from the browser URL. |
| Span not highlighted | span_id may belong to a different trace. Verify against exported span data. |
org_id unknown | Run ax organizations list --output json and use .organizations[].id. If the CLI cannot access the organization, ask the user to copy it from their Arize browser URL. |
Related Skills
- arize-trace: Export spans to get
trace_id,span_id, andstart_time.
Examples
See references/EXAMPLES.md for a complete set of concrete URLs for every link type.
FAQ
What does the arize-link skill do?
Generates deep links to the Arize UI for projects, traces, spans, sessions, datasets, experiments, labeling queues, evaluators, and annotation configs. Discovers organization and project IDs with the ax CLI and produces clickable URLs for sharing Arize resources with team members. Use when the user wants to link to or open a project, trace, span, session, dataset, experiment, evaluator, or annotation config in the Arize UI.
How do I install arize-link?
Run npx skills add https://github.com/arize-ai/arize-skills --skill arize-link in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/arize-link/ (personal) or .claude/skills/arize-link/ (project).
Which AI agents can use arize-link?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is arize-link safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains arize-link?
It is published by arize-ai in arize-ai/arize-skills. It has 3,066 recorded installs.
More from arize-ai/arize-skills
arize-instrumentation
arize-ai/arize-skills
Adds Arize AX tracing to an LLM application for the first time. Detects the stack, routes to the single matching integration doc, wires auto-instrumentation after user confirmation, and verifies traces land. Use when the user wants to instrument their app, add tracing from scratch, set up LLM observability, integrate OpenTelemetry or openinference, or get started with Arize tracing.
arize-prompt-optimization
arize-ai/arize-skills
Optimizes, improves, and debugs LLM prompts using production trace data, evaluations, and annotations. Extracts prompts from spans, gathers performance signal, and runs a data-driven optimization loop using the ax CLI. Use when the user mentions optimize prompt, improve prompt, make AI respond better, improve output quality, prompt engineering, prompt tuning, or system prompt improvement.
arize-trace
arize-ai/arize-skills
Downloads, exports, and inspects existing Arize traces and spans to understand what an LLM app is doing or debug runtime issues. Covers exporting traces by ID, spans by ID, sessions by ID, and root-cause investigation using the ax CLI. Use when the user wants to look at existing trace data, see what their LLM app is doing, export traces, download spans, investigate errors, or analyze behavior regressions.
arize-experiment
arize-ai/arize-skills
Creates, runs, and analyzes Arize experiments for evaluating and comparing model performance. Covers experiment CRUD, exporting runs, comparing results, and evaluation workflows using the ax CLI. Use when the user mentions create experiment, run experiment, compare models, model performance, evaluate AI, experiment results, benchmark, A/B test models, or measure accuracy.
arize-dataset
arize-ai/arize-skills
Creates, manages, and queries Arize datasets and examples. Covers dataset CRUD, appending examples, exporting data, and file-based dataset creation using the ax CLI. Use when the user needs test data, evaluation examples, or mentions create dataset, list datasets, export dataset, append examples, dataset version, golden dataset, or test set.
arize-evaluator
arize-ai/arize-skills
Handles LLM-as-judge and code evaluator workflows on Arize including creating/updating evaluators, running evaluations on spans or experiments, managing tasks, trigger-run operations, column mapping, and continuous monitoring. Use when the user mentions create evaluator, LLM judge, code evaluator, hallucination, faithfulness, correctness, relevance, run eval, score spans, score experiment, trigger-run, column mapping, continuous monitoring, or improve evaluator prompt.
Popular frontend & design skills
setup-matt-pocock-skills
mattpocock/skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
frontend-design
anthropics/skills
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
hyperframes-animation
heygen-com/hyperframes
All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.
prototype
mattpocock/skills
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
hyperframes-core
heygen-com/hyperframes
The HyperFrames composition contract — build one renderable project. Use for composition structure, the data- timing attributes, class="clip", tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.
vercel-react-best-practices
vercel-labs/agent-skills
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.