Skip to content
Product
Skill

/linear-monitor

Health-check Linear projects for slipping dates, stale In Progress, and orphan issues. Use when the user asks for a Linear health check, atRisk scan, monitoring, /linear-monitor, or when a Cursor Automation runs the Linear tracking health recipe. Default read + comment; no mass

BOOST
From plugin
linear-methodology
106 skills
Install
$ npx -y skills add tjcages/linear --skill linear-monitor --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/linear-monitor

Context preview

The summary Claude sees to decide when to auto-load this skill.

Health-check Linear projects for slipping dates, stale In Progress, and orphan issues. Use when the user asks for a Linear health check, atRisk scan, monitoring, /linear-monitor, or when a Cursor Automation runs the Linear tracking health recipe. Default read + comment; no mass

SKILL.md

linear-monitor.SKILL.md
name: linear-monitor
version: 1.0.2
description: >-
  Health-check Linear projects for slipping dates, stale In Progress, and
  orphan issues. Use when the user asks for a Linear health check, atRisk
  scan, monitoring, /linear-monitor, or when a Cursor Automation runs the
  Linear tracking health recipe. Default read + comment; no mass creates.
  NOT for bootstrap (linear-setup) or full rescue (linear-sync).

Linear monitor

Chat rules: [RESPONSE.md](./RESPONSE.md). Auth: [AUTH.md](./AUTH.md). Cadence: [METHODOLOGY.md](./METHODOLOGY.md) §6, §9, §20. Automation recipe: [AUTOMATION.md](./AUTOMATION.md).

Step 0 — auth

Probe Linear MCP. On failure → AUTH.md; **stop**.

Scope

User-named team/project, or all accessible teams if unset. **Never** soft-nudge git repos from Automation runs.

Checks (do now)

1. **Dates** — milestones/issues with targets approaching where work is not trending Done → candidates for `atRisk` (post only if health actually changes). 2. **Stale In Progress** — no comment >7 days → list with links. 3. **Orphans** — issues with no milestone → list. 4. **Anti-patterns glance** — milestone spam, status theater (§19); note only, don’t rewrite unasked.

Writes

  • **Default:** read + optional comment on existing issues with findings.
  • **Status updates:** only on real health changes (§20).
  • **Never:** mass-create issues; never reorganize structure (hand off to linear-sync).

Output shape

1. Findings first (≤5 bullets; overflow → later). 2. What you changed (if anything), with links. 3. ONE next action for the human.

Read more
Ships withlinear-methodology

A proven methodology for building and tracking features, projects, and issues across numerous builds.

Get the whole plugin
Stats
10
Stars
0
Forks
Maintained
Maintenance
JavaScript
Language
MIT
License
2mo ago
Last commit
3mo ago
Created
9d ago
Added

Repo: tjcages/linear

Other skills on linear-methodology.