linear-monitor skillA
linear-monitor is agent-read markdown (skill) from tjcages/skills: 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)..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# 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 the whole file at its exact version.
How to install
mdr add tjcages/skills/linear-monitor@v1.0.2mdr add tjcages/skills/linear-monitor@sha256:18993a6c56f61f32Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_wkswn6ek3ukhb36a)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.2 latest | 2026-08-25 | b7cbce9 | 1,640 B | A | view · diff |
| v1.0.2 | 2026-07-29 | 6e8c949 | 1,613 B | A | view · diff |
| v1.0.1 | 2026-07-21 | 07b7a5a | 1,613 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (1640 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
tjcages/skills · 4 stars · license none · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_wkswn6ek3ukhb36a GET https://markdownregistry.com/api/v1/resolve?ref=tjcages/skills/linear-monitor GET https://markdownregistry.com/api/v1/blob/18993a6c56f61f32d0a6c111217d9079dab6d8520d57a2e5514657180b4a3d18
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.