stale-labels

Name: stale-labels
Availability: InStock
Author: Linear

Audit Linear issue labels for a named team and generate a tiered markdown report.

18|13|Updated Oct 17, 2025

Search Tags:#linear #workflow hygiene #stale detection #label audit #issue metrics #team operations

Ready to run

npx skills add https://github.com/linear/linear-solutions --skill stale-labels

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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.

Core Features & Use Cases

Label staleness auditing for a specific team: Resolves a named team, enumerates its labels, and evaluates label usage by issue count and most-recent issue activity.
Tiered cleanup reporting: Produces a clear report separating Unused, Low-use & stale, and Legacy labels, while also listing active labels (as counts) for context.
Read-only safety: Performs analysis only and does not delete or modify any labels, making it suitable for audit-style workflows before any manual action.

Quick Start

Ask to audit the labels for a specific team name and generate a tiered cleanup report with the default or specified staleness thresholds.

Frequently Asked Questions about stale-labels

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I find and clean up unused Linear labels in my workspace?▼

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.

What is the best way to audit stale Linear labels for a specific team?▼

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.

Can I see which Linear labels are considered legacy or low-use before deleting them?▼

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.

Does the stale label audit automatically delete or modify labels in Linear?▼

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.

How do I configure staleness thresholds for a Linear label audit?▼

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.

What happens if my team has more than 250 labels in Linear?▼

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.