linear-hello-world

Linear Read-Only Connectivity Proof

Overview

Verify endpoint, auth mode, viewer identity, and visible team count without spending the first test on a production write.

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 GraphQL endpoint is https://api.linear.app/graphql and supports introspection.
• Personal API keys use Authorization: <API_KEY> without Bearer; OAuth access tokens use Authorization: Bearer <ACCESS_TOKEN>.
• The official TypeScript SDK accepts either apiKey or accessToken in LinearClient.

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: <API_KEY>; OAuth tokens use Authorization: Bearer <ACCESS_TOKEN>. 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 repository runtime, package manager, secret-loading convention, and existing Linear client code.
2. Select personal API key only for owner-controlled scripts or OAuth for applications used by others.
3. Pin a compatible @linear/sdk range or construct a minimal GraphQL request using the correct authorization form.
4. Query only viewer ID/display name and a small page of visible team IDs/keys; inspect GraphQL errors.
5. Record SDK version, auth mode, endpoint, status, and counts without logging the token or returned personal content.
6. Leave all create/update/delete operations for a separately approved workflow.

Approval Boundaries

Do not create, reveal, rotate, or revoke credentials; authorize an OAuth app; change scopes or team access; create, mutate, archive, or delete workspace data; configure or re-enable webhooks; import or export data; change roles, SCIM, or audit streaming; transmit diagnostics; change paid entitlements; or perform another production mutation without explicit approval from the accountable owner. Keep diagnosis read-only unless implementation was requested.

Output

Return the workspace and team scope, auth mode without credential value, files and contracts inspected, exact operation names, evidence collected, validation result, sensitive fields redacted, remaining risk, accountable owner, approval state, and rollback or next action.

Error Handling

Examples

Use a compact handoff that makes scope, mutation authority, and verification evidence reviewable.

Input:

runtime=node20; client=sdk; auth=personal-key-reference; operation=viewer+teams(first:5)

Expected handoff:

endpoint=verified; viewer=present; visible-teams=count-only; mutations=0

Resources

• Skill-specific official documentation
• Linear developer documentation index
• Linear GraphQL API