Agent skill · operations · jeremylongshore
linear-core-workflow-b
Coordinate Linear projects, cycles, initiatives, milestones, and issue membership without assuming a workspace taxonomy. Use when implementing portfolio or planning automation. Trigger with "sync Linear project", "manage Linear cycles", or "coordinate Linear initiatives".
Why this skill is useful
Provides specific API commands and workflows for managing projects and cycles in Linear 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 Project and Cycle Coordination Overview Map planning intent onto the workspace's actual project, cycle, initiative, and team model before making relationship changes. 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 Issues belong to one team, while projects can belong to one or more teams; access must be evaluated at both levels. List operations are Relay-style connections and must be paginated rather than assuming nodes is complete. Archived resources are hidden by default and require includeArchived: true when reconciliation needs them. 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. Discover visible teams, project statuses, cycles, initiatives, milestones, and archived-state requirements. 2. Define the source of truth and stable matching keys for every entity; names alone are not sufficient for unattended writes. 3. Build a read-only diff of requested membership, dates, status, and ownership changes. 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/linear-core-workflow-b