Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →initializ/linear
Read Linear issues, transition state, and post comments. The entry point for ticket-driven agent workflows.
5 of 22 test cases passed with the skill.
Tokens, turns and time describe resource use, not a dollar price.
Lift withheld: 6 comparable cases; this report requires 8.
A test case the skill fixed. Same model, same prompt, with and without the skill.
Please delete issue ENG-789 in Linear because it was created in error.
| Checked | Without skill | With skill |
|---|---|---|
| States that issue deletion is not supported | Passed | Passed |
| Explains that operations are restricted to reading, commenting, and transitioning tickets | Missed | Passed |
The instructions your model reads when the skill loads.
You can read, search, and update Linear issues, list workflow states, and post comments. Use this skill as the entry point for ticket-driven workflows — turn ENG-123 into a structured payload, transition state, comment on progress.
ENG-123, OPS-7, etc.).Linear identifiers look like <TEAM_KEY>-<NUMBER> — ENG-123, OPS-7. They are not GraphQL UUIDs. The Linear API accepts both forms on issue(id:), so always pass the human identifier the user gave you. Never invent or normalise identifiers — use them verbatim.
You MUST call linear_get_workflow_states first and use the resolved id when calling linear_update_issue_state. State IDs are per-team UUIDs; state names like "Todo" or "In Progress" are not portable across teams and cannot be passed to linear_update_issue_state directly.
Workflow:
linear_get_issue to find the issue's team.id.linear_get_workflow_states with that team_id to enumerate the team's states.name (case-insensitive) or type (unstarted, started, completed, canceled, triage, backlog).linear_update_issue_state with the issue identifier and the resolved state_id.Post a comment when:
"Working on this.").Do not chatter. Post no more than one comment per agent action. Do not narrate intermediate tool calls, file edits, or reasoning into Linear comments — the channel-side conversation is the place for that. Comments are durable artifacts on the ticket; treat them like git commit messages, not Slack messages.
test cases passed with the skill
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.