Integrations

Linear

Read and manage Linear issues and projects through a Node CLI backed by the official Linear SDK.

What it does

Read Linear teams, projects, issues, workflow states, labels, and user data, then create or update issues, add comments, and create projects through a bundled Node CLI. It uses the official @linear/sdk with LINEAR_API_KEY, follows a read-before-write workflow, and reports changed IDs, states, assignees, blockers, and follow-up actions.

When to use it

  • Triage urgent bugs and assign owners
  • Plan sprint scope and missing issues
  • Prepare release blockers and rollout tasks
  • Create follow-up tasks for stale documentation

The skill document

Linear Workflow Management

Manage Linear issues and projects through the bundled CLI at {baseDir}/scripts/linear-cli.js.

Scope and Runtime Model

  • This skill runs node {baseDir}/scripts/linear-cli.js ....
  • The CLI uses the official @linear/sdk.
  • Authentication is LINEAR_API_KEY from the local environment.
  • Expected API destination is Linear GraphQL (https://api.linear.app/graphql) through the official SDK.

Prerequisites

  1. Node.js and npm are installed.
  2. Install script dependencies once:
    • cd {baseDir}/scripts && npm install
  3. Set your API key:
    • export LINEAR_API_KEY="lin_api_..."

If dependencies or LINEAR_API_KEY are missing, stop and complete setup before issue/project operations.

Authentication and Credentials

  • Required credential: LINEAR_API_KEY.
  • Get it from https://linear.app/settings/api.
  • Use least-privilege access and a dedicated token for automation.

Required Workflow

  1. Clarify intent and scope:
    • Team/project, labels, cycle, assignee, due date, priority.
  2. Read current state first:
    • List/get issues, projects, statuses, labels, users, cycles.
  3. Apply mutations second:
    • Create/update issues, comments, projects, milestones, labels.
  4. Summarize exactly what changed:
    • Mention IDs, states, assignees, blockers, and follow-up actions.

Command Coverage

  • Teams and projects: teams, projects, createProject
  • Issues: issues, issue, createIssue, updateIssue
  • Comments: createComment
  • States and labels: states, labels
  • User: user

Quick Examples

node {baseDir}/scripts/linear-cli.js teams
node {baseDir}/scripts/linear-cli.js projects
node {baseDir}/scripts/linear-cli.js issues
node {baseDir}/scripts/linear-cli.js issue ENG-123
node {baseDir}/scripts/linear-cli.js createIssue "Title" "Description" "team-id" '{"priority":2}'
node {baseDir}/scripts/linear-cli.js updateIssue "issue-id" '{"stateId":"state-id"}'

Practical Workflows

  • Triage urgent bugs: list high-priority open issues, assign owners, move state to In Progress, add triage comments.
  • Sprint planning: review cycle scope, create missing issues, set priorities and estimates, align assignees.
  • Release prep: verify blockers, update project status, create milestone tasks, add rollout comments.
  • Documentation cleanup: find stale docs/issues, open follow-up tasks, link related records.

Safety and Operational Rules

  • Never invent IDs; fetch and confirm before updates.
  • Prefer narrow updates over broad bulk edits.
  • For bulk edits, explain grouping logic before applying changes.
  • Do not include secrets in issue comments or descriptions.
  • Do not send data to endpoints outside Linear API scope for this skill.

References

  • references/API.md for priority values and workflow patterns.

Questions people ask

What setup is required before running Linear operations?
Install Node.js and npm, run npm install in the skill’s scripts directory, and set LINEAR_API_KEY in the local environment. The key can be created from Linear’s API settings.
How does it avoid updating the wrong Linear records?
It reads the current state first and never invents IDs; records are fetched and confirmed before updates. It also prefers narrow changes and requires the grouping logic to be explained before bulk edits.
Which Linear operations are supported?
The CLI covers listing teams, projects, and issues; retrieving an issue; creating projects and issues; updating issues; adding comments; and reading states, labels, and user data.

Related skills

LinkedIn

Access LinkedIn profiles, posts, media uploads, public libraries, and advertising APIs through managed OAuth.

410 installs45 stars

GitHub

Access and manage GitHub resources through the REST API with managed OAuth connections.

595 installs47 stars

Outlook

Read and manage Outlook mail, folders, calendars, and contacts through Microsoft Graph.

771 installs46 stars

Linear

Query and manage Linear work items through GraphQL with managed OAuth authentication.

517 installs18 stars

Salesforce

Query and manage Salesforce sObjects through REST APIs with managed OAuth and explicit write approvals.

704 installs8 stars

Asana

Manage Asana tasks, projects, users, workspaces, and webhooks through managed OAuth APIs.

601 installs6 stars