Agent skill · software engineering · jeremylongshore
linear-core-workflow-a
Implement a controlled Linear issue lifecycle from discovery through create, update, relation, comment, and archive actions. Use when automating issue operations with the GraphQL API or TypeScript SDK. Trigger with "automate Linear issues", "build an issue workflow", or "update Linear issue states".
Why this skill is useful
Adds specific commands and patterns for managing issue lifecycles in Linear that the AI wouldn't reliably generate on its own.
What it needs
Requires @linear/sdk 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 Issue Lifecycle Workflow Overview Build an issue workflow that resolves workspace-owned identifiers first and treats each write as a reviewable, reversible business action. 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 issueCreate requires a team ID; without a state ID Linear selects the team's first Backlog state, or Triage when enabled. The SDK uses verb-first mutation names such as createIssue, updateIssue, and archiveIssue. Changes made during the first three minutes after issue creation are treated as part of creation and do not produce activity-log entries. 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. Resolve the authenticated viewer, organization, target team, workflow states, labels, and assignees using read-only queries. 2. Translate the requested business transition into an explicit create/update/comment/relation plan with stable IDs. 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/linear-core-workflow-a--dc55dd