linear-setup skillA
linear-setup is agent-read markdown (skill) from tjcages/skills: Bootstrap or extend Linear project tracking the right way — methodology, not API CRUD. Use when the user asks to set up Linear tracking, track this project in Linear, add this repo to Linear, backfill history, get ready to track, or consents after a soft-nudge from linear-discipline. Anchors to North Star, backfills Done with evidence, wires blockedBy, installs per-repo discipline. NOT for one-off issue create/comment — Linear MCP handles that..
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 setup Chat rules: [RESPONSE.md](./RESPONSE.md). Auth: [AUTH.md](./AUTH.md). Full method: [METHODOLOGY.md](./METHODOLOGY.md). ## Step 0 — auth Probe Linear MCP. On failure → AUTH.md steps for this agent; **stop**. Never invent API calls. ## Operating order Follow **in sequence**. Early gates exist because getting them wrong corrupts live workflows. ### 1. Already tracked? (§1a) Search Linear by repo name **and** ask the user. Never assume blank slate. - **Nothing** → fresh bootstrap; continue. - **Exists** → STOP. Enumerate issues/milestones/labels/docs/status updates → summarize → per-category yes/no **before any write**. Extend conservatively. Scan repo for unmirrored roadmap docs (§4.7). ### 2. North Star (§1b) README-as-vision is usually enough — say the call out loud. Question 5 (why track?) picks the shape — see METHODOLOGY goal→shape table. ### 3–4. Type + structure (§2–§3) Suggested types: Product / Tool / Drop / Marketing. Milestones 1:1 with real phases. Separate engineering / launch / rollout tracks. Dates only with a real signal. Prefer §17 if shape is unclear. ### 5. Backfill (§4) …
Read the whole file at its exact version.
How to install
mdr add tjcages/skills/linear-setup@v1.0.2mdr add tjcages/skills/linear-setup@sha256:effcfdf8f066d6e0Pin 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_ovmjoelxcilgfn6d)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.2 latest | 2026-08-25 | b7cbce9 | 2,746 B | A | view · diff |
| v1.0.2 | 2026-07-29 | 6e8c949 | 2,719 B | A | view · diff |
| v1.0.1 | 2026-07-21 | 07b7a5a | 2,719 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 (2746 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_ovmjoelxcilgfn6d GET https://markdownregistry.com/api/v1/resolve?ref=tjcages/skills/linear-setup GET https://markdownregistry.com/api/v1/blob/effcfdf8f066d6e0d656177555be6f382e9a6e34bf9a6b4df683c59a6491c766
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.