linear-monitor
tjcages/linear · Agent Skill
Health-check Linear projects for slipping dates, stale in-progress work, orphan issues, and tracking anti-patterns.
Jump to install ↓Overview
| Publisher | |
|---|---|
| Repository | tjcages/linear ↗ |
| Skill folder | linear-monitor |
| Stars | 10 |
| Bundled files | 7 |
| License | MIT |
| Last updated | July 29, 2026 |
| Links | Skill source ↗ · Repository ↗ |
Mozgi check
What we found in the skill files. Details come with a subscription.
Installation
A skill is a folder with a SKILL.md file. Pick your agent and run the commands in a terminal (macOS, Linux or Git Bash on Windows) from your project root.
Copy the prompt into Claude, Codex or another assistant: it will review the skill and install it for you.
Install the “linear-monitor” skill from mozgi.io (https://mozgi.io/skills/tjcages-linear-monitor/) for me. 1. Download the archive: https://mozgi.io/skills/tjcages-linear-monitor/download If it fails, take the skill folder from the source: https://github.com/tjcages/linear/tree/main/skills/linear-monitor 2. Read SKILL.md and the other files. Check the skill is safe: no hidden commands, no sending data elsewhere, no scripts doing something other than described. If anything looks suspicious, stop and tell me. 3. Put the “linear-monitor” folder into your agent's skills folder: .claude/skills/ for Claude Code, .agents/skills/ for Codex, .cursor/skills/ for Cursor, .gemini/skills/ for Gemini CLI. Inside the project if we are in one, otherwise in the home folder (~/.claude/skills/ etc.). 4. Make sure <skills folder>/linear-monitor/SKILL.md exists. 5. Briefly tell me what this skill does and offer to try it on my task. If you cannot do a step yourself, tell me what to click or type.
git clone --depth 1 --branch main https://github.com/tjcages/linear.git /tmp/linear mkdir -p .claude/skills cp -r /tmp/linear/skills/linear-monitor .claude/skills/linear-monitor
Restart Claude Code — the skill appears in the list; call it manually with /linear-monitor. For all projects use ~/.claude/skills.
git clone --depth 1 --branch main https://github.com/tjcages/linear.git /tmp/linear mkdir -p .agents/skills cp -r /tmp/linear/skills/linear-monitor .agents/skills/linear-monitor
Codex looks for skills in .agents/skills from the current folder up to the repo root; call one with /skills or $linear-monitor. For all projects use ~/.agents/skills.
git clone --depth 1 --branch main https://github.com/tjcages/linear.git /tmp/linear mkdir -p .cursor/skills cp -r /tmp/linear/skills/linear-monitor .cursor/skills/linear-monitor
Cursor picks the skill up on start; call it with “/” in Agent chat. Cursor also reads .claude/skills and .agents/skills. For all projects use ~/.cursor/skills.
git clone --depth 1 --branch main https://github.com/tjcages/linear.git /tmp/linear mkdir -p .gemini/skills cp -r /tmp/linear/skills/linear-monitor .gemini/skills/linear-monitor
Gemini CLI offers to activate the skill when a task matches — you approve it. For all projects use ~/.gemini/skills.
Read SKILL.md and any companion files before deciding whether to install. Click a file to preview it.
SKILL.md contents
Original author text · read-onlyLinear monitor
Chat rules: RESPONSE.md ↗. Auth: AUTH.md ↗. Cadence: METHODOLOGY.md ↗ §6, §9, §20. Automation recipe: 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.
Frequently asked questions
What does the linear-monitor skill do?
Health-check Linear projects for slipping dates, stale in-progress work, orphan issues, and tracking anti-patterns.
How do I install linear-monitor?
Open the “Installation” block on this page and pick your agent — Claude Code, Codex, Cursor or Gemini CLI — for ready-made commands that copy the skill folder to the right place. Or copy the prompt from the “Via assistant” tab and let the assistant review and install the skill.
Which AI models work with linear-monitor?
Skills are plain Markdown instructions (the Agent Skills format), so linear-monitor works with any agent that reads SKILL.md: Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and more. The model loads the instructions only when a task matches the skill's description.
Is linear-monitor free?
The skill is published openly by tjcages under the MIT license. The skill itself costs nothing — you only pay your AI provider for the tokens you use.
Is it safe to install skills?
A skill is a set of instructions your agent will follow, so read SKILL.md and its companion files before installing. Scripts in the skill folder only run if your agent runs them — keep an eye on what it does and do not grant unnecessary permissions.
How is a skill different from an MCP server or a plugin?
An MCP server or plugin gives the model new tools — code that runs and returns a result. A skill gives it knowledge and process: how to approach a task, which steps to follow and what good output looks like. It needs no server or API key.