Agent skill · software engineering · jeremylongshore
linear-multi-env-setup
Analyze and enforce separate Linear development, staging, and production credentials, apps, webhooks, data, and rollout controls. Use when one integration runs across multiple environments. Trigger with "separate Linear environments", "stage Linear OAuth app", or "isolate Linear webhooks".
Why this skill is useful
Adds executable scripts for configuring Linear across multiple environments with secret management that aren't in public docs.
What it needs
Requires node installed locally. Requires aws, gcp, 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 Multi-Environment Isolation Overview Make environment boundaries explicit so a local test cannot consume production credentials, events, or team data. 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 callback URLs are registered on an application, and OAuth webhook settings create a workspace-specific webhook when that app is authorized. Webhook signing secrets and OAuth client secrets rotate independently and take effect immediately for their respective uses. Client credentials must be enabled per OAuth app and app-team access can be changed from the app details page. 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. Inventory every environment's workspace, OAuth app, callback URL, webhook URL, signing secret, client secret, team access, and data class. 2. Use separate app registrations and secret references where blast radius or callback ownership differs. 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/linear-multi-env-setup