Skip to content
Skills Library
Management & product · Tool integration

linear

/linear

Read and manage software issues, tickets, projects, and planning data in Linear. Use to review sprints and cycles, identify ticket rollover and release blockers, and update issue status, assignees, priorities, and milestones through Linear's official MCP server.

Licence
CC0-1.0
Last repository change
25.10.2026

Assessment and security

91/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content26 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.

Licence

CC0-1.0, otwarta.

What it does and when to use it

Read and manage software issues, tickets, projects, and planning data in Linear. Use to review sprints and cycles, identify ticket rollover and release blockers, and update issue status, assignees, priorities, and milestones through Linear's official MCP server.

Original author description

Read and manage software issues, tickets, projects, and planning data in Linear. Use to review sprints and cycles, identify ticket rollover and release blockers, and update issue status, assignees, priorities, and milestones through Linear's official MCP server.

How it works

SKILL.md has no level-two headings · 42 lines, 316 words

SKILL.md preview
---
name: "linear"
description: >-
  Read and manage software issues, tickets, projects, and planning data in Linear.
  Use to review sprints and cycles, identify ticket rollover and release blockers,
  and update issue status, assignees, priorities, and milestones through Linear's
  official MCP server.
icon: "linear"
metadata: { "includeInPrompt": false }
---

# Linear

Use the installed `linear` CLI. Start with `linear status`. If it reports
`not_connected`, run `linear authorize-url` and share only the returned
`connect_url` with the user.

OAuth uses Dynamic Client Registration and PKCE through authd. No shared client
secret enters Muse, and credentials must never be requested in chat.
The first connection requests read-only access. Before a write, or after one
fails for missing access, run `linear status --for-command <permission>`. For
Linear's `save_*` tools, use the matching `*.create` permission when the
arguments omit `id`, and the matching `*.manage` permission when they include
`id`. If the status command
returns `scope_status: not_granted`, copy `scope_add_url` exactly and post it on
its own line as `[Additional Linear access](<scope_add_url>)` so the client
renders the native access button, then wait for consent to finish before
retrying once. OAuth access does not replace Hatch approval. Never construct a
scope URL or ask for tokens in chat.

Run `linear list-tools` to inspect the live provider catalogue and schemas,
then call an advertised tool with:

```text
linear call-tool --name <tool> --arguments-json '<json-object>'
```

`list-tools` exposes only reviewed Linear tools and includes each tool's
`hatch_permission`, `hatch_action`, and `hatch_permission_label`. For a
polymorphic `save_*` tool, the permission fields show the `id`-based selector
used at execution. Linear hides write tools from its live catalogue while the
OAuth grant is read-only; do not describe an all-read `tools` list as lack of
write support. In that state, `list-tools` returns manifest-derived
`additional_access` entries separately from the provider-advertised tools. When
the user requests one of those capabilities, share its `scope_add_url` using
the exact Additional Linear access link format above, wait for consent, then
rerun `linear list-tools` to obtain the provider's live write-tool schema.
Unknown or newly advertised provider tools remain unavailable until reviewed.
Read permissions follow the user's connector settings; changes require the
corresponding granular approval. Do not retry a failed or timed-out write
automatically because its side effect may have completed.
Files in this package (3)
  • SKILL.md 3 KB
  • connector_auth_config.yaml 1 KB
  • manifest.yaml 3 KB

Versions

RepositoryScoreLicence
This page · asgeirtj/system_prompts_leaks91CC0-1.0
jjuraszek/pi-gauntlet100MIT
TerminalSkills/skills100Apache-2.0
OpenHands/extensions100MIT
magnus919/agent-skills100MIT
joe-broadhead/opencode-linear100MIT
glebis/claude-skills100MIT
apideck-libraries/api-skills100Apache-2.0
getsentry/junior100Apache-2.0

Database snapshot: 13.11.2026 · package version bf32bf3512f8 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90devartslab-linear
    Work with Linear via the linear-mcp-server MCP tools. Use when the user wants to view, create, update, triage, comment on, or organize Linear issues, projects, cycles, documents, releases, milestones, or pull-request diffs, or mentions Linear tickets, teams, or the DevArts Lab workspace.
  • 90linearis
    Manage Linear.app work from the command line with the linearis CLI (bins linearis / linear), which outputs JSON: issues/tickets, projects, cycles (sprints), milestones, initiatives (roadmap), documents, labels, teams, users, and issue discussions/comments. Use when the user…
  • 100project-manager
    Use this skill for ANY interaction with external issue tracking and project management tools (Linear, Jira, GitHub Issues, etc.). This includes: - Reading, creating, or updating issues in Linear/Jira/GitHub - Querying project boards, backlogs, or sprints - Updating issue…
  • 90dev10x:linear
    Linear issue tracker operations via MCP tools. Get, create, update issues and list comments. Documentation-only skill — no scripts. TRIGGER when: performing CRUD operations on Linear issues, comments, or statuses. DO NOT TRIGGER when: using GitHub Issues or JIRA (use…
  • 100linear-core-workflow-b
    Coordinate Linear projects, cycles, initiatives, milestones, and issue membership without assuming a workspace taxonomy. Use when implementing portfolio or planning automation. Trigger with "sync Linear project", "manage Linear cycles", or "coordinate Linear initiatives".
  • 96linear-project-management
    Use this skill when driving Linear projects and issues from an agent.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.