Manage Linear issues, boards, and cycles. Uses **Linear MCP** for standard operations and **plugin commands** for unique features.
From linearnpx claudepluginhub ruslan-korneev/claude-plugins --plugin linearThis skill uses the workspace's default tool permissions.
references/filtering.mdreferences/graphql-queries.mdreferences/workflow-states.mdProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Calculates TAM/SAM/SOM using top-down, bottom-up, and value theory methodologies for market sizing, revenue estimation, and startup validation.
Manage Linear issues, boards, and cycles. Uses Linear MCP for standard operations and plugin commands for unique features.
Use this skill when the user wants to:
/linear:board)/linear:cycle)/linear:delete)/linear:comment)For standard CRUD operations (create, get, list, update, search issues, add comments, manage projects/teams), use the Linear MCP tools directly — they are provided by the official Linear MCP server.
Trigger phrases for plugin commands:
The official Linear MCP server (mcp.linear.app) provides ~21 tools:
list_issues, list_my_issues, get_issue, create_issue, update_issue, searchlist_projects, get_project, create_project, update_projectlist_teams, get_teamlist_users, get_userlist_comments, create_commentget_document, list_documents, search_documentationlist_issue_statuses, get_issue_status, list_issue_labels| Command | Feature |
|---|---|
/linear:board | ASCII kanban board visualization |
/linear:cycle | Cycle management with velocity stats |
/linear:delete | Archive/delete issues |
/linear:comment | Edit/delete comments (MCP only supports create) |
Analyzes codebase to auto-suggest issue attributes (description, labels, estimate, priority). Works with both MCP create_issue and /linear:create flows.
| Variable | Description | Example |
|---|---|---|
LINEAR_API_KEY | Personal API Key from Linear Settings > API | lin_api_XXXXXXXXXXXX |
LINEAR_TEAM | Default team key | ENG |
Set in ~/.claude/settings.local.json:
{
"env": {
"LINEAR_API_KEY": "lin_api_XXXXXXXXXXXX",
"LINEAR_TEAM": "ENG"
}
}
The MCP server is configured in .mcp.json at the repository root. It connects automatically when the plugin is installed.
To add manually: claude mcp add --transport http linear-server https://mcp.linear.app/mcp
$LINEAR_TEAM environment variablebasename $(pwd) — auto-detected from current directoryPlugin commands use Linear's GraphQL API directly:
curl -s -X POST https://api.linear.app/graphql \
-H "Content-Type: application/json" \
-H "Authorization: $LINEAR_API_KEY" \
-d '{"query": "...", "variables": {...}}'
LINEAR_API_KEY is set — show setup instructions if missingjqecho "$RESPONSE" | jq -e '.errors' > /dev/null 2>&1echo "$RESPONSE" | jq -r '.errors[0].message'Linear uses cursor-based pagination:
issues(first: 50, after: $cursor) {
nodes { ... }
pageInfo { hasNextPage endCursor }
}
Loop while hasNextPage is true, passing endCursor as after.