Skip to main content
skill CX Codex official · GitHub

pr-artifact-explorer — GitHub Copilot skill: PRs and artifacts

The pr-artifact-explorer GitHub Copilot skill opens GitHub PRs, issues, workflow runs, Actions artifacts, and web previews in an Artifact Explorer panel. Ask to inspect or share one of these items to activate it.

MIT ★ 41,430 updated 2026-10-23

Install into GitHub Copilot · GitHub CLI All methods and platforms ↓
gh skill install github/awesome-copilot skills/pr-artifact-explorer
Open on GitHub

What pr-artifact-explorer does

The skill displays PRs, issues, GitHub Actions runs, artifacts, and web pages in the Artifact Explorer canvas. Runs without a PR can be filtered by event, status, branch, or workflow. Artifact previews support file browsing and static sites, with shareable links.

Set a browser viewport and zoom, capture Chromium screenshots, or browse in an isolated window with navigation history. JUnit XML appears as a test report, and video files use a native player. Artifact downloads run as background jobs and can be retried after a failure. Artifact programs and build scripts are never executed. The controlled browser requires Playwright and Chromium; if either is missing, the skill relays setup instructions rather than installing it.

What it helps with

  • open a GitHub PR or issue in a viewing panel
  • filter workflow runs that have no associated PR
  • inspect an Actions artifact and share its preview
  • check a web preview at a chosen viewport size
  • read test results from JUnit XML

Example prompts for the agent

  • Open PR 123 in owner/repo in the Artifact Explorer.
  • Show scheduled runs in owner/repo and inspect their artifacts.
  • Open localhost:3000 in a mobile viewport and capture a screenshot.

How to install pr-artifact-explorer

1GitHub CLI

gh skill install github/awesome-copilot skills/pr-artifact-explorer

2Manually: put the files in place

.github/skills/pr-artifact-explorer/SKILL.md

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

Questions about pr-artifact-explorer

How do I install pr-artifact-explorer in GitHub Copilot?

Run gh skill install github/awesome-copilot skills/pr-artifact-explorer. The skill file is at .github/skills/pr-artifact-explorer/SKILL.md.

What does pr-artifact-explorer do?

It opens GitHub PRs, issues, Actions runs, artifacts, and web previews in an Artifact Explorer panel. It can filter runs, capture screenshots, and render supported files such as JUnit reports and videos.

What does pr-artifact-explorer need to run?

The controlled browser needs Playwright and Chromium. If either is missing, the skill provides setup instructions instead of installing it.

Source text

SKILL.md · MIT
---
name: pr-artifact-explorer
description: 'Open, share, and inspect GitHub PRs, issues, workflow runs (including scheduled, manual and other runs with no PR), Actions artifacts, and local or HTTP(S) web previews in the Artifact Explorer canvas, with viewport presets, zoom, screenshots, and recoverable download jobs.'
---

# Artifact Explorer

Use the `pr-artifact-explorer` canvas to show a user pull requests, issues, workflow runs, Actions artifacts, and web pages.

## How to drive the canvas

The action names below (`open_target`, `share`, ...) are **canvas actions, not standalone tools**. Always:

1. Call `list_canvas_capabilities { canvasId: "pr-artifact-explorer" }` to discover the actions and their schemas.
2. Call `open_canvas { canvasId: "pr-artifact-explorer", instanceId: "<handle you choose>" }` to open or focus the panel.
3. Call `invoke_canvas_action { instanceId, actionName, input }` with that same `instanceId`.

## Open a target

`invoke_canvas_action` with `open_target { input }` (or the open input `repository`, `pullNumber`, `runId`, `artifactId`, `url`, `route`, `view: "runs"` with run filters, plus `preset`/`width`/`height`/`zoom`). `input` accepts:

- GitHub PR/issue URLs or `owner/repo#123`; issues display details only
- Actions links and requests that need no PR: `https://github.com/<owner>/<repo>/actions` (also `?query=event%3Aschedule`, `/actions/workflows/<file>.yml`), `https://github.com/<owner>/<repo>/actions/runs/<run>`, `owner/repo actions`, `owner/repo run 123`, `show scheduled runs in owner/repo`
- real artifact permalinks (`https://github.com/<owner>/<repo>/actions/runs/<run>/artifacts/<id>`), an artifact ID with a repository, or a shared explorer link/route such as `#/docs`, `#/artifact/owner%2Frepo/0/456?file=index.html`, `#/browser?v=...`
- `http(s)://` and `localhost` URLs (browser preview)
- bounded natural language: `open PR 123 in owner/repo`, `show localhost:3000 on mobile`, `go back`, `zoom 150%`, `tablet`, `1280x720`, `screenshot`

Use `share { input, preset?, zoom?, width?, height? }` to produce a link, route, and text to give the user. Artifact shares keep repository/artifact/file identity (not preview ports); the recipient pastes it into the canvas or into `open_target`.

## Workflow runs without a pull request

Many runs have no PR: `schedule` (cron), `workflow_dispatch`, `push`, `release`, `workflow_run`, and others. Use `open_runs { repository, event?, status?, branch?, workflow?, excludePullRequests?, hasArtifacts? }` to open the repository's **Workflow runs** list (for example `event: "schedule"` for cron runs; `excludePullRequests` and `hasArtifacts` default to true, so pass false to include PR runs or runs with no artifacts), and `open_run { repository, runId }` to open one run and its artifacts. The same artifact preview, Browser view, sharing and Re-run behavior applies; artifacts opened from a run keep a `?run=<id>` route so breadcrumbs return to the run. Run rows show a lazily loaded artifact count; the branch filter autocompletes real branches. Routes use `nopr=0` and `artifacts=0` to turn those defaults off.

## Artifacts

`inspect_artifact { repository, artifactId }` starts a background job. Downloads continue past soft limits; when one is reached the user is prompted for a larger value (`set_limit { kind, value }`; the value must be at least the live progress). Check `job_status`; use `retry_job` after an `interrupted` or `failed` job (a completed ZIP is reused) and `cancel_job` only when asked. Never execute artifact programs or build scripts: artifacts are only inspected or previewed as static sites and files.

Re-running the workflow that produced an artifact is a UI-only, user-confirmed action (the Re-run button on an artifact row or a run page). Never attempt it yourself or call its API; if the user wants a fresh artifact, tell them to use that button. It reuses the original commit, ref and actor, is limited to 30 days and 50 re-runs, and only requests a run, not a ready artifact.

## Browser preview

- `navigate_browser { url, preset?, zoom? }` opens an http(s) URL, including localhost.
- `set_viewport { preset: native | mobile | tablet | desktop | custom, width?, height?, orientation? }` sets the emulated page size.
- `set_zoom { zoom, fit? }` scales the view without changing the viewport.
- `screenshot { mode?: "fresh" | "controlled", url?, preset?, width?, height?, fullPage? }` takes a real Chromium PNG saved under the session `files/artifact-explorer-screenshots` folder. `fresh` (default) renders the URL anew and is labeled `fresh-render`; `controlled` captures the live isolated Chromium page (`controlled-current`).
- `controlled_navigate { url, preset?, ... }`, `controlled_back`, `controlled_forward`, `controlled_refresh`, `controlled_close` drive an isolated Chromium (in-memory profile, no login state) with real history; use it for sites that block iframes. Navigation failures are returned as errors, never as blank pages. If Playwright or Chromium is missing, relay the returned setup instructions to the user (including a `playwright_config_unsupported` error for the retired `PR_ARTIFACT_EXPLORER_PLAYWRIGHT` variable); never install silently.
- Pages that forbid framing (X-Frame-Options / CSP) are reported and not bypassed.

## Previewing files

- A contextual **Browser view** action appears in the preview toolbar only for static-site HTML artifacts; it is not a global nav item. Open URLs directly with `open_target` / `navigate_browser` or a `#/browser?v=...` route.
- `.webm`, `.mp4` and `.mov` use native `<video controls>` with range seeking (the whole entry is CRC/size verified once, then reused). Codec support is browser-dependent (WebM VP8/VP9 is most reliable; H.264 MP4/MOV may not play), so a failure shows an explanation and a download fallback.
- A compact **Preview / Raw** toggle sits beside Download for every file (`&view=raw` in routes). Raw shows exact source for text and a bounded, labelled-partial hex+ASCII view for binary; unsafe/encrypted entries explain why and keep the ZIP download.
- Browser chrome and owned artifact HTML follow the inherited canvas theme (initial and live changes); controlled Chromium and captures follow the current color scheme. External sites keep their own theme.
- **Open in default browser** (Sharing and help menu) launches the current http(s) target in the OS browser. Owned artifact sites are served by this canvas's loopback server and stop when it closes.
- JUnit XML (`testsuites`/`testsuite` roots) renders a native report with totals, status filters, search and failure/error/skipped/stdout/stderr details; the XML source and download stay available. Malformed reports fall back to source with an error; other XML uses the generic viewer.

## Recovery

If the canvas misbehaves, call `restart_canvas`: it keeps the port, token, and running jobs. Use `docs` to open the built-in Docs tab, which also lists keyboard shortcuts (press `?`).

© github · MIT · github/awesome-copilot

Similar skills

SKILL.md skills catalog →

From the same set993

The whole set →
spring-boot-4-migration The spring-boot-4-migration GitHub Copilot skill guides Spring Boot 3.x projects through a move to 4.0. It also handles migration-related build or test failures and reviews an existing upgrade. CX Codex +1 ★ 41,430repo stars skill-distribution-audit skill-distribution-audit — a GitHub Copilot skill that validates skill collections before release. Reconciles source repositories against distribution manifests and actual discovery output. CX Codex +1 ★ 41,430repo stars scout-issue The scout-issue GitHub Copilot skill finds open GitHub issues that fit a developer’s contribution goals. It asks about skills, experience, available time, and contribution type before ranking candidates. CX Codex +1 ★ 41,430repo stars sap-cloud-integration This GitHub Copilot skill guides work on SAP Cloud Integration iFlows. It activates for CPI Groovy scripts, exchange settings, retry design, and adapter errors. CX Codex +1 ★ 41,430repo stars ponder ponder — a skill for GitHub Copilot runs iterative appraisal loops over a subject until evaluations converge. It enforces exhaustive unit coverage so no item is skipped. CX Codex +1 ★ 41,430repo stars openapi-to-application-java-spring-boot The openapi-to-application-java-spring-boot GitHub Copilot skill builds a Spring Boot application skeleton from an OpenAPI specification. It activates for requests to create or implement a Java API from an OpenAPI or Swagger file. CX Codex +1 ★ 41,430repo stars on-device-delegate on-device-delegate — a GitHub Copilot skill that delegates heavy file reading to an on-device worker. Keeps the main cloud context lean during log analysis and test triage. CX Codex +1 ★ 41,430repo stars markdown-to-word-mermaid The markdown-to-word-mermaid GitHub Copilot skill converts Markdown files with Mermaid diagrams into Word documents. It includes SVG diagrams with PNG fallbacks and places tall diagrams with page breaks in mind. CX Codex +1 ★ 41,430repo stars

Project sponsors

Companies that keep this analytics open