● Communauté
wrsmith108
⚡ Instantané
linear-claude-skill
par 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.
Pourquoi l'utiliser
Fonctionnalités clés
- 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
Démo en direct
Aperçu en pratique
linear-claude-skill.replay
▶ prêt
Cas d'usage
Usages concrets : linear-claude-skill
Quand l'utiliser : Friday afternoon, you need to know what shipped this cycle, what slipped, and what to roll over.
Déroulement
-
Ask Claude to pull the current cycle
Show me every issue in the current cycle for team ENG — grouped by state, with the assignee.✓ Copié
→ 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?✓ Copié
→ 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.✓ Copié
→ Confirmation of the rollover + paste-ready recap
Résultat : A clean cycle close-out in 10 minutes instead of an hour.
Pièges
- Claude rolls over issues you meant to cancel — Tell it 'list first, confirm, then mutate' — keep a human checkpoint before writes
Combiner avec : github · slack
Quand l'utiliser : Monday morning, the Bugs project has 40 untriaged items and you need to cut the list.
Déroulement
-
List untriaged bugs
Find all issues in project 'Bugs' with no priority and no assignee, created in the last 14 days.✓ Copié
→ 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.✓ Copié
→ Reasoned suggestions, not blanket Medium
-
Apply the decisions
Apply those priorities and assign to the suggested teams. Confirm before each write.✓ Copié
→ Per-issue confirmation
Résultat : A fully triaged bug inbox with traceable reasoning per issue.
Pièges
- 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
Quand l'utiliser : Before a status review meeting or async update to stakeholders.
Déroulement
-
Gather project state
Summarize project 'Mobile v2.0': issue counts by state, % complete, and what's changed since last Monday.✓ Copié
→ Numeric snapshot + delta
-
Call out risks
List the top 3 risks — issues blocked, overdue, or with no owner.✓ Copié
→ Ranked risks with why
-
Draft the update
Write a 5-bullet status update: progress, shipped this week, next week, risks, asks.✓ Copié
→ Paste-ready paragraph or bullets
Résultat : A crisp stakeholder update you didn't have to write yourself.
Pièges
- Updates become uniformly 'on track' — Force Claude to pick actual risks from stale issues; don't let it round to green
Combinaisons
Associez-le à d'autres MCPs pour un effet X10
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.✓ Copié
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.✓ Copié
Coût et limites
Coût d'exécution
- Quota d'API
- Linear API: 1500 requests / hour on personal keys
- Tokens par appel
- 200–2000 tokens per report step
- Monétaire
- Free — Linear Free and Standard plans both support API access
- Astuce
- Batch GraphQL fields in one query — saves both rate limit and token budget
Sécurité
Permissions, secrets, portée
Portées minimales : read
Stockage des identifiants : Linear API key in env var (LINEAR_API_KEY). Never paste into the prompt.
Sortie de données : api.linear.app only
Ne jamais accorder : admin (org-wide write)
- Issues, projects, and cycles may contain confidential roadmap info — think twice before pasting into external tools.
Dépannage
Erreurs courantes et correctifs
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.
Vérifier : 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.
Alternatives
linear-claude-skill vs autres
| Alternative | Quand l'utiliser | Compromis |
|---|
| 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 |