arize-link
Skill72 starsChanged 37 days agoMITView on GitHub
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.
2 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- github/awesome-copilotedited, first seen Oct 25, 2026
- JustineDevs/premortemedited, first seen Jun 9, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- github/awesome-copilot★ 41k85% same
- JustineDevs/premortem★ 285% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- arize-adminSkill
- arize-ai-provider-integrationSkill
- arize-annotationSkill
- arize-compliance-auditSkill
- arize-datasetSkill
- arize-evaluatorSkill
- arize-experimentSkill
- arize-instrumentation-healthSkill
- arize-instrumentationSkill
- arize-migrate-braintrustSkill
- arize-migrate-langfuseSkill
- arize-migrate-langsmithSkill
- arize-phoenix-migrationSkill
- arize-prompt-optimizationSkill
- arize-promptsSkill
- arize-span-routingSkill
- arize-traceSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 35
Prefer the CLI over asking the user for IDs that it can provide:
- Very specific: line 41
Use .organizations[].id for the organization ID.
- Very specific: line 49
Use the matching project's id.
- Distinctive: line 122
Prefer tight windows; 90-day windows load slowly.
- Distinctive: line 127
Verify all path IDs are base64-encoded.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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 jsonUse .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 jsonUse 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 jsonAll 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_llmSession:
{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_llmDataset (selectedTab: examples or experiments):
{base_url}/organizations/{org_id}/spaces/{space_id}/datasets/{dataset_id}?selectedTab=examplesExperiment (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-configsTime 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

