skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
lwlee2608/agent-skills104 installs

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.

How do I install this agent skill?

npx skills add https://github.com/lwlee2608/agent-skills --skill linear-issues
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    This skill facilitates interaction with Linear issues through the official Linear MCP server. It provides guidelines for issue management, naming resolution, and comment formatting.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

What does this agent skill do?

Work with Linear

Do all Linear work through the installed Linear MCP server.

Rules

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

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

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

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

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

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

How can the creator link this skill?

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/lwlee2608/agent-skills/linear-issues">View linear-issues on skillZs</a>