Skip to main content
skill official · GitHub

arize-link · github — GitHub Copilot skill: what it does, how to install

Builds deep links to the Arize UI for traces, spans, sessions, datasets, and evaluators. Convenient when sharing observability records with teammates.

Install into GitHub Copilot · Skills CLI (Vercel) All methods and platforms ↓
npx skills add github/awesome-copilot --skill arize-link
Open on GitHub

What arize-link does

This skill creates clickable links pointing to https://app.arize.com or custom on-prem Arize hostnames. It constructs URLs for traces, highlighted spans, sessions, datasets, labeling queues, and evaluators.

All path IDs such as org_id and space_id must use base64 encoding. A plain numeric ID produces a link that returns a 404 error. The skill handles raw internal IDs by encoding them before injecting them into URL parameters.

Trace and session links require epoch millisecond timestamps in startA and endA. Omitting these values makes the interface fall back to a 7-day window. Older records will simply show no data.

What it helps with

  • generate deep links to Arize traces and highlighted spans
  • share specific dataset or evaluation queue views via URL
  • set explicit epoch time windows to avoid empty trace views
  • format base64 identifiers required by Arize routing

Example prompts for the agent

  • Generate an Arize link for trace tr_456 in project proj_123
  • Create an Arize URL for session sess_789 covering the last 24 hours
  • Link to evaluator eval_abc version v1

How to install arize-link

1Skills CLI (Vercel)

npx skills add github/awesome-copilot --skill arize-link

2GitHub CLI

gh skill install github/awesome-copilot arize-link

3Manually: put the files in place

.github/skills/arize-link/SKILL.md

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about arize-link

How do I install arize-link for GitHub Copilot?

Run gh skill install github/awesome-copilot arize-link. You can also install it using npx skills add github/awesome-copilot --skill arize-link.

What does arize-link do?

It creates clickable deep links to specific Arize UI resources like traces, spans, sessions, and datasets using IDs from logs or exports.

Why does an Arize deep link return a 404 or empty view?

A 404 occurs when path IDs are plain numbers rather than base64 strings. An empty view happens when startA and endA time windows exclude the trace.

Source text

SKILL.md · MIT
---
name: arize-link
description: Generates deep links to the Arize UI for traces, spans, sessions, datasets, labeling queues, evaluators, and annotation configs. Produces clickable URLs for sharing Arize resources with team members. Use when the user wants to link to or open a trace, span, session, dataset, evaluator, or annotation config in the Arize UI.
metadata:
  author: arize
  version: "1.0"
---

# Arize Link

Generate deep links to the Arize UI for traces, spans, sessions, datasets, labeling queues, evaluators, and annotation configs.

## When to Use

- User wants a link to a 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 or context (exported trace data, parsed URLs):

| 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 |
| | `queue_id` — specific queue (omit for list) |
| | `evaluator_id` [+ `version`] — evaluator |

**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)

**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
```

**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:**
1. **User-provided URL** — extract and reuse `startA`/`endA` directly.
2. **Span `start_time`** — pad ±1 day (or ±1 hour for a tighter window).
3. **Fallback** — last 90 days (`now - 90d` to `now`).

Prefer tight windows; 90-day windows load slowly.

## Instructions

1. Gather IDs from user, exported data, or URL context.
2. Verify all path IDs are base64-encoded.
3. Determine `startA`/`endA` using the priority order above.
4. 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`, `space_id`, `project_id` from the browser URL. |
| Span not highlighted | `span_id` may belong to a different trace. Verify against exported span data. |
| `org_id` unknown | `ax` CLI doesn't expose it. Ask user to copy from `https://app.arize.com/organizations/{org_id}/spaces/{space_id}/…`. |

## Related Skills

- **arize-trace**: Export spans to get `trace_id`, `span_id`, and `start_time`.

## Examples

See references/EXAMPLES.md for a complete set of concrete URLs for every link type.

© arize · MIT · github/awesome-copilot

Similar skills

Everything for AI and ML →

arize-link by other authors comes first.

From the same set770

The whole set →

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor