How to use the Arize Link Generator agent skill

What is the arize-link skill and what does it make the agent do?

An agent skill is a folder containing a SKILL.md file and optional reference files. When the skill is installed, the agent reads its instructions when a request matches the skill's description. The arize-link skill is described as generating deep links to the Arize UI for traces, spans, sessions, datasets, labeling queues, evaluators and annotation configs, producing clickable URLs for sharing Arize resources with team members.

The agent does not call Arize itself. It takes IDs it already has, from exported trace data, logs or a pasted URL, and builds a link to the matching page. It fills in the organisation, space and project IDs and a time window so the link opens with data visible.

• Trace and span links, with the span optionally highlighted
• Session links
• Dataset links, with the examples or experiments tab
• Labeling queue list and individual queue links
• Evaluator links, with an optional version
• Annotation config list links

Install the arize-link skill

Download the ZIP of the skill from the agent-skills directory page. Unzip it into your personal skills folder at ~/.claude/skills/, or into a project's .claude/skills/ folder if you want the skill available only in that project. The unzipped folder should contain SKILL.md and references/EXAMPLES.md.

If you use the Claude apps, you can instead upload the skill under Settings → Capabilities → Skills.

• Personal install: ~/.claude/skills/
• Project install: .claude/skills/ inside your project

What you need before you start

You need an Arize account with access to the organisation and space that contains the resources. Links only open for people who have that access, so a link is useless without it.

The skill needs base64-encoded IDs for the organisation, the space and each resource. Copy them from your Arize browser URL, which has the form https://app.arize.com/organizations/{org_id}/spaces/{space_id}/…. A plain numeric ID produces a link that returns a 404 error. The skill references the separate arize-trace skill for exporting span IDs and start times, but that skill is not bundled with this one.

• An Arize account with access to the organisation and space
• Base64-encoded org_id and space_id
• Base64-encoded resource IDs such as project_id, trace_id, span_id, dataset_id, queue_id or evaluator_id
• Optional: the arize-trace skill, for exporting span IDs and start times

Trigger the skill with natural requests

You do not need special syntax. Describe what you want to open or link to in plain language, and include the IDs you have. The skill's description covers requests to link to or open a trace, span, session, dataset, evaluator or annotation config in the Arize UI.

The skill also applies when you have IDs from exported data or logs and need to link back to the UI, or when you ask to open or view one of these items in Arize.

• "Give me a link to trace abc123 in project XYZ in my Arize space."
• "Make a shareable link to this span from the export so I can send it to Sam."
• "Link my teammate to the evaluator with this ID, latest version."
• "Open the dataset with this ID in Arize."

How the time window works

For trace, span and session links, the start and end times (startA and endA, in epoch milliseconds) matter. If they are left out, Arize defaults to the last 7 days, and a trace older than that will show as having no recent data. The skill chooses the window in this order: reuse the start and end times from a URL the user provided, then use the span's start time padded by one day either side (or one hour for a tighter window), and finally fall back to the last 90 days.

Tight windows load faster than 90-day windows, so prefer a narrow range when you have a start time.

Safety notes: scripts and network

According to the skill's listing, arize-link runs no scripts and uses no network access. It only produces text containing URLs. Because the links point to your organisation's Arize data, share them only with people who already have access to that organisation and space.

• Runs scripts: no
• Uses network: no
• Links open only for users with access to the organisation and space

Troubleshoot common link problems

Most problems come from the time window or from the IDs. An empty view usually means the trace falls outside the window, so widen it from one hour to one day to 90 days. A 404 usually means an ID is wrong or is not base64-encoded, so check the org, space and project IDs against the browser URL. If the span is not highlighted, the span ID may belong to a different trace.

• No data or empty view: widen the time window
• 404: check that IDs are copied from the browser URL and are base64-encoded
• Span not highlighted: confirm the span belongs to the trace