/ Diretório / Playground / linear-claude-skill
● Comunidade wrsmith108 ⚡ Instantâneo

linear-claude-skill

por wrsmith108 · wrsmith108/linear-claude-skill

A Claude skill that teaches the agent how to manage Linear issues, projects, and cycles through the Linear MCP and SDK.

Clone this skill into ~/.claude/skills/ and Claude gets a working mental model of Linear — teams, cycles, issue states, GraphQL queries, and common automations. It wraps the Linear MCP (or direct SDK calls) with opinionated patterns so the agent does triage, rollovers, and project reporting without reinventing the API each turn.

Por que usar

Principais recursos

Demo ao vivo

Como fica na prática

linear-claude-skill.replay ▶ pronto
0/0

Instalar

Escolha seu cliente

~/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
    }
  }
}

Abra Claude Desktop → Settings → Developer → Edit Config. Reinicie após salvar.

~/.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 usa o mesmo esquema mcpServers que o Claude Desktop. Config de projeto vence a global.

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
    }
  }
}

Clique no ícone MCP Servers na barra lateral do Cline, depois "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
    }
  }
}

Mesmo formato do Claude Desktop. Reinicie o Windsurf para aplicar.

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

O Continue usa um array de objetos de servidor em vez de um map.

~/.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"
        ]
      }
    }
  }
}

Adicione em context_servers. Zed recarrega automaticamente ao salvar.

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

Uma linha só. Verifique com claude mcp list. Remova com claude mcp remove.

Casos de uso

Usos do mundo real: 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

Quando usar: Friday afternoon, you need to know what shipped this cycle, what slipped, and what to roll over.

Pré-requisitos
  • 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
Fluxo
  1. Ask Claude to pull the current cycle
    Show me every issue in the current cycle for team ENG — grouped by state, with the assignee.✓ Copiado
    → Table: Backlog / In Progress / In Review / Done with issue IDs
  2. Diagnose slips
    Which issues are still In Progress or In Review with 2 days left? Who owns them?✓ Copiado
    → Per-issue one-liner with risk call-out
  3. Roll over and write the recap
    Roll incomplete issues into the next cycle and draft a Slack recap of what actually shipped.✓ Copiado
    → Confirmation of the rollover + paste-ready recap

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

Armadilhas
  • Claude rolls over issues you meant to cancel — Tell it 'list first, confirm, then mutate' — keep a human checkpoint before writes
Combine com: github · slack

Triage the bug inbox with prioritization rationale

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

Quando usar: Monday morning, the Bugs project has 40 untriaged items and you need to cut the list.

Fluxo
  1. List untriaged bugs
    Find all issues in project 'Bugs' with no priority and no assignee, created in the last 14 days.✓ Copiado
    → Ranked table with titles
  2. Suggest priority + owner
    For each, suggest priority (Urgent/High/Medium/Low) and the most-likely team based on the file paths or labels mentioned.✓ Copiado
    → Reasoned suggestions, not blanket Medium
  3. Apply the decisions
    Apply those priorities and assign to the suggested teams. Confirm before each write.✓ Copiado
    → Per-issue confirmation

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

Armadilhas
  • 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
Combine com: github

Generate a project status update from Linear

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

Quando usar: Before a status review meeting or async update to stakeholders.

Fluxo
  1. Gather project state
    Summarize project 'Mobile v2.0': issue counts by state, % complete, and what's changed since last Monday.✓ Copiado
    → Numeric snapshot + delta
  2. Call out risks
    List the top 3 risks — issues blocked, overdue, or with no owner.✓ Copiado
    → Ranked risks with why
  3. Draft the update
    Write a 5-bullet status update: progress, shipped this week, next week, risks, asks.✓ Copiado
    → Paste-ready paragraph or bullets

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

Armadilhas
  • Updates become uniformly 'on track' — Force Claude to pick actual risks from stale issues; don't let it round to green
Combine com: github

Combinações

Combine com outros MCPs para 10× de alavancagem

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.✓ Copiado
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.✓ Copiado

Ferramentas

O que este MCP expõe

FerramentaEntradasQuando chamarCusto
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

Custo e limites

O que custa rodar

Cota de API
Linear API: 1500 requests / hour on personal keys
Tokens por chamada
200–2000 tokens per report step
Monetário
Free — Linear Free and Standard plans both support API access
Dica
Batch GraphQL fields in one query — saves both rate limit and token budget

Segurança

Permissões, segredos, alcance

Escopos mínimos: read
Armazenamento de credenciais: Linear API key in env var (LINEAR_API_KEY). Never paste into the prompt.
Saída de dados: api.linear.app only
Nunca conceda: admin (org-wide write)

Solução de problemas

Erros comuns e correções

Skill doesn't activate

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

Verificar: 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.

Verificar: 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.

Alternativas

linear-claude-skill vs. outros

AlternativaQuando usarTroca
Linear MCP (official)You want a JSON-RPC tool surface rather than a prompt skillMCP gives real tools; skill gives better defaults and reporting prose
Jira skillYour team uses Jira instead of LinearDifferent data model entirely

Mais

Recursos

📖 Leia o README oficial no GitHub

🐙 Ver issues abertas

🔍 Ver todos os 400+ servidores MCP e Skills