dev10x:linear
/dev10x: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 dev10x:jira), or creating tickets across trackers (use dev10x:ticket-create).
- Author
- dev10x-guru ↗
- Repository
- dev10x-claude ↗
- Licence
- MIT
- Last repository change
- 12.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 3
No signals detected. Repository changed on 12.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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 dev10x:jira), or creating tickets across trackers (use dev10x:ticket-create).
Original author description
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 dev10x:jira), or creating tickets across trackers (use dev10x:ticket-create).
How it works
- Orchestration
- Operation Mapping
- Team IDs
- URL Template
- Prerequisite Check
- Project Assignment
- Searching for JTBD in Ticket
- MCP Tool Variants
SKILL.md preview
---
name: dev10x:linear
invocation-name: dev10x:linear
description: >
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 dev10x:jira),
or creating tickets across trackers (use dev10x:ticket-create).
user-invocable: false
allowed-tools:
- mcp__claude_ai_Linear__get_issue
- mcp__claude_ai_Linear__list_issues
- mcp__claude_ai_Linear__save_issue
- mcp__claude_ai_Linear__list_comments
- mcp__claude_ai_Linear__create_comment
- mcp__claude_ai_Linear__list_issue_statuses
- mcp__claude_ai_Linear__get_issue_status
- mcp__claude_ai_Linear__list_issue_labels
- mcp__claude_ai_Linear__create_issue_label
- mcp__claude_ai_Linear__save_project
- mcp__claude_ai_Linear__get_project
- mcp__claude_ai_Linear__list_projects
- mcp__claude_ai_Linear__save_milestone
- mcp__claude_ai_Linear__get_milestone
- mcp__claude_ai_Linear__list_milestones
---
# dev10x:linear — Linear Issue Tracker
## Orchestration
This skill follows `references/task-orchestration.md` patterns.
Create a task at invocation, mark completed when done:
**REQUIRED: Create a task at invocation.** Execute at startup:
1. `TaskCreate(subject="Linear issue operation", activeForm="Operating on Linear issue")`
Mark completed when done: `TaskUpdate(taskId, status="completed")`
Documentation-only skill centralizing Linear MCP tool references.
No scripts — all operations use MCP tools directly.
## Operation Mapping
| Operation | MCP Tool | Parameters |
|-----------|----------|------------|
| Get issue | `mcp__claude_ai_Linear__get_issue` | `id: "TEAM-133"` |
| List issues | `mcp__claude_ai_Linear__list_issues` | `team: "your-team-uuid"` |
| Create/update issue | `mcp__claude_ai_Linear__save_issue` | `id: "TEAM-133", state: "In Progress"` |
| List comments | `mcp__claude_ai_Linear__list_comments` | `issueId: "TEAM-133"` |
| Create comment | `mcp__claude_ai_Linear__create_comment` | `issueId: "TEAM-133", body: "..."` |
| List statuses | `mcp__claude_ai_Linear__list_issue_statuses` | `team: "your-team-uuid"` |
| Get status | `mcp__claude_ai_Linear__get_issue_status` | `id: "STATUS_UUID"` |
| List labels | `mcp__claude_ai_Linear__list_issue_labels` | `team: "your-team-uuid"` |
| Create label | `mcp__claude_ai_Linear__create_issue_label` | `team: "your-team-uuid", name: "label"` |
| Create/update project | `mcp__claude_ai_Linear__save_project` | `name: "Project", teamIds: ["UUID"]` |
| Get project | `mcp__claude_ai_Linear__get_project` | `id: "PROJECT_UUID"` |
| List projects | `mcp__claude_ai_Linear__list_projects` | `team: "TEAM_UUID"` |
| Create/update milestone | `mcp__claude_ai_Linear__save_milestone` | `name: "Phase 1", projectId: "UUID"` |
| Get milestone | `mcp__claude_ai_Linear__get_milestone` | `id: "MILESTONE_UUID"` |
| List milestones | `mcp__claude_ai_Linear__list_milestones` | `projectId: "UUID"` |
## Team IDs
| Team | UUID |
|------|------|
| YOUR_TEAM | `your-team-uuid` |
Replace `your-team-uuid` with the UUID from your Linear workspace settings.
To find it: Settings → Teams → select your team → the UUID is in the URL.
## URL Template
```
https://linear.app/your-org/issue/{TICKET_ID}
```
Example: `https://linear.app/your-org/issue/TEAM-133`
Replace `your-org` with your Linear organization slug.
## Prerequisite Check
Before using Linear MCP tools, verify availability:
1. Check if any `mcp__claude_ai_Linear__*` or `mcp__plugin_linear_linear__*` tool is available
2. If not available, inform the user:
```
Linear MCP is not enabled. Please enable the Linear MCP server
in your Claude Code settings to use this skill.
```
3. Do not proceed if Linear MCP is unavailable
## Project Assignment
**CRITICAL: Always resolve project UUID before assignment.**
The `save_issue` `project` parameter accepts a name, ID, or slug —
but name matching is exact and **fails silently** on mismatch.
`"app-pos-mcp"` vs `"app-pos mcp"` will succeed without error but
leave the ticket unlinked.
### Resolution Steps
1. **Resolve UUID first** — call `list_projects(team: "TEAM_UUID")`
and match by display name (case-insensitive, normalize hyphens
to spaces)
2. **Use the UUID** in all subsequent `save_issue` calls:
`save_issue(id: "TEAM-133", project: "PROJECT_UUID")`
3. **Verify linkage** — after `save_issue`, call
`get_issue(id: "TEAM-133")` and confirm the response contains
the expected `projectId`
### Batch Assignment Verification
After assigning multiple tickets to a project, verify all were
linked by calling `list_issues(project: "PROJECT_UUID")` and
checking that every expected ticket ID appears in the results.
## Searching for JTBD in Ticket
To find an existing Job Story on a Linear ticket:
1. Get issue: `mcp__claude_ai_Linear__get_issue(id: "TEAM-133")`
2. Search the description for `**When**` / `**[actor] wants to**` / `**so [beneficiary] can**` pattern (legacy `**I want to**` / `**so I can**` also matches)
3. For localized tickets, also search for translated structural labels in
the ticket language
4. If BDD or Gherkin-derived keywords appear, validate translations
against Cucumber's language reference:
https://cucumber.io/docs/gherkin/languages/
5. If not found, list comments: `mcp__claude_ai_Linear__list_comments(issueId: "TEAM-133")`
6. Search each comment body for the same pattern
7. Return the first match, or empty if none found
## MCP Tool Variants
Two MCP server configurations may provide Linear tools:
| Provider | Tool prefix | Notes |
|----------|-------------|-------|
| Claude AI (cloud) | `mcp__claude_ai_Linear__` | Available in Claude Code web/desktop |
| Plugin (local) | `mcp__plugin_linear_linear__` | Requires local MCP server config |
Both provide the same operations. Check for either prefix when
verifying availability.
Versions
The database has no other skills named dev10x:linear.
Database snapshot: 13.11.2026 · package version e1ad54516299 (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
- 90using-tracker
Use when the user mentions issues, tickets, tasks, epics, current work, sprint or cycle, backlog, creating or updating issues, or anything about task tracking and planning in any tracker (Linear, Jira, GitHub Issues, local files). Invoke BEFORE asking the user any question about… - 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… - 90tracker
Read, create and update tickets in whichever tracker the project uses (Linear, Jira, ClickUp, GitHub Issues, markdown files, or a custom one). Use whenever a task involves a ticket: reading its scope, creating one, moving its status, commenting. Never call tracker tools directly. - 100linear-cli
This skill should be used when the user asks to "create a Linear issue", "list Linear tickets", "start working on a ticket", "update Linear issue", "link PR to Linear", "view issue details", mentions "linear issue", "DEV-xxx", or needs to manage Linear issues from the command line. - 100writing-tickets
Write or rewrite an issue tracker ticket (Linear, GitHub Issues, Jira, or similar) that a person or coding agent will pick up. States the objective, evidence, decisions already made, hard rules, and done criteria, and leaves the how to the implementer. Use when the user says… - 100jira-integration
Use this skill when retrieving Jira tickets, analyzing requirements, updating ticket status, adding comments, or transitioning issues. Provides Jira API patterns via MCP or direct REST calls.