Orca Linear Ticket Workflow
stablyai/orca
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…
Read Linear issues, transition state, and post comments. An agent skill from initializ/forge.
$ npx skills add initializ/forge --skill linear -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install initializ/forge linear --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "linear" agent skill from https://github.com/initializ/forge/tree/main/forge-skills/local/embedded/linear into .claude/skills/linear/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linear", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/initializ/forge/tree/main/forge-skills/local/embedded/linearType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add initializ/forge --skill linear -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install initializ/forge linear --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/initializ/forge.git skills-src && mkdir -p .agents/skills && cp -r skills-src/forge-skills/local/embedded/linear .agents/skills/linear && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "linear" agent skill from https://github.com/initializ/forge/tree/main/forge-skills/local/embedded/linear into .agents/skills/linear/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linear", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add initializ/forge --skill linear -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install initializ/forge linear --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/initializ/forge.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/forge-skills/local/embedded/linear .cursor/skills/linear && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "linear" agent skill from https://github.com/initializ/forge/tree/main/forge-skills/local/embedded/linear into .cursor/skills/linear/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linear", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/initializ/forge.git --path forge-skills/local/embedded/linear--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add initializ/forge --skill linear -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install initializ/forge linear --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/initializ/forge.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/forge-skills/local/embedded/linear .gemini/skills/linear && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "linear" agent skill from https://github.com/initializ/forge/tree/main/forge-skills/local/embedded/linear into .gemini/skills/linear/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linear", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install initializ/forge linearInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add initializ/forge --skill linear -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/initializ/forge.git skills-src && mkdir -p .github/skills && cp -r skills-src/forge-skills/local/embedded/linear .github/skills/linear && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "linear" agent skill from https://github.com/initializ/forge/tree/main/forge-skills/local/embedded/linear into .github/skills/linear/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linear", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add initializ/forge --skill linear -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install initializ/forge linear --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/initializ/forge.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/forge-skills/local/embedded/linear .opencode/skills/linear && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "linear" agent skill from https://github.com/initializ/forge/tree/main/forge-skills/local/embedded/linear into .opencode/skills/linear/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linear", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
linearRead 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. 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.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 3c608d8. It shows what the files ask for, not the result of running them.
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.
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.
Hosts in commands or code, which the agent is likely to contact:
linear.appFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
TEAM_KEYFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from initializ/forge at commit 3c608d8, republished under its Apache-2.0 licence (© initializ). 754 words, ~1,908 tokens.
.claude/skills/linear/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.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.
"Todo" or "In Progress" (state types unstarted, started) unless they specify otherwise.Fetch a Linear issue by its human identifier.
Input:
| Parameter | Type | Required | Description |
|---|---|---|---|
| identifier | string | yes | Issue identifier like ENG-123 |
Output:
{
"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/..."
}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:
| Parameter | Type | Required | Description |
|---|---|---|---|
| team_id | string | no | Linear team UUID or team key like ENG. Auto-detects which form. Defaults to $LINEAR_DEFAULT_TEAM_ID when set. |
| state | string | no | Workflow state type (unstarted, started, completed, canceled, triage, backlog). |
| assignee_email | string | no | Filter by assignee email. |
| label | string | no | Filter by label name. |
| query | string | no | Free-text search over title and description. |
| limit | integer | no | Max results (default 20, capped at 100). |
Examples — call the tool directly, do not ask the user for an ID:
| User says | Tool 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:
{
"count": 3,
"issues": [
{ "identifier": "ENG-1", "title": "...", "state": "Todo", "assignee_email": "...", "url": "..." }
]
}List issues assigned to the API key's owner (viewer).
Input:
| Parameter | Type | Required | Description |
|---|---|---|---|
| state | string | no | Comma-separated state types. Default: "started,unstarted" ("In Progress" / "Todo"). |
| limit | integer | no | Max results (default 20, capped at 100). |
Output: same shape as linear_search_issues.
Enumerate a team's workflow states. Required before linear_update_issue_state.
Input:
| Parameter | Type | Required | Description |
|---|---|---|---|
| team_id | string | yes | Linear team UUID (from linear_get_issue's team.id). |
Output:
{
"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.
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:
| Parameter | Type | Required | Description |
|---|---|---|---|
| identifier | string | yes | Issue identifier like ENG-123. |
| state_id | string | yes | Workflow state UUID from linear_get_workflow_states. |
Output:
{
"success": true,
"identifier": "ENG-123",
"state": { "id": "...", "name": "In Progress", "type": "started" }
}Post a markdown comment to an issue.
Input:
| Parameter | Type | Required | Description |
|---|---|---|---|
| identifier | string | yes | Issue identifier like ENG-123. |
| body | string | yes | Markdown comment body. Capped at 10 000 characters; longer bodies are truncated client-side. |
Output:
{
"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
SKILL.md and 7 other files (scripts) in forge-skills/local/embedded/linear of initializ/forge.
Open the folder on GitHubat commit 3c608d8
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Linear this skillinitializ/forge | 223 | — | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Orca Linear Ticket Workflowstablyai/orca | 87k | 1 repos | ~522 | Automated safety check: Pass | MIT | |
| Review Triage Phaseprisma/orm | 48k | — | ~995 | Automated safety check: Pass | Apache-2.0 | |
| Commitdinerojs/dinero.js | 6.8k | — | ~667 | Automated safety check: Pass | MIT | |
| Draft Pull Request Creatorwordpress-mobile/WordPress-Android | 3.2k | — | ~881 | Automated safety check: Notes | GPL-2.0 | |
| Linear Tickets via Orcastablyai/orca | 87k | — | ~558 | Automated safety check: Pass | MIT |
stablyai/orca
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…
prisma/orm
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`.
dinerojs/dinero.js
Create a git commit with optional automatic Linear issue linking.
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.
stablyai/orca
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…
lobehub/lobe-icons
Add or modify icon keyword mappings for providers, models, or agents in lobe-icons.
initializ/forge
Turn a task description and repository into a structured implementation plan (files to create, files to modify, tests to add, risks).
initializ/forge
AI-powered code review for diffs and individual files using LLM analysis
initializ/forge
Scaffold and iterate on standalone Preact + HTM applications with zero build dependencies
initializ/forge
General-purpose coding agent that reads, writes, and edits code, and searches codebases.
initializ/forge
Scaffold and iterate on Vite + React applications. An agent skill from initializ/forge.
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…
Works with
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.