Agent skill

Linear

by initializ in initializ/forge

Read Linear issues, transition state, and post comments. An agent skill from initializ/forge.

Apache-2.0Auto-check passed

Install Linear

skills CLI
$ npx skills add initializ/forge --skill linear -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install initializ/forge linear --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/initializ/forge.git skills-src && mkdir -p .claude/skills && cp -r skills-src/forge-skills/local/embedded/linear .claude/skills/linear && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
linear
GitHub stars
223
Token cost
~1.9k tokens
SKILL.md length
754 words
Files
8 (incl. scripts)
Skills in repo
15
Repo updated
First seen
Licence
Apache-2.0

At a glance

Read Linear issues, transition state, and post comments. An agent skill from initializ/forge.

  • Works in 4 steps: linear_get_issue to find the issue's… → linear_get_workflow_states with that… → Pick the state by matching its name… → …
  • SKILL.md covers When to use this skill, Issue identifier format, State transition pattern (hard… and Commenting etiquette, plus 7 more sections
  • Runs Shell scripts from its folder; reaches linear.app; needs TEAM_KEY

What it does

Linear is an agent skill from initializ/forge. Read Linear issues, transition state, and post comments. The entry point for ticket-driven agent workflows.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including scripts (for example `scripts/common.sh`, `scripts/linear-add-comment.sh` and `scripts/linear-get-issue.sh`).

It works with Linear. The repository describes itself as: Forge is the open-source runtime for Anthropic's Agent Skills standard — built for the agent that runs next to a service, in your environment, on infrastructure you already… The licence is Apache-2.0.

Example prompts

  • “/linear”

Requirements

  • A Bash shell
  • A credential in LINEAR_API_KEY
  • A credential in TEAM_KEY

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. linear_get_issue to find the issue's team.id.
  2. linear_get_workflow_states with that team_id to enumerate the team's states.
  3. Pick the state by matching its name (case-insensitive) or type (unstarted, started, completed, canceled, triage, backlog).
  4. linear_update_issue_state with the issue identifier and the resolved state_id.

What it can do on your machine

Read from SKILL.md and the folder at commit 3c608d8. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 7 files in scripts/ (Shell), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • linear.app

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • TEAM_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Linear loads about 1.9k tokens when it runs. Until then it costs about 29 tokens; SKILL.md has 754 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~29
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from initializ/forge at commit 3c608d8, republished under its Apache-2.0 licence (© initializ). 754 words, ~1,908 tokens.

Download SKILL.mdSave it as .claude/skills/linear/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
linear
description
Read Linear issues, transition state, and post comments. The entry point for ticket-driven agent workflows.
icon
📋
category
project-management
tags
linear, issue-tracking, tickets, workflow

Linear Skill

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.

When to use this skill

  • The user references a Linear issue by identifier (ENG-123, OPS-7, etc.).
  • The user asks for "my tickets" / "open issues" / "what's assigned to me".
  • An automation needs to mark work started, post a PR link as a comment, or move a ticket through workflow states.

Issue identifier format

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.

State transition pattern (hard rule)

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:

  1. linear_get_issue to find the issue's team.id.
  2. linear_get_workflow_states with that team_id to enumerate the team's states.
  3. Pick the state by matching its name (case-insensitive) or type (unstarted, started, completed, canceled, triage, backlog).
  4. linear_update_issue_state with the issue identifier and the resolved state_id.

Commenting etiquette

Post a comment when:

  • Work has been picked up (one comment, e.g. "Working on this.").
  • A pull request has been opened (one comment with the PR URL).
  • Work is blocked and the user should know.
  • Work is complete (one comment summarising what shipped).

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.

Safety rules

  • Never include secrets, tokens, or environment variable values in comment bodies.
  • Never transition an issue to a "Done" or "Completed" state without explicit user confirmation.
  • Never delete issues, comments, or projects through this skill — the tools don't support it. If the user asks, tell them this skill is read/comment/transition only.
  • When the user asks for "my tickets", default to state filter "Todo" or "In Progress" (state types unstarted, started) unless they specify otherwise.

Tool: linear_get_issue

Fetch a Linear issue by its human identifier.

Input:

ParameterTypeRequiredDescription
identifierstringyesIssue identifier like ENG-123

Output:

json
{
  "identifier": "ENG-123",
  "title": "...",
  "description": "...",
  "state": { "id": "...", "name": "In Progress", "type": "started" },
  "assignee": { "email": "...", "name": "..." },
  "team": { "id": "...", "key": "ENG", "name": "Engineering" },
  "labels": ["bug", "p1"],
  "priority": 2,
  "url": "https://linear.app/..."
}
Show full SKILL.md (348 more words)Show less

Tool: linear_search_issues

Filter issues across one team — or across all teams the API key can see, if no team is supplied. All parameters are optional. Call this tool with {} when the user asks something broad like "list open issues" or "what's in the backlog" — do not ask for a team_id first; the result will include the team key in each issue's identifier (e.g. ENG-12 vs OPS-7) and the user can drill down from there.

Input:

ParameterTypeRequiredDescription
team_idstringnoLinear team UUID or team key like ENG. Auto-detects which form. Defaults to $LINEAR_DEFAULT_TEAM_ID when set.
statestringnoWorkflow state type (unstarted, started, completed, canceled, triage, backlog).
assignee_emailstringnoFilter by assignee email.
labelstringnoFilter by label name.
querystringnoFree-text search over title and description.
limitintegernoMax results (default 20, capped at 100).

Examples — call the tool directly, do not ask the user for an ID:

User saysTool input
"list open issues" / "what's in the backlog"{}
"show me INI tickets"{"team_id": "INI"} (team key works)
"open bugs in ENG"{"team_id": "ENG", "state": "unstarted", "label": "bug"}
"what's @alice working on?"{"assignee_email": "alice@example.com", "state": "started"}

Output:

json
{
  "count": 3,
  "issues": [
    { "identifier": "ENG-1", "title": "...", "state": "Todo", "assignee_email": "...", "url": "..." }
  ]
}

Tool: linear_list_my_issues

List issues assigned to the API key's owner (viewer).

Input:

ParameterTypeRequiredDescription
statestringnoComma-separated state types. Default: "started,unstarted" ("In Progress" / "Todo").
limitintegernoMax results (default 20, capped at 100).

Output: same shape as linear_search_issues.

Tool: linear_get_workflow_states

Enumerate a team's workflow states. Required before linear_update_issue_state.

Input:

ParameterTypeRequiredDescription
team_idstringyesLinear team UUID (from linear_get_issue's team.id).

Output:

json
{
  "team_id": "...",
  "states": [
    { "id": "...", "name": "Todo",        "type": "unstarted", "position": 0 },
    { "id": "...", "name": "In Progress", "type": "started",   "position": 1 },
    { "id": "...", "name": "Done",        "type": "completed", "position": 2 }
  ]
}

States are sorted by position.

Tool: linear_update_issue_state

Transition an issue to a different workflow state. The state_id must come from linear_get_workflow_states — do not invent or guess it.

Input:

ParameterTypeRequiredDescription
identifierstringyesIssue identifier like ENG-123.
state_idstringyesWorkflow state UUID from linear_get_workflow_states.

Output:

json
{
  "success": true,
  "identifier": "ENG-123",
  "state": { "id": "...", "name": "In Progress", "type": "started" }
}

Tool: linear_add_comment

Post a markdown comment to an issue.

Input:

ParameterTypeRequiredDescription
identifierstringyesIssue identifier like ENG-123.
bodystringyesMarkdown comment body. Capped at 10 000 characters; longer bodies are truncated client-side.

Output:

json
{
  "success": true,
  "comment": { "id": "...", "url": "https://linear.app/...", "created_at": "2026-05-20T..." }
}

© initializ, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 7 other files (scripts) in forge-skills/local/embedded/linear of initializ/forge.

  • SKILL.md
  • scripts/common.sh
  • scripts/linear-add-comment.sh
  • scripts/linear-get-issue.sh
  • scripts/linear-get-workflow-states.sh
  • scripts/linear-list-my-issues.sh
  • scripts/linear-search-issues.sh
  • scripts/linear-update-issue-state.sh

Open the folder on GitHubat commit 3c608d8

Compare with similar skills

Linear next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Linear compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Linear this skillinitializ/forge223—~1.9kAutomated safety check: PassApache-2.0
Orca Linear Ticket Workflowstablyai/orca87k1 repos~522Automated safety check: PassMIT
Review Triage Phaseprisma/orm48k—~995Automated safety check: PassApache-2.0
Commitdinerojs/dinero.js6.8k—~667Automated safety check: PassMIT
Draft Pull Request Creatorwordpress-mobile/WordPress-Android3.2k—~881Automated safety check: NotesGPL-2.0
Linear Tickets via Orcastablyai/orca87k—~558Automated safety check: PassMIT

Similar skills

  • Linear ticket work through Orca's CLI. Use when working from a linked Linear issue, finishing work with a PR/MR link and a completion comment, moving a ticket…

    87k GitHub starsUsed in 1 repo~522 tokens
    Productivity & AutomationAuto-check passed
  • Official

    Runs the triage step of the review-framework loop: reads fetched PR review state, builds `review-actions.json`, validates it and renders `review-actions.md`.

    48k GitHub stars~995 tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Commit

    dinerojs/dinero.js

    Create a git commit with optional automatic Linear issue linking.

    6.8k GitHub stars~667 tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Draft Pull Request Creator

    wordpress-mobile/WordPress-Android

    Commits and pushes current changes, writes a pull request title and body from the branch history and template, and opens a draft PR on GitHub after you approve it.

    3.2k GitHub stars~881 tokensUpdated today
    DevelopmentAuto-check: notes
  • Linear ticket work through Orca's CLI. Use when working from a linked Linear issue, finishing work with a PR/MR link and a completion comment, moving a ticket…

    87k GitHub stars~558 tokensUpdated today
    Productivity & AutomationAuto-check passed
  • Add Icon Mapping

    lobehub/lobe-icons

    Add or modify icon keyword mappings for providers, models, or agents in lobe-icons.

    2.6k GitHub stars~1.5k tokensUpdated yesterday
    MobileAuto-check: warnings

More from initializ/forge

All 15 skills in this repo
  • Code Plan

    initializ/forge

    Turn a task description and repository into a structured implementation plan (files to create, files to modify, tests to add, risks).

    223 GitHub stars~1.9k tokensUpdated 6 days ago
    Auto-check passed
  • Code Review

    initializ/forge

    AI-powered code review for diffs and individual files using LLM analysis

    223 GitHub stars~3k tokensUpdated 6 days ago
    Auto-check passed
  • Codegen HTML

    initializ/forge

    Scaffold and iterate on standalone Preact + HTM applications with zero build dependencies

    223 GitHub stars~1.5k tokensUpdated 6 days ago
    Auto-check passed
  • Code Agent

    initializ/forge

    General-purpose coding agent that reads, writes, and edits code, and searches codebases.

    223 GitHub stars~2.5k tokensUpdated 6 days ago
    Auto-check: warnings
  • Codegen React

    initializ/forge

    Scaffold and iterate on Vite + React applications. An agent skill from initializ/forge.

    223 GitHub stars~1.8k tokensUpdated 6 days ago
    Auto-check passed
  • K8s Cost Visibility

    initializ/forge

    Estimate Kubernetes infrastructure costs by querying cluster node, pod, PVC/PV, and LoadBalancer data, applying cloud pricing models, and producing cost attribution reports with storage and…

    223 GitHub stars~2.7k tokensUpdated 6 days ago
    Auto-check passed

Works with

Questions about Linear

What does Linear do?

Read Linear issues, transition state, and post comments. An agent skill from initializ/forge. Linear is an agent skill from initializ/forge. Read Linear issues, transition state, and post comments.

How do I install Linear in Claude Code?

Run `npx skills add initializ/forge --skill linear -a claude-code`. Or copy the skill folder (forge-skills/local/embedded/linear in initializ/forge) into .claude/skills/linear in your project. Claude Code loads it when a task matches its description.

How do I install Linear in Codex?

Run `npx skills add initializ/forge --skill linear -a codex`. Or copy the skill folder (forge-skills/local/embedded/linear in initializ/forge) into .agents/skills/linear in your project. Codex loads it when a task matches its description.

Can I use Linear in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add initializ/forge --skill linear -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/linear, .gemini/skills/linear, .github/skills/linear and .opencode/skills/linear in your project.

What does Linear need to run?

Going by SKILL.md and its folder, Linear needs a shell for the scripts in its folder and credentials named TEAM_KEY. Our summary lists: A Bash shell; A credential in LINEAR_API_KEY; A credential in TEAM_KEY.

Does Linear access the network?

SKILL.md names 1 domain. In commands or code: linear.app; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Linear safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Linear use?

Linear is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Linear use?

About 1.9k tokens (SKILL.md is roughly 7.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Linear?

Skills that share tags, products or a category with Linear: Orca Linear Ticket Workflow (stablyai/orca, 87k stars), Review Triage Phase (prisma/orm, 48k stars), Commit (dinerojs/dinero.js, 6.8k stars) and Draft Pull Request Creator (wordpress-mobile/WordPress-Android, 3.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Linear?

initializ (a GitHub organization) maintains it in initializ/forge, which has 223 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 1, 2026.

Source: initializ/forge on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.