linear-aging

Generate aging reports that assign one named owner to every stale issue in a tracker export.

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/JYeswak/grok_bot_playground --skill linear-aging-jyeswak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linear-aging
Source: https://github.com/JYeswak/grok_bot_playground/tree/main/plugin/skills/linear-aging
Command: npx skills add https://github.com/JYeswak/grok_bot_playground --skill linear-aging-jyeswak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Backlogs rot when stale issues have no clear owner: team labels, rotations, and shared assignees mean nobody acts. This Skill turns an issue tracker export into an aging report where every stale issue has exactly one named human owner, or is explicitly flagged as needing one. ## Core Features & Use Cases - Aging computation: Calculates issue age in days from a stated field (created, last status change, or last human comment) against a configurable threshold N, with checkable arithmetic. - Single-owner assignment: Names exactly one roster-approved owner per stale issue, falling back to a "needs an owner" label with the specific decision required. - Diff against prior runs: Reports newly stale issues, issues still stale and older, and issues resolved since the last report. - Use Case: Before a weekly triage meeting, run the report over your Linear workspace to get a ranked list of stale issues, each with one decider and a one-line next action. ## Quick Start Ask the assistant to generate an aging report for issues older than 30 days using the connected Linear workspace and the provided owner roster.

Frequently Asked Questions about linear-aging

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

FAQPage Schema
How do I find stale issues in Linear and assign owners?

Run an aging report over the Linear issue set with a threshold in days and an owner roster. Each stale issue gets exactly one named owner from the roster, or is filed under "needs an owner" with the decision required to assign it.

How is issue age calculated in an aging report?

Age is computed as the as-of date minus a stated field: created date, last status change, or last human comment. The report names which field was used and shows the field value so the arithmetic is checkable.

Can this skill edit, close, or reassign Linear issues?

No. The skill is strictly read-only and never creates, edits, closes, comments on, labels, or reassigns issues. A proposed owner is only a proposal; the owner's explicit approval on that exact reassignment is required, and all writes happen outside the skill.

What happens when a stale issue has no clear owner?

It is filed under "needs an owner" with the specific decision required and who can make it. A team name, label, rotation, or two names never counts as an owner, and candidates not on the supplied roster are never named.

What data source does the aging report use?

It reads issues through the linear-mcp tools (linear_list_teams, linear_list_issues, linear_get_issue) when connected, or a pasted export provided by the owner as a fallback. It never invents a tracker API or claims a connector that does not exist.