Agent skill · software engineering · jeremylongshore
linear-sdk-patterns
Implement current Linear TypeScript SDK query, mutation, pagination, raw GraphQL, and error-handling patterns. Use when building or refactoring a typed Linear adapter. Trigger with "use Linear SDK", "refactor Linear client", or "write typed Linear GraphQL".
Why this skill is useful
Provides specific TypeScript patterns for using the Linear SDK, including pagination and relation loading techniques that the AI wouldn't reliably generate on its own.
What it needs
Requires @linear/sdk installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Linear TypeScript SDK Patterns Overview Keep SDK mechanics inside a bounded adapter and expose domain-shaped results rather than generated model objects throughout the application. 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 Current SDK mutations use verb-first names such as createIssue, updateUser, and archiveProject. Connections expose nodes, pageInfo, fetchNext, and fetchPrevious; optional variables are passed in an object. linearClient.client.rawRequest supports purpose-built GraphQL, while LinearError exposes parsed request/response/error evidence. 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. Inspect the installed SDK version, generated types, adapter boundary, call sites, and error policy. 2. Create one client per approved auth context and inject it; never construct clients throughout business code. 3. Wrap SDK models in domain functions that accept stable IDs and return minimum typed projections. 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/linear-sdk-patterns