Interacting with Linear issues, projects, and teams. Use when creating issues, updating issues, querying issues, managing projects, working on tasks, discussing backlogs, or any interaction with Linear.
Manages Linear issues and projects through API interactions, CLI commands, and issue workflows.
npx claudepluginhub bendrucker/claudeThis skill is limited to using the following tools:
api.mdTools and workflows for managing issues, projects, and teams in Linear.
Choose the right tool for the task:
linear api CLI - Use for complex queries, bulk operations, or anything not supported by MCP toolsWhen creating issues, set the appropriate status based on assignment:
assignee: "me"): Set state: "Todo"state: "Backlog"Example:
// Issue for myself
await linear.create_issue({
team: "ENG",
title: "Fix authentication bug",
assignee: "me",
state: "Todo"
})
// Unassigned issue
await linear.create_issue({
team: "ENG",
title: "Research API performance",
state: "Backlog"
})
Use assignee: "me" to filter issues assigned to the authenticated user:
// My issues
await linear.list_issues({ assignee: "me" })
// Team backlog
await linear.list_issues({ team: "ENG", state: "Backlog" })
You can use label names directly in create_issue and update_issue - no need to look up IDs:
await linear.create_issue({
team: "ENG",
title: "Update documentation",
labels: ["documentation", "high-priority"]
})
Label Lookup: Labels can exist at the workspace level or team level. When searching for labels, check both:
list_issue_labels() (no team filter)list_issue_labels({ team: "TEAM" })If a label isn't found at the workspace level, check the team before concluding it doesn't exist.
Use linear api for queries and mutations not supported by MCP tools. See api.md for full documentation.
linear api 'query { viewer { id name } }'
With variables:
linear api 'query($id: String!) { issue(id: $id) { title } }' --variable id=ISSUE_ID
Pipe output through jq for formatting:
linear api 'query { viewer { assignedIssues { nodes { identifier title } } } }' | jq '.data.viewer.assignedIssues.nodes'
Use the linear:// URL scheme to open issues in the native Mac app instead of the browser:
# Replace https://linear.app with linear:// in any Linear URL
open "linear://team-slug/issue/ENG-123"
The desktop app must be installed. When given an issue identifier (e.g., ENG-123), construct the URL using the team's workspace slug and issue identifier.
api.mdExpert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.