How do I install the Linear Issues skill?

Run npx skillmds@latest add lwlee2608/linear-issues 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.

What does the Linear Issues skill do?

Use when reading, searching, creating, updating, or commenting on Linear issues. Routes every Linear operation through the installed Linear MCP server and keeps ticket comments to a few sentences. It is listed under AI & ML on SkillMD.

Is Linear Issues safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Linear Issues?

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 Issues free to use?

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

Who published Linear Issues?

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

Linear Issues by lwlee2608 — Agent Skill

Name: Linear Issues
Author: lwlee2608

File contents

Work with Linear

Do all Linear work through the installed Linear MCP server.

Rules

Use the Linear MCP tools (mcp__linear__*: list_issues, get_issue, create_issue, update_issue, list_comments, create_comment, …). Read the actual schemas before calling — Linear renames tools without notice.
Never fall back to the GraphQL API or web UI. If no Linear MCP server is connected, stop and tell the user to add https://mcp.linear.app/mcp (HTTP transport) to their agent. In Claude Code:
```
claude mcp add --transport http linear https://mcp.linear.app/mcp
```
Resolve names to IDs before writing. Team, state, label, and assignee fields take UUIDs; a display name fails or silently no-ops. Call the matching list_* tool first.
Keep comments short. 1–3 sentences. Outcome first, link the PR instead of pasting the diff, no preamble, no recap of the ticket, no sign-off, no emoji.
```
Root cause: config loader reads `retry_count` but the YAML key is `retryCount`, so it binds 0. Fixed in #482.
```
Don't hand-move a PR-linked issue to Done. A linked PR (branch name, or Fixes ENG-482 in the title/body) moves the issue to Done on merge. Set it by hand only when no PR is linked, or the user asks.
Confirm before writes the user did not ask for. Issues, status changes, and comments are visible to the whole team. If they asked for the write, just do it.

Verification

Re-read the object after a write; report the identifier and URL (ENG-482 — https://linear.app/…).
If a comment runs past ~3 sentences, cut it.

Frequently asked questions

Linear Issues