Menu
Fetch and display a GitHub gist. Triggers when the user asks to read, fetch, or view a URL from gist.github.com.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Spot-check the health of a live Aztec network deployment by sweeping recent GCP logs for warn/error messages, mapping each to the deployed code, classifying expected vs unexpected, and verifying the hard invariants (no slashing, no attestation timeouts, no unexplained prunes/conflicts). Use when asked to "spot-check", "review logs", or "health check" a network (staging, testnet, devnet, ...) over a recent window.
Reference for merge-train automation internals -- workflows, scripts, CI integration, and configuration. Use when modifying or debugging merge-train infrastructure.
Build and update the developer documentation site for a new release
Guide for working with merge-train branches -- creating PRs, choosing the right base branch, understanding labels, handling failures, and bypassing checks.
Create a well-formed Linear issue — with complete context for a fresh agent, a point estimate (1/2/3/5), and acceptance criteria. Works standalone or as part of planning a project with multiple issues. Use when asked to file/create/open a Linear issue, "make a ticket", or when breaking a plan into tracked work.
Build or adjust a Linear cycle — for a whole team or just yourself. Size capacity from last-3-cycle velocity, fill with backlog bugs/high-priority items first and project work after (in your chosen project focus order), with no unassigned issues. Use when planning/prepping a cycle for a team, or when one member wants to fill/rebalance their own cycle work.
| name | read-gist |
| description | Fetch and display a GitHub gist. Triggers when the user asks to read, fetch, or view a URL from gist.github.com. |
| argument-hint | <gist URL or ID> |
| allowed-tools | Bash(gh gist *), WebFetch |
Fetch and display the contents of a GitHub gist.
Activate this skill when the user provides a URL matching gist.github.com or asks to fetch/read a gist by ID.
The argument is a gist URL or gist ID: $ARGUMENTS
Extract the gist ID from the input. It can be:
https://gist.github.com/<user>/<id> -> extract <id>https://gist.github.com/<id> -> extract <id>https://gist.githubusercontent.com/... -> extract the gist ID segmentTry gh gist view first (preferred):
gh gist view <id> --raw
If the gist has multiple files, list them first with gh gist view <id> (without --raw) to show filenames, then fetch with --raw or specify a filename with -f <filename> if the user asked for a specific file.
Fallback to WebFetch only if gh is not available or the command fails with an auth/install error:
https://gist.githubusercontent.com/<user>/<id>/raw for single-file gistshttps://api.github.com/gists/<id> and extract file contents from the JSON responseReturn the contents to the caller. If there are multiple files, show each file with its filename as a header.