Agent skill · operations · jeremylongshore
linear-incident-runbook
Analyze and contain Linear integration incidents across authentication, GraphQL, rate budgets, webhooks, and data synchronization. Use when responding to an active degradation or reconciling after an incident. Trigger with "Linear integration incident", "Linear webhook outage", or "Linear API degradation".
Why this skill is useful
Provides specific diagnostic scripts and procedures for handling Linear production incidents that the AI wouldn't reliably generate on its own.
What it needs
Requires jq installed locally. Requires linear account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Linear Integration Incident Runbook Overview Restore a safe operating state from read-only evidence first, then reconcile missed or duplicated work without generating diagnostic mutations in production. Prerequisites The target repository, Linear workspace, environment, and accountable owner Current security, privacy, compliance, capacity, and change-control requirements An approved Linear credential only when a bounded live verification is necessary Tool Discipline Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current first-party Linear documentation and package metadata. Use Write or Edit only for requested implementation with known target files. Never write credentials, customer content, unrestricted environment output, or unredacted GraphQL variables. Current Contract Linear webhooks time out after five seconds and retry failed deliveries at one minute, one hour, and six hours, up to three retries. Rate-limit evidence comes from request, endpoint, and complexity headers plus RATELIMITED GraphQL errors. OAuth client-secret rotation invalidates client-credentials tokens immediately but does not revoke existing workspace access/refresh tokens by itself. Authentication Use a personal API key only for owner-controlled scripts, OAuth with PKCE for user-delegated applications, or an enabled client-credentials grant for approved automation. Personal keys use Authorization: <APIKEY>; OAuth tokens use Authorization: Bearer <ACCESSTOKEN>. Store credentials server-side in an approved secret manager. Treat app approval, team access, scope changes, credential creation, rotation, revocation, and production access as owner-approved actions. Instructions 1. Declare severity, commander, affected workspaces/teams, start time, customer impact, and mutation freeze state. 2. Check Linear service status and the smallest read-only authenticated query; capture redacted errors and rate headers. 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/linear-incident-runbook