How do I install the Linear skill?

Run npx skillmds@latest add modbender/linear-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Linear safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Linear?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Linear free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Linear?

modbender (@modbender) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Linear by modbender — Agent Skill

Name: Linear
Author: modbender

Linear

Manage Linear projects, issues, and tasks via the bundled Node CLI and the official Linear API. Use when you need to read, create, update, or organize Linear issues, projects, teams, milestones, comments, cycles, labels, and documents.

modbender Updated Sep 21, 2026 12 repo stars

File contents

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

Node.js and npm are installed.
Install script dependencies once:
- cd {baseDir}/scripts && npm install
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

Clarify intent and scope:
- Team/project, labels, cycle, assignee, due date, priority.
Read current state first:
- List/get issues, projects, statuses, labels, users, cycles.
Apply mutations second:
- Create/update issues, comments, projects, milestones, labels.
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.

---name: linear-2description: Manage Linear projects, issues, and tasks via the bundled Node CLI and the official Linear API. Use when you need to read, create, update, or organize Linear issues, projects, teams, milestones, comments, cycles, labels, and documents.---# Linear Workflow ManagementManage 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.## Prerequisites1. 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 Workflow1. 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```bashnode {baseDir}/scripts/linear-cli.js teamsnode {baseDir}/scripts/linear-cli.js projectsnode {baseDir}/scripts/linear-cli.js issuesnode {baseDir}/scripts/linear-cli.js issue ENG-123node {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.

Frequently asked questions