hyperlane-xyz/hyperlane-monorepo / .agents/skills/fetch-linear-ticket
fetch-linear-ticket
VerifiedFetch a Linear ticket's title + description (the source of all warp route parameters) from a ticket ID or URL, using whichever Linear access the agent has — a Linear integration/tool if present, otherwise the Linear GraphQL API with LINEAR_API_KEY — and halt clearly if no access is configured. Referenced by every warp deploy/update skill that reads a ticket.
Fetch Linear Ticket
Every warp deploy/update skill starts from a Linear ticket whose description carries the route parameters (token, chains, fee type, owners, etc.). This skill standardizes how the ticket is fetched so the access method and the not-configured error are consistent across the chain, rather than each skill hard-coding one path.
Input
- Ticket ID or URL (required) — e.g.
ENG-3516orhttps://linear.app/hyperlane-xyz/issue/ENG-3516/....
Step 1: Extract the issue ID
From a URL, pull the issue key (e.g. ENG-3516). If given a bare key, use it directly.
Step 2: Fetch the ticket (capability-first)
Fetch the issue's title and description using whichever Linear access this agent has:
-
Preferred — the agent's Linear integration. If a Linear tool/integration is available (e.g. a
get_issuecapability), use it to fetch the issue by key. This path also exposes attachment/image signed URLs (used later for logos). -
Fallback — the GraphQL API. If no integration is available but
LINEAR_API_KEYis set, query the API directly:curl -sS -X POST https://api.linear.app/graphql \ -w '\nHTTP %{http_code}\n' \ -H "Authorization: $LINEAR_API_KEY" \ -H "Content-Type: application/json" \ -d '{"query": "{ issue(id: \"<ISSUE_ID>\") { title description } }"}'Fail closed — validate the response before using it.
curlwon't error on an HTTP failure by itself, and GraphQL returns HTTP 200 even on errors. Treat any of these as a failed fetch and halt (do NOT proceed with an empty/partial description): a non-2xx HTTP status (e.g. 401/403/429/5xx), a body containing a top-levelerrorsarray, or a nulldata.issue.
If neither is available — no Linear integration AND LINEAR_API_KEY unset or returning 401 — halt and tell the user:
No Linear access is configured. Either enable the Linear integration, or
export LINEAR_API_KEY=<your-key>and restart the coding-assistant session, then try again.
Step 3: Return
Show the user the ticket title and description before proceeding. The calling skill parses the description for its own fields (token details, chains, fee type, warp route ID, owners, quote signers, ownership table, change instructions, etc.) — this skill only fetches; it does not interpret.
Consumers
/warp-deploy-fund-deployer, /warp-deploy-init-route, /warp-deploy-validate-owners, /warp-deploy-update-owners, /warp-update, /warp-update-extend. (Fetching a fresh signed URL for a logo attachment mid-skill is a separate, integration-specific operation and stays in the caller.)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |