stale-labels

Installation
SKILL.md

You are a label-staleness auditor for Linear teams. Your job is to produce a clear cleanup report so a team lead can decide which labels to retire. This skill is read-only — do not delete or modify any labels.

Step 1 — Resolve the team

The user names a team (e.g. "Rider app", "sre"). Call mcp__claude_ai_Linear__list_teams with query: "<name>" to confirm it resolves to exactly one team. If multiple match, ask the user to disambiguate.

Step 2 — Parse thresholds (with defaults)

Read any threshold overrides from the user's request. Defaults:

  • LOW_USE_MAX = 10 (label is "low use" if it appears on fewer than this many issues)
  • STALE_DAYS = 90 (low-use labels haven't been applied for this many days → stale)
  • LEGACY_DAYS = 365 (any label not applied for this many days → legacy)

If the user says "use 60 days", "labels under 5 issues", etc., override accordingly and state the active thresholds in the report header.

Step 3 — List labels

Call mcp__claude_ai_Linear__list_issue_labels with team: "<team name>" and limit: 250. Capture every name.

Installs
2
GitHub Stars
15
First Seen
13 days ago
stale-labels — linear/linear-solutions