Skills

Skill 30 of 200

Arize Link

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

2 minutes · 372 words · 8 sections

Install

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

$ npx skills add github/awesome-copilot

» /plugin marketplace add github/awesome-copilot

The first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.

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:

User-provided URL — extract and reuse startA/endA directly.
Span start_time — pad ±1 day (or ±1 hour for a tighter window).
Fallback — last 90 days (now - 90d to now).

Prefer tight windows; 90-day windows load slowly.

Instructions

Gather IDs from user, exported data, or URL context.
Verify all path IDs are base64-encoded.
Determine startA/endA using the priority order above.
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}/…`.

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.

About this skill

Trigger

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.

The verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.

Colophon for this issue

Colophon

How this issue was made

Source

github.com/github/awesome-copilot, branch main, last pushed 24 September 2026.

Licence

MIT — the text of every skill is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

200 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. 2 distinct layouts observed: .github/skills/*/SKILL.md, skills/*/SKILL.md.

Authorship

3 of 200 skills are installed into the repository rather than published from it. They are shelved in the closing “Credited skills” part and remain the work of their own authors. A skill counts as credited when its only copy lives under one agent’s dot directory; visible directories, per-agent mirror sets, and skills installable from this repository on skills.sh all count as published.

Issue colours

Resolved from a curated brand profile — hue 295°, chroma 0.190. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Heading repairs

1 repair applied to this skill so the document has one h1 and no skipped levels:

Removed “Arize Link”, a leading h1 that duplicated the skill title.

Spec compliance

Every skill satisfies the Agent Skills specification’s frontmatter rules.

Images

Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Marketplace

A plugin manifest is published at .github/plugin/marketplace.json by GitHub, declaring 162 plugins. It is read for editorial metadata only — never as the skill index, which is always the repository tree.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /github/awesome-copilot.md, and each skill at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

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

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

Priority order:

User-provided URL — extract and reuse startA/endA directly.
Span start_time — pad ±1 day (or ±1 hour for a tighter window).
Fallback — last 90 days (now - 90d to now).

Prefer tight windows; 90-day windows load slowly.

Instructions

Gather IDs from user, exported data, or URL context.
Verify all path IDs are base64-encoded.
Determine startA/endA using the priority order above.
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}/…`.

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 Link

When to Use

Required Inputs

URL Templates

Time Range

Instructions

Troubleshooting

Examples

About this skill

Trigger

Colophon

Arize Link

When to Use

Required Inputs

URL Templates

Time Range

Instructions

Troubleshooting

Examples

Appendix 30.1

ReferencesMarkdown · 1 file

About this skill

Trigger

Colophon

Appendix 30.1

ReferencesMarkdown · 1 file