Linear issues and projects
Works with Linear issues, projects and cycles through Linear's MCP server in a fixed order: setup, scope, read, then write, with sample workflows for triage, sprints and releases. Use when an agent should read or update Linear as part of a task.
linear- Author
- OpenAI
- Source
- openai/skills/skills/.curated/linear @ 49f948f
- License
- Apache-2.0
About this skill
What it does
The skill sets a fixed order for working in Linear through Linear's MCP server. Step 0 is setup when the server is not connected: codex mcp add linear --url https://mcp.linear.app/mcp, turning on the remote MCP client in config.toml, codex mcp login linear for OAuth, then a restart. For connection errors on Windows it gives a config that runs mcp-remote through WSL.
Then the agent clarifies scope (team, project, priority, labels, cycle, dates) and confirms the IDs it needs, reads before it writes, explains the grouping before any bulk change and ends with a summary, gaps and next steps.
The file names the MCP tools it expects: issues, statuses and labels (list_issues, create_issue, update_issue and others), projects, teams and users, documents, comments and cycles. It sketches nine workflows, from sprint planning and bug triage to workload balance and retrospectives, plus troubleshooting for OAuth, tool-call errors, missing data and rate limits.
When to use it, and when not
Use it when the agent should read or change Linear issues, projects or cycles as part of a task, especially in bulk.
For a single lookup the connected MCP server alone is enough.
How to run it
The install command below puts the whole folder in place: SKILL.md, the icons, the Codex metadata file and the licence. It needs the Linear MCP server (https://mcp.linear.app/mcp) connected to your workspace through OAuth; no API key is stored. The setup commands in Step 0 are Codex commands; other agents connect the same server URL in their own MCP settings. To call it:
- Claude Code:
/linear, or ask for the skill by name. - Codex:
$linear. - Cursor: type
/in the Agent chat and picklinear.
Example: /linear List unassigned high-priority bugs in the Payments team and suggest owners based on current load.
OpenAI has marked openai/skills deprecated; our copy is pinned to a commit there, and as of November 2026 openai/plugins has no newer version of this skill.
How it differs from similar skills
Issue and PR triage and Spec to tickets are workflows over whatever tracker the project has configured, Linear included: triage moves issues through roles and writes agent briefs, to-tickets publishes a plan as tickets with blocking links. Both run only when called and expect Matt Pocock's tracker setup. This skill is the opposite: specific to Linear, with setup and tool names, but only short sample workflows. Planning and task breakdown can also put its tasks into Linear when the project names it as the tracker.
Install
Run one command — it saves SKILL.md and the files it uses into your agent's skills folder. Claude Code and Codex pick up a new skill without a restart; if it does not show up, restart the agent.
curl -fsSL --create-dirs -o ~/.claude/skills/linear/SKILL.md https://anymodel.org/en/skills/openai/linear/SKILL.md -o ~/.claude/skills/linear/LICENSE.txt https://anymodel.org/en/skills/openai/linear/LICENSE.txt -o ~/.claude/skills/linear/agents/openai.yaml https://anymodel.org/en/skills/openai/linear/agents/openai.yaml -o ~/.claude/skills/linear/assets/linear-small.svg https://anymodel.org/en/skills/openai/linear/assets/linear-small.svg -o ~/.claude/skills/linear/assets/linear.png https://anymodel.org/en/skills/openai/linear/assets/linear.png
curl -fsSL --create-dirs -o ~/.agents/skills/linear/SKILL.md https://anymodel.org/en/skills/openai/linear/SKILL.md -o ~/.agents/skills/linear/LICENSE.txt https://anymodel.org/en/skills/openai/linear/LICENSE.txt -o ~/.agents/skills/linear/agents/openai.yaml https://anymodel.org/en/skills/openai/linear/agents/openai.yaml -o ~/.agents/skills/linear/assets/linear-small.svg https://anymodel.org/en/skills/openai/linear/assets/linear-small.svg -o ~/.agents/skills/linear/assets/linear.png https://anymodel.org/en/skills/openai/linear/assets/linear.png
foreach ($f in 'SKILL.md','LICENSE.txt','agents/openai.yaml','assets/linear-small.svg','assets/linear.png') { $p = Join-Path "$HOME\.claude\skills\linear" $f; New-Item -ItemType Directory -Force (Split-Path $p) | Out-Null; Invoke-WebRequest "https://anymodel.org/en/skills/openai/linear/$f" -UseBasicParsing -OutFile $p }foreach ($f in 'SKILL.md','LICENSE.txt','agents/openai.yaml','assets/linear-small.svg','assets/linear.png') { $p = Join-Path "$HOME\.agents\skills\linear" $f; New-Item -ItemType Directory -Force (Split-Path $p) | Out-Null; Invoke-WebRequest "https://anymodel.org/en/skills/openai/linear/$f" -UseBasicParsing -OutFile $p }Any other agent: save the file into its skills folder, or give it the link to the file: https://anymodel.org/en/skills/openai/linear/SKILL.md
SKILL.md
Linear
Overview
This skill provides a structured workflow for managing issues, projects & team workflows in Linear. It ensures consistent integration with the Linear MCP server, which offers natural-language project management for issues, projects, documentation, and team collaboration.
Prerequisites
- Linear MCP server must be connected and accessible via OAuth
- Confirm access to the relevant Linear workspace, teams, and projects
Required Workflow
Follow these steps in order. Do not skip steps.
Step 0: Set up Linear MCP (if not already configured)
If any MCP call fails because Linear MCP is not connected, pause and set it up:
- Add the Linear MCP:
codex mcp add linear --url https://mcp.linear.app/mcp
- Enable remote MCP client:
- Set
[features] rmcp_client = trueinconfig.tomlor runcodex --enable rmcp_client
- Set
- Log in with OAuth:
codex mcp login linear
After successful login, the user will have to restart codex. You should finish your answer and tell them so when they try again they can continue with Step 1.
Windows/WSL note: If you see connection errors on Windows, try configuring the Linear MCP to run via WSL:
{"mcpServers": {"linear": {"command": "wsl", "args": ["npx", "-y", "mcp-remote", "https://mcp.linear.app/sse", "--transport", "sse-only"]}}}
Step 1
Clarify the user's goal and scope (e.g., issue triage, sprint planning, documentation audit, workload balance). Confirm team/project, priority, labels, cycle, and due dates as needed.
Step 2
Select the appropriate workflow (see Practical Workflows below) and identify the Linear MCP tools you will need. Confirm required identifiers (issue ID, project ID, team key) before calling tools.
Step 3
Execute Linear MCP tool calls in logical batches:
- Read first (list/get/search) to build context.
- Create or update next (issues, projects, labels, comments) with all required fields.
- For bulk operations, explain the grouping logic before applying changes.
Step 4
Summarize results, call out remaining gaps or blockers, and propose next actions (additional issues, label changes, assignments, or follow-up comments).
Available Tools
Issue Management: list_issues, get_issue, create_issue, update_issue, list_my_issues, list_issue_statuses, list_issue_labels, create_issue_label
Project & Team: list_projects, get_project, create_project, update_project, list_teams, get_team, list_users
Documentation & Collaboration: list_documents, get_document, search_documentation, list_comments, create_comment, list_cycles
Practical Workflows
- Sprint Planning: Review open issues for a target team, pick top items by priority, and create a new cycle (e.g., "Q1 Performance Sprint") with assignments.
- Bug Triage: List critical/high-priority bugs, rank by user impact, and move the top items to "In Progress."
- Documentation Audit: Search documentation (e.g., API auth), then open labeled "documentation" issues for gaps or outdated sections with detailed fixes.
- Team Workload Balance: Group active issues by assignee, flag anyone with high load, and suggest or apply redistributions.
- Release Planning: Create a project (e.g., "v2.0 Release") with milestones (feature freeze, beta, docs, launch) and generate issues with estimates.
- Cross-Project Dependencies: Find all "blocked" issues, identify blockers, and create linked issues if missing.
- Automated Status Updates: Find your issues with stale updates and add status comments based on current state/blockers.
- Smart Labeling: Analyze unlabeled issues, suggest/apply labels, and create missing label categories.
- Sprint Retrospectives: Generate a report for the last completed cycle, note completed vs. pushed work, and open discussion issues for patterns.
Tips for Maximum Productivity
- Batch operations for related changes; consider smart templates for recurring issue structures.
- Use natural queries when possible ("Show me what John is working on this week").
- Leverage context: reference prior issues in new requests.
- Break large updates into smaller batches to avoid rate limits; cache or reuse filters when listing frequently.
Troubleshooting
- Authentication: Clear browser cookies, re-run OAuth, verify workspace permissions, ensure API access is enabled.
- Tool Calling Errors: Confirm the model supports multiple tool calls, provide all required fields, and split complex requests.
- Missing Data: Refresh token, verify workspace access, check for archived projects, and confirm correct team selection.
- Performance: Remember Linear API rate limits; batch bulk operations, use specific filters, or cache frequent queries.
Connect through AnyModel API
This skill runs on whatever model your agent uses. Point Claude Code, Codex or Cursor at AnyModel to run it on Claude, GPT, Gemini and more with one key — pay per token, no subscription.
AnyModel