linear-setup

tjcages/linear · Agent Skill

Bootstrap or extend Linear project tracking with evidence-based backfill, milestones, dependencies, and repository discipline.

Jump to install ↓

Overview

PublishertjcagesCommunity
Repositorytjcages/linear ↗
Skill folderlinear-setup
Stars10
Bundled files7
LicenseMIT
Last updatedJuly 29, 2026
LinksSkill source ↗ · Repository ↗

Mozgi check

What we found in the skill files. Details come with a subscription.

Security
low risk · no obvious risks found — the full report shows the details
Compatibility
instructions only — works with most agents
Similar skills
144 similar skills found
Also with 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-setup” skill from mozgi.io (https://mozgi.io/skills/tjcages-linear-setup/) for me.

1. Download the archive: https://mozgi.io/skills/tjcages-linear-setup/download
   If it fails, take the skill folder from the source: https://github.com/tjcages/linear/tree/main/skills/linear-setup
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-setup” 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-setup/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.

Review the source files

7 files Download Zip

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-only

Linear setup

Chat rules: RESPONSE.md ↗. Auth: AUTH.md ↗. Full method: 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)

CHANGELOG > roadmap > git log. Feature-level default; per-release for launched packages. Done only with evidence. Doc “done” ≠ proof — corroborate (§4.8).

Writing (tickets)

Titles ≤8 words. Descriptions ≤3 sentences or ≤5 bullets. Comments ≤3 lines. Screenshots over prose (§10).

6. Wire (§4, §10, §11)

Real blockedBy/blocks. Surface UI-only items early (§11). Add README as Linear project document.

7. Install discipline (§5)

Write the tracking protocol into always-loaded agent instructions (CLAUDE.md / AGENTS.md / .cursor/rules/) with real team/project/milestone names. Bootstrap is not done without this.

8. Honesty (§6, §9)

Status updates at milestone/health moments only. atRisk before dates slip.

9. Done check (§18, §26)

Rubric ≥16/20 with no load-bearing 0, or full §26 audit.

After setup

Point user to always-on (if missing) via finish linear-tracking install. Optional Cursor weekly health: AUTOMATION.md ↗. One next action.

Frequently asked questions

What does the linear-setup skill do?

Bootstrap or extend Linear project tracking with evidence-based backfill, milestones, dependencies, and repository discipline.

How do I install linear-setup?

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-setup?

Skills are plain Markdown instructions (the Agent Skills format), so linear-setup 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-setup 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.

Related skills

All skills →