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.

Git & PRsPack: OpenAI skills87 lineslinear
Author
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 pick linear.

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.

Claude Code — macOS, Linux
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
Codex, Cursor — macOS, Linux
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
Claude Code — Windows PowerShell
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 }
Codex, Cursor — Windows PowerShell
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

Raw

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:

  1. Add the Linear MCP:
    • codex mcp add linear --url https://mcp.linear.app/mcp
  2. Enable remote MCP client:
    • Set [features] rmcp_client = true in config.toml or run codex --enable rmcp_client
  3. 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.

More from the pack OpenAI skills

ASP.NET Core apps

Guides the agent through current ASP.NET Core practice: choosing Blazor, Razor Pages, MVC or Minimal APIs, Program.cs and middleware order, auth, EF Core, tests and upgrades to .NET 10. Use when building, reviewing or upgrading an ASP.NET Core app.

ChatGPT Apps SDK

Builds ChatGPT apps on the Apps SDK: reads current OpenAI docs first, picks an app archetype, plans MCP tools, adapts an official example or scaffolds a Node server and widget, then tests in Developer Mode. Use when building or fixing an app inside ChatGPT.

CLI creator from API docs

Builds a durable CLI from API docs, an OpenAPI spec, curls or a script: JSON output, doctor and dry-run commands, safe auth, installed on PATH and paired with a companion skill. Use when an agent keeps hitting the same service through ad hoc calls.

Define a measurable goal

Turns a fuzzy intention into one measurable goal with a validator, scope and stop condition, then registers it via get_goal and create_goal. Use before goal-backed or long-running agent work, when "done" needs a number or a check.

Address GitHub PR comments

Fetches all comments, reviews and inline threads on the current branch's GitHub PR with a gh GraphQL script, numbers them and fixes only the ones you pick. Use when a PR has review comments to work through and you want to choose which get changed.

Fix failing GitHub Actions checks

Finds failing GitHub Actions checks on a PR with gh, pulls the logs, extracts the failure snippet and drafts a fix plan, changing code only after approval. Use when a PR's CI is red and you want the cause and a plan before any edit.

Jupyter notebooks

Creates and tidies Jupyter notebooks for experiments or tutorials from bundled templates via a stdlib script, with structure patterns and a run-top-to-bottom checklist. Use when starting a notebook or turning a messy one into something others can rerun.

Deploy to Netlify

Deploys the current project to Netlify with `npx netlify`: checks the login, links the folder to a site by Git remote or creates one, builds locally and returns a preview or production URL. Use when you want to publish a site to Netlify from your machine.

Browser automation with Playwright CLI

Drives a real browser from the terminal with playwright-cli: snapshots give element refs for clicks and typing, plus screenshots, console, network and traces, with no test files written. Use when a task needs a browser clicked through step by step.

Deploy to Render

Deploys an app to Render from a Git repo: writes and validates a render.yaml Blueprint with services, databases and secrets, or creates one service through the Render MCP server, then checks status and logs. Use when an app needs hosting on Render.

Security best-practice review

Checks Python, JavaScript/TypeScript and Go code against bundled security specs for ten frameworks, writes a report by severity with line numbers and fixes one finding at a time. Use when you explicitly ask for a security best-practice review.

Repository threat model

Writes a repository-grounded threat model: trust boundaries, assets, attacker capabilities and ranked abuse paths with mitigations, asking you to confirm key assumptions before the final file. Use when you explicitly ask to threat model a codebase.

Sentry issues and events

Reads Sentry issues and events through the sentry CLI without changing anything: recent production errors, issue and event details, AI root-cause summaries, with PII redacted. Use when you ask what is failing in production according to Sentry.

Deploy to Vercel

Deploys a project to Vercel, as a preview unless told otherwise, through the Vercel CLI or, without an account, a bundled script that uploads the folder and returns a preview link and a claim link. Use when you want a shareable deployment link fast.

Figma MCP design context

Reads Figma frames through the Figma MCP server in a fixed order (design context, metadata, screenshot) and rebuilds them with the project's components and tokens; also covers server setup in Codex. Use when connecting Figma MCP or coding from a frame link.

Figma use_figma prerequisite

Sets the rules an agent must load before every use_figma call that runs Plugin API JavaScript in a Figma file: return values, page resets, colours, fonts, node IDs, small validated steps. Use when creating or editing anything inside a Figma file.

Implement a Figma design in code

Implements a Figma frame or component as code in your repo with 1:1 visual parity: fetches context and a screenshot, maps the output to project tokens and components, then runs a validation checklist. Use when a Figma link must become production UI.

Generate a Figma design from an app

Builds or updates a full screen in Figma from code or a description, section by section, using the file's published components, variables and styles instead of hardcoded values. Use when a page from your app should exist as a Figma screen.

Figma design system from a codebase

Builds a Figma design system library from a codebase in five supervised phases: discovery, variables and styles, page structure, components one by one, QA. Use when a product needs a Figma library that matches its code tokens and components.

Figma Code Connect components

Links published Figma components to the code components that implement them via Code Connect: finds unmapped ones, matches them in the codebase, maps only what the user approves. Use when a Figma library and its code both exist but are not linked.

Figma design system rules

Writes project rules for turning Figma designs into code into CLAUDE.md, AGENTS.md or a Cursor rules file, based on Figma's rule template and an analysis of the codebase. Use when setting up an agent for regular Figma-to-code work in a repo.

Create a new Figma file

Creates a blank Figma design file or FigJam board in your drafts, resolving the plan through whoami, and returns the file key and URL. Use when the next Figma step needs a fresh file to write into.