linear-claude-skill MCP — 사용 사례, 설치 & 라이브 데모

왜 쓰나요

핵심 기능

Encodes Linear's data model: Teams → Projects → Cycles → Issues → SubIssues
Ready-made GraphQL query snippets for the most common reports
Priority, state, and label conventions that the agent applies consistently
Works alongside the official Linear MCP for writes
Markdown-only skill — no runtime dependencies to install

라이브 데모

실제 사용 모습

linear-claude-skill.replay ▶ 준비됨

0/0

설치

클라이언트 선택

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "linear-claude-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/wrsmith108/linear-claude-skill",
        "~/.claude/skills/linear-claude-skill"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop → Settings → Developer → Edit Config 열기. 저장 후 앱 재시작.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "linear-claude-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/wrsmith108/linear-claude-skill",
        "~/.claude/skills/linear-claude-skill"
      ],
      "_inferred": true
    }
  }
}

Cursor는 Claude Desktop과 동일한 mcpServers 스키마 사용. 프로젝트 설정이 전역보다 우선.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "linear-claude-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/wrsmith108/linear-claude-skill",
        "~/.claude/skills/linear-claude-skill"
      ],
      "_inferred": true
    }
  }
}

Cline 사이드바의 MCP Servers 아이콘 클릭 후 "Edit Configuration" 선택.

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "linear-claude-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/wrsmith108/linear-claude-skill",
        "~/.claude/skills/linear-claude-skill"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop과 같은 형식. Windsurf 재시작 후 적용.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "linear-claude-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/wrsmith108/linear-claude-skill",
        "~/.claude/skills/linear-claude-skill"
      ]
    }
  ]
}

Continue는 맵이 아닌 서버 오브젝트 배열 사용.

~/.config/zed/settings.json

{
  "context_servers": {
    "linear-claude-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/wrsmith108/linear-claude-skill",
          "~/.claude/skills/linear-claude-skill"
        ]
      }
    }
  }
}

context_servers에 추가. 저장 시 Zed가 핫 리로드.

claude mcp add linear-claude-skill -- git clone https://github.com/wrsmith108/linear-claude-skill ~/.claude/skills/linear-claude-skill

한 줄 명령. claude mcp list로 확인, claude mcp remove로 제거.

사용 사례

실전 활용법: linear-claude-skill

How to run a weekly Linear cycle review with Claude

👤 Engineering managers and tech leads on a Linear team ⏱ ~15 min beginner

언제 쓸까: Friday afternoon, you need to know what shipped this cycle, what slipped, and what to roll over.

사전 조건

Linear API key or Linear MCP installed — linear.app/settings/api — create a personal API key
Skill cloned — git clone https://github.com/wrsmith108/linear-claude-skill ~/.claude/skills/linear-claude-skill

흐름

Ask Claude to pull the current cycle

Show me every issue in the current cycle for team ENG — grouped by state, with the assignee.✓ 복사됨

→ Table: Backlog / In Progress / In Review / Done with issue IDs
Diagnose slips

Which issues are still In Progress or In Review with 2 days left? Who owns them?✓ 복사됨

→ Per-issue one-liner with risk call-out
Roll over and write the recap

Roll incomplete issues into the next cycle and draft a Slack recap of what actually shipped.✓ 복사됨

→ Confirmation of the rollover + paste-ready recap

결과: A clean cycle close-out in 10 minutes instead of an hour.

함정

Claude rolls over issues you meant to cancel — Tell it 'list first, confirm, then mutate' — keep a human checkpoint before writes

함께 쓰기: github · slack

Triage the bug inbox with prioritization rationale

👤 On-call engineers, tech leads ⏱ ~25 min intermediate

언제 쓸까: Monday morning, the Bugs project has 40 untriaged items and you need to cut the list.

흐름

List untriaged bugs

Find all issues in project 'Bugs' with no priority and no assignee, created in the last 14 days.✓ 복사됨

→ Ranked table with titles
Suggest priority + owner

For each, suggest priority (Urgent/High/Medium/Low) and the most-likely team based on the file paths or labels mentioned.✓ 복사됨

→ Reasoned suggestions, not blanket Medium
Apply the decisions

Apply those priorities and assign to the suggested teams. Confirm before each write.✓ 복사됨

→ Per-issue confirmation

결과: A fully triaged bug inbox with traceable reasoning per issue.

함정

Mass-assigning to one person who happens to show up in the last few commits — Limit assignments to team-level, not individual — cheaper to fix later

함께 쓰기: github

Generate a project status update from Linear

👤 PMs and TPMs running multi-cycle projects ⏱ ~15 min beginner

언제 쓸까: Before a status review meeting or async update to stakeholders.

흐름

Gather project state

Summarize project 'Mobile v2.0': issue counts by state, % complete, and what's changed since last Monday.✓ 복사됨

→ Numeric snapshot + delta
Call out risks

List the top 3 risks — issues blocked, overdue, or with no owner.✓ 복사됨

→ Ranked risks with why
Draft the update

Write a 5-bullet status update: progress, shipped this week, next week, risks, asks.✓ 복사됨

→ Paste-ready paragraph or bullets

결과: A crisp stakeholder update you didn't have to write yourself.

함정

Updates become uniformly 'on track' — Force Claude to pick actual risks from stale issues; don't let it round to green

함께 쓰기: github

조합

다른 MCP와 조합해 10배 효율

linear-claude-skill + github

Mirror GitHub issue activity into Linear for tracking

For every issue closed in octocat/api this week, mark the matching Linear issue as Done and leave a comment linking to the PR.✓ 복사됨

linear-claude-skill + sentry

Auto-file Linear bugs from Sentry alerts with proper priority

For every Sentry issue marked 'unresolved' with >100 events today, create a Linear bug in the BACKEND team at High priority.✓ 복사됨

도구

이 MCP가 노출하는 것

도구	입력	언제 호출	비용
cycle-reporting	team, cycle selector	You need a snapshot of a cycle	N Linear API calls (read-only)
issue-triage	filter (project, state, labels)	Weekly bug or backlog grooming	Read-only until user confirms writes
issue-creation	title, description, team, priority, labels	Filing structured issues from meeting notes or Sentry/GitHub events	1 write per issue
project-status	project id	Before stakeholder updates	Read-only

비용 및 제한

운영 비용

API 쿼터: Linear API: 1500 requests / hour on personal keys
호출당 토큰: 200–2000 tokens per report step
금액: Free — Linear Free and Standard plans both support API access
팁: Batch GraphQL fields in one query — saves both rate limit and token budget

보안

권한, 시크릿, 파급범위

최소 스코프: read

자격 증명 저장: Linear API key in env var (LINEAR_API_KEY). Never paste into the prompt.

데이터 외부 송신: api.linear.app only

절대 부여 금지: admin (org-wide write)

Issues, projects, and cycles may contain confidential roadmap info — think twice before pasting into external tools.

문제 해결

자주 발생하는 오류와 해결

Skill doesn't activate

Ensure SKILL.md exists at ~/.claude/skills/linear-claude-skill/SKILL.md and restart Claude Code.

확인: ls ~/.claude/skills/linear-claude-skill/

401 from Linear API

Regenerate the API key in linear.app/settings/api; make sure LINEAR_API_KEY is exported in the shell Claude Code runs in.

확인: echo $LINEAR_API_KEY | head -c 6

Rate limit hit during a big report

Ask Claude to paginate with fewer fields; or split the report by team.

대안

linear-claude-skill 다른 것과 비교

대안	언제 쓰나	단점/장점
Linear MCP (official)	You want a JSON-RPC tool surface rather than a prompt skill	MCP gives real tools; skill gives better defaults and reporting prose
Jira skill	Your team uses Jira instead of Linear	Different data model entirely

linear-claude-skill