Agent skill · software engineering · jeremylongshore
linear-install-auth
Install the current Linear TypeScript SDK and configure personal-key, OAuth, or app-actor authentication safely. Use when connecting a repository or correcting an auth setup. Trigger with "install Linear SDK", "configure Linear OAuth", or "set up Linear API auth".
Why this skill is useful
Adds specific commands and patterns for authenticating with the Linear API that the AI wouldn't reliably generate on its own.
What it needs
Requires node 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 SDK Installation and Authentication Overview Choose authentication from the operating model, pin the SDK through the repository's lockfile, and prove access with a bounded read-only query. 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 The official package is @linear/sdk; npm reported 95.0.0 with Node.js >=18.x on 2026-09-11. Personal keys use a raw Authorization value; OAuth tokens use the Bearer scheme. The SDK represents these as apiKey and accessToken. OAuth is recommended for applications used by other people; scheduled automation should use the client-credentials grant when enabled. 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 runtime, Node version, manifest, lockfile, existing client construction, and secret provider. 2. Choose personal key for an owner-controlled integration, authorization-code OAuth for user-delegated access, or client credentials for approved unattended automation. 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/linear-install-auth