Agent skill · software engineering · jeremylongshore
linear-prod-checklist
Analyze a Linear integration for production across auth, data, quotas, webhooks, recovery, and ownership. Use when preparing a launch, material permission change, or production migration. Trigger with "review Linear readiness", "launch Linear integration", or "Linear production checklist".
Why this skill is useful
Provides specific implementation patterns and production readiness checks for Linear integrations that the AI wouldn't reliably generate on its own.
What it needs
Requires linear account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Linear Production Readiness Gate Overview Produce an evidence-backed go, conditional-go, or no-go decision instead of a box-checking document detached from the deployed system. 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 OAuth is recommended for apps used by others, and app/team authorization, refresh behavior, and secret rotation must be tested. Webhook receivers require public HTTPS, raw-body signature verification, a 200 response within five seconds, deduplication, and reconciliation. Request and complexity limits vary by auth mode and can include lower endpoint-specific windows. 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. Identify the exact artifact, commit, environment, workspace/team scope, data classes, owner, and rollback authority. 2. Verify SDK/runtime compatibility, token type, exact scopes, secret storage, rotation, revocation, and access review. 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/linear-prod-checklist