agentleFS
Sign inStart free
DROOdotFOODROOdotFOO/agent-skills/skills/linear/SKILL.md

linear

Skill1 starsChanged 2 months agoMITView on GitHub

Linear MCP reference for issues, projects, cycles, milestones, comments, documents, releases, and diffs through Linear's hosted MCP server. TRIGGER when: user mentions Linear, a Linear issue key like LIN-123 or ENG-42, asks to create/update/find Linear issues or projects, summarize a cycle, post standup notes to Linear, or uses linear MCP tools. DO NOT TRIGGER when: user asks for GitHub issues or PRs (use prd-to-plan, qa, or watchdog skills), or configures the raxol-symphony Linear tracker (use raxol-symphony skill).

83 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use agent-deep-links, helium-mcp and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ComposioHQSkill

    agent-deep-links

    Build, validate, and troubleshoot deep links for Codex, Cursor, VS Code, Visual Studio, and similar tools. Use when users ask for clickable links (especially in Slack) that open threads, files, folders, or app settings.

    Also in 3 projects that use this

  • ComposioHQSkill

    helium-mcp

    Search real-time news with bias scoring, get live stock/ETF/crypto data with AI analysis, ML options pricing, balanced news synthesis, and meme search via the Helium MCP server.

    Also in 3 projects that use this

  • petestewartSkill

    datadog-logs

    Query Datadog logs via the Logs Search API v2. Use when the user asks to "check the logs", "search logs", "find errors in Datadog", "look up logs for", "show me production logs", "check for errors", "search Datadog", or any request involving log search, error investigation, or production debugging that requires Datadog log data.

    Also in 3 projects that use this

  • OpenAISkill

    pull

    Also in 5 projects that use this

  • SentrySkill

    datadog

    Query live Datadog telemetry (logs, metrics, traces, spans, monitors, incidents, dashboards, services, hosts) through Datadog's Pup CLI. Use when users ask to investigate production behavior in Datadog, including searching logs, checking monitor status, inspecting traces or spans, looking up incidents, finding services, or correlating metrics. Do not use it for Sentry issues, repository/source-code work, or ticketing.

    Also in 4 projects that use this

  • +7 more from ComposioHQ

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 79 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Never invent an issue key, team, or project.

    line 26
  2. Distinctive:

    Before any write that touches more than one object (bulk comments, project scaffolding, label replacement), show the exact plan and wait …

    line 30

“Common” is measured: kept by at least 6 in 10 of the 79 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Linear MCP

Linear's hosted MCP server (https://mcp.linear.app/mcp, Streamable HTTP, OAuth 2.1). 68 tools on read-write, 38 on /mcp/readonly. Tool names are mcp__linear__<tool> in hosts that namespace MCP tools.

Strict rules

  • Never invent an issue key, team, or project. Resolve names with list_teams, list_projects, list_users, list_issue_statuses before writing.
  • save_* tools create when id is omitted and update when it is set. Never pass id on create; never omit it on update.
  • Before any write that touches more than one object (bulk comments, project scaffolding, label replacement), show the exact plan and wait for approval.
  • labels replaces the whole label set; use addLabels / removeLabels for incremental changes.
  • share_issue, unshare_issue, submit_diff_review, merge_diff, and every delete_* / retire_* tool require an explicit user request.

Identifiers

ObjectAccepts
IssueLIN-123 key or UUID
ProjectP-ENG-123, slug, name, or UUID
Teamkey, name, or UUID
UserUUID, name, email, or "me"
Cyclename, number, or UUID
Statetype (triage, started, ...), name, or UUID

Workspace: get_workspace. Current user's queue: list_issues(assignee="me").

Endpoint choice

NeedEndpoint
Create/update anythinghttps://mcp.linear.app/mcp
Reporting, summaries, triagehttps://mcp.linear.app/mcp/readonly

/mcp/readonly is enforced server-side: write tools are absent from tools/list and tools/call on one returns Tool save_issue not found, even with a read-write token. The /sse endpoint is deprecated.

Reference

FileTopic
tools-reference.mdAll 68 tools grouped by object, RO flag, arguments
usage-patterns.mdStandup -> comments, plan -> project, cycle report
mcp-setup.mdClaude Code, Codex, Raxol setup and re-auth

What You Get

  • Complete, live-captured inventory of Linear MCP tools with read-only markers and key arguments.
  • Identifier resolution rules and write guardrails that avoid duplicate issues and destructive label/relation edits.
  • Host setup for Claude Code, Codex, and Raxol, including read-only pinning and OAuth recovery.

See also

  • raxol-symphony -- tracker-driven agent orchestration that reads Linear via GraphQL
  • prd-to-plan -- PRD to phased plan; GitHub issue output
  • qa -- bug triage and GitHub issue creation
  • prepper -- pre-session briefings

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free