linear-issue-trackerlisted
Install: claude install-skill thientranhung/astragentic
# Tracker adapter: Linear
**Measured on a live project that ran Linear until 2026-08-21.** What the pipeline
requires of *any* tracker is `.agents/tracker-contract.md`; this file is the HOW for one of them.
**The project half stays in the project.** Workspace, team key, project id and the ticket prefix
live in the project's `docs/agents/issue-tracker.md`.
Reach it through the **`linear-server` MCP tools**. Do not shell out to a CLI.
## Read this before choosing Linear
**The free tier stops accepting new issues.** `save_issue` returns
`"You've exceeded the free issue limit"`, and that does not degrade a pipeline — it **stops**
one, because the first step of the method is `create`. A project hit this and had to migrate the
same day.
Requirements 1–5 are about a tracker's *model*. A tracker also has to accept a write. **Check the
ceiling of the tier you are on before building a pipeline on it.**
That aside, Linear is the shape the other two adapters approximate: native workflow states, a
real status field, a board that follows it with no second write, native relations, native
assignee. All five requirements met by the product, which is why this adapter is the thin one.
## Conventions
- **Create** — `save_issue` with `team`, `project`, `title`, markdown `description`. Omit `id`.
- **Read** — `get_issue` with the identifier, then `list_comments` for the discussion.
- **List** — `list_issues` filtered by `team`, `project`, `state`, `label`, `assignee`.
- **Comment** — `sav