Create or register a canvas extension in the awesome-copilot repository. Use when asked to scaffold a new canvas extension, create its plugin.json, add a reusable extension to one or more plugins, or migrate extension metadata. Extensions are reusable source under extensions/; shippable plugin manifests belong under plugins/.
arize-trace
arize-trace is an open-source integrations skill for Claude Code and compatible agents, published by github. Its author describes it as: “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…”. The project has 38k stars on GitHub and is available under the MIT license. Add it to your setup with `git clone https://github.com/github/awesome-copilot ~/.claude/skills/arize-trace`.
What arize-trace does
> **`SPACE`** — All `--space` flags and the `ARIZE_SPACE` env var accept a space **name** (e.g., `my-workspace`) or a base64 space **ID** (e.g., `U3BhY2U6...`). Find yours with `ax spaces list`.
Installation
Add arize-trace to your agent with:
git clone https://github.com/github/awesome-copilot ~/.claude/skills/arize-traceAlways review a skill's source before installing it. This command comes from the skill's public repository; the linked repo is the source of truth for exact setup steps.
What's inside
The SKILL.md for arize-trace is organised into these sections:
- Concepts
- Prerequisites
- Export Spans: ax spans export
- By trace ID
- By span ID
- By session ID
- Flags
- Bulk export with --all
- Export Traces: ax traces export
- How it differs from ax spans export
- Time-series index lag
- Filter Syntax Reference
When to use it
Reach for arize-trace when you want integrations help from your agent without writing the same instructions every session. Load the skill and the agent picks it up automatically for relevant tasks.
Strengths
- Clear MIT license — safe to read and adapt
- Ships in github/awesome-copilot, an established project with 37,982 GitHub stars
- Actively maintained (recent commits)
Topics
Frequently asked questions
- What does arize-trace do?
- 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.
- How do I install arize-trace?
- Run git clone https://github.com/github/awesome-copilot ~/.claude/skills/arize-trace in your agent, then reload your skills. Review the source at https://github.com/github/awesome-copilot before installing.
- Is arize-trace free to use?
- Yes. arize-trace is free and open source under the MIT license, so you can read, run, and adapt it within that license's terms.
- Where does arize-trace come from?
- arize-trace ships inside github/awesome-copilot, a repository that contains 41 catalogued skills in total. The repository's 37,982 GitHub stars apply to that whole collection, not to this skill on its own.
Related skills
More Integrations →Run the AgentRC readiness assessment on the current repository and produce a static HTML dashboard at reports/index.html. Wraps `npx github:microsoft/agentrc readiness` and hands off rendering to the @ai-readiness-reporter custom agent. Supports policies (--policy) for org-specific scoring. Use when asked to assess, audit, or score the AI readiness of a repo.
Generate tailored AI agent instruction files via AgentRC instructions command. Produces .github/copilot-instructions.md (default, recommended for Copilot in VS Code) plus optional per-area .instructions.md files with applyTo globs for monorepos. Use after running /acreadiness-assess to close gaps in the AI Tooling pillar.
Help the user pick, write, or apply an AgentRC policy. Policies customise readiness scoring by disabling irrelevant checks, overriding impact/level, setting pass-rate thresholds, or chaining org baselines with team overrides. Use when the user asks about strict mode, AI-only scoring, custom weights, CI gating, or wants org-wide standardisation.
Add educational comments to the file specified, or prompt asking for file to comment if one is not provided.