lwlee2608/agent-skills

linear-issues

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.

First seen Jul 27, 2026

Installation

$ npx skills add lwlee2608/agent-skills --skill linear-issues

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from lwlee2608/agent-skills · top by installs.

npx skills add lwlee2608/agent-skills

Browse all from lwlee2608/agent-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Also listed on

Alternate registries and mirrors of this skill.

Repository health

Stars 1
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,924 B
  • docs SUMMARY.md 217 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 40 installs

SKILL.md

Work with Linear

Do all Linear work through the installed Linear MCP server.

Rules

  1. Use the Linear MCP tools (mcplinear*: listissues, getissue, createissue, updateissue, listcomments, createcomment, …). Read the actual schemas before calling — Linear renames tools without notice.
  1. 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:

``bash claude mcp add --transport http linear https://mcp.linear.app/mcp ``

  1. 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.
  1. 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. ``

  1. 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.
  1. 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

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