Audit Linear issue labels for a named team and generate a tiered markdown report.
npx skills add https://github.com/linear/linear-solutions --skill stale-labels
Please help me install this Agent Skill. Skill: stale-labels Source: https://github.com/linear/linear-solutions/tree/main/Skills/stale-labels Command: npx skills add https://github.com/linear/linear-solutions --skill stale-labels
This Skill helps team leads identify unused, low-usage, and legacy labels in a Linear workspace so labels can be retired with confidence instead of being cleaned up blindly.
Ask to audit the labels for a specific team name and generate a tiered cleanup report with the default or specified staleness thresholds.
High-intent search queries and answers about installing and using this skill.
To find and clean up unused Linear labels, you can audit a specific team's labels to identify unused, low-use, and stale labels based on issue counts and recent activity. The audit generates a readable markdown report for review without modifying any labels.
The best way to audit stale Linear labels is to resolve a single team's labels, compute usage counts and most recent issue dates, and apply configurable staleness thresholds. This produces a tiered cleanup report separating unused, low-use, and legacy labels.
Yes, you can generate a tiered cleanup report that separates unused, low-use & stale, and legacy labels for retirement consideration. The report also lists active labels as counts for context, ensuring labels can be retired with confidence.
No, the stale label audit performs read-only analysis and does not delete or modify any labels. It is designed for audit-style workflows, providing a markdown report for manual action before any cleanup occurs.
You can configure staleness thresholds by setting LOW_USE_MAX, STALE_DAYS, and LEGACY_DAYS parameters. These thresholds evaluate label usage counts and most recent issue activity dates to categorize labels appropriately.
The label audit lists up to 250 labels for a named team. If your team exceeds this limit, labels beyond the 250 cap will not be included in the usage count and staleness evaluation report.
lobehubAutomate Linear issue status updates and completion comments via MCP tools.
VictoriaMetricsAnalyze VictoriaMetrics TSDB status and metric usage to produce a remediation report.
breethomasAnalyze Linear workspace health and usage patterns to surface structural, backlog, and hygiene issues.
cmbaysAudit GitHub issues for missing, deprecated, or inconsistent labels.
