Agent skill

Linear CLI

A skill your agent uses when the user wants to list, view, start, create, or update Linear issues from the terminal via schpet/linear-cli, including setup, auth, repo config, and safe read/write…

MITAuto-check passed

Install Linear CLI

skills CLI

$ npx skills add Peiiii/nextclaw --skill linear-cli -a claude-code

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

GitHub CLI

$ gh skill install Peiiii/nextclaw linear-cli --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/Peiiii/nextclaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/linear-cli .claude/skills/linear-cli && 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/

Paste into Claude Code

Install the "linear-cli" agent skill from https://github.com/Peiiii/nextclaw/tree/master/skills/linear-cli into .claude/skills/linear-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linear-cli", 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

$skill-installer install https://github.com/Peiiii/nextclaw/tree/master/skills/linear-cli

Type 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.

skills CLI

$ npx skills add Peiiii/nextclaw --skill linear-cli -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Peiiii/nextclaw linear-cli --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Peiiii/nextclaw.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/linear-cli .agents/skills/linear-cli && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "linear-cli" agent skill from https://github.com/Peiiii/nextclaw/tree/master/skills/linear-cli into .agents/skills/linear-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linear-cli", 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.

skills CLI

$ npx skills add Peiiii/nextclaw --skill linear-cli -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Peiiii/nextclaw linear-cli --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Peiiii/nextclaw.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/linear-cli .cursor/skills/linear-cli && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "linear-cli" agent skill from https://github.com/Peiiii/nextclaw/tree/master/skills/linear-cli into .cursor/skills/linear-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linear-cli", 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

$ gemini skills install https://github.com/Peiiii/nextclaw.git --path skills/linear-cli

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Peiiii/nextclaw --skill linear-cli -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Peiiii/nextclaw linear-cli --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Peiiii/nextclaw.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/linear-cli .gemini/skills/linear-cli && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "linear-cli" agent skill from https://github.com/Peiiii/nextclaw/tree/master/skills/linear-cli into .gemini/skills/linear-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linear-cli", 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.

GitHub CLI

$ gh skill install Peiiii/nextclaw linear-cli

Installs 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).

skills CLI

$ npx skills add Peiiii/nextclaw --skill linear-cli -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Peiiii/nextclaw.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/linear-cli .github/skills/linear-cli && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "linear-cli" agent skill from https://github.com/Peiiii/nextclaw/tree/master/skills/linear-cli into .github/skills/linear-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linear-cli", 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.

skills CLI

$ npx skills add Peiiii/nextclaw --skill linear-cli -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Peiiii/nextclaw linear-cli --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Peiiii/nextclaw.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/linear-cli .opencode/skills/linear-cli && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "linear-cli" agent skill from https://github.com/Peiiii/nextclaw/tree/master/skills/linear-cli into .opencode/skills/linear-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linear-cli", 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.

Facts

Skill name: linear-cli
GitHub stars: 260
Token cost: ~1.6k tokens
SKILL.md length: 814 words
Files: 2
Skills in repo: 70
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

A skill your agent uses when the user wants to list, view, start, create, or update Linear issues from the terminal via schpet/linear-cli, including setup, auth, repo config, and safe read/write…

Works in 6 steps: Classify the task → Check whether the CLI exists → Confirm CLI version → …
The user wants to list
SKILL.md covers Overview, What This Skill Covers, What This Skill Does Not Cover and First-Use Workflow, plus 3 more sections
Calls brew, npx and pnpm

What it does

Linear CLI is an agent skill from Peiiii/nextclaw. Use when the user wants to list, view, start, create, or update Linear issues from the terminal via schpet/linear-cli, including setup, auth, repo config, and safe read/write boundaries.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `marketplace.json`).

It works with Linear. The repository describes itself as: A human-centered long-term AI partner—not a task-centered assistant. The licence is MIT.

When your agent uses it

The user wants to list
Update Linear issues from the terminal via schpet/linear-cli
Including setup
Safe read/write boundaries

Example prompts

“/linear-cli”

Requirements

Node.js

Workflow steps

6 steps, taken from the step headings in SKILL.md.

Classify the task
Check whether the CLI exists
Confirm CLI version
Authentication and configuration
Readiness check
Respect “current issue” rules

What it can do on your machine

Read from SKILL.md and the folder at commit 973722e. 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
Shell commands in SKILL.md call:
- brew
- npx
- pnpm
- bunx
- deno
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
- github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Linear CLI loads about 1.6k tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 814 words of instructions outside code blocks.

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

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from Peiiii/nextclaw at commit 973722e, republished under its MIT licence (© Peiiii). 814 words, ~1,557 tokens.

Download SKILL.mdSave it as .claude/skills/linear-cli/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: linear-cli
description: Use when the user wants to list, view, start, create, or update Linear issues from the terminal via schpet/linear-cli, including setup, auth, repo config, and safe read/write boundaries.

Linear CLI (schpet/linear-cli)

Overview

Use this skill to help the user work through a local linear installation from inside NextClaw.

This skill is intentionally decoupled:

The skill owns explanation, onboarding, readiness checks, workflow choice, and risk handling.
The linear CLI owns actual execution against Linear’s API and the user’s git or Jujutsu workspace.

From the user’s point of view, the experience should feel complete:

install the CLI if needed,
ensure authentication and project configuration,
verify readiness with observable commands,
then run the real task.

Do not pretend the environment is ready when it is not.

What This Skill Covers

Issue workflows: list, view, start, create, update, delete, comments, PR helpers (when gh is available as documented upstream).
Team, project, milestone, and document commands exposed by the installed CLI.
Git branch–based “current issue” semantics and Jujutsu Linear-issue trailers when the user uses jj.
First-use setup: API key, linear auth login, and linear config in the target repository.
Readiness checks and bounded troubleshooting.

What This Skill Does Not Cover

Inventing flags or subcommands that do not appear in linear --help or the installed CLI help for the relevant subcommand.
Claiming Linear workspace permissions or plan limits the user does not have.
Silently bypassing missing authentication or broken configuration.
Silently triggering destructive or write actions without explicit user confirmation.
Treating third-party CLI behavior as native NextClaw behavior.

First-Use Workflow

When the user asks for a linear-powered task, follow this order.

1. Classify the task

Classify the task into one of these:

read-only (view, list, print id/url/title),
write (create/update/delete issues, start work, comments, milestones, documents),
VCS-assisted (branch creation, issue binding).

If the task does not fit what the CLI supports, say so clearly.

2. Check whether the CLI exists

Run:

bash

command -v linear

If missing, explain that the CLI must be installed locally first. Prefer one of these install paths and stay consistent with the user’s platform and package preferences:

Homebrew: brew install schpet/tap/linear (see upstream tap name in the repository).
npm (project or global): install @schpet/linear-cli and invoke via npx linear / pnpm exec linear / bunx linear as appropriate.
Deno: follow upstream deno install instructions from the README.

After installation, continue with readiness checks instead of jumping straight into the user task.

3. Confirm CLI version

Run:

bash

linear --version

If this fails, treat the install as broken and fix that before API-backed tasks.

4. Authentication and configuration

The CLI needs a Linear API key and login state. The user creates a key under Linear account security settings (see upstream docs).

Guide the user through:

bash

linear auth login

For repository-specific defaults (team, workspace slug, VCS mode), run from the target repo:

bash

linear config

Configuration is resolved from ./linear.toml, ./.linear.toml, repo root, .config/linear.toml, and platform-appropriate user config paths as documented upstream. Environment variables override file values when both apply.

5. Readiness check

Prefer a lightweight read that hits the API after auth, for example:

bash

linear team list

If this fails with authentication or permission errors, do not proceed to the user’s real task. Diagnose auth, workspace, or token scope first.

Show full SKILL.md (323 more words)Show less

6. Respect “current issue” rules

The CLI derives the current issue from:

git: issue id embedded in the branch name (for example ENG-123-my-feature),
jj: Linear-issue trailer in commit metadata.

If the user expects “current issue” behavior but the branch or trailers do not match, explain the mismatch before running issue-scoped commands.

Safe Execution Rules

Prefer read-only commands before write commands.
For creates, updates, deletes, starts, comments, or other writes, ask for explicit confirmation first unless the user already gave a clear, scoped instruction for that write.
Do not assume gh or a Git host CLI is installed; if the user wants linear issue pr, verify gh availability or follow upstream behavior transparently.
If the user is in the wrong directory for linear config or issue context, say so and ask to switch to the intended repository root.

Troubleshooting

`linear` not found

Explain that the CLI is not installed or not on PATH.
Guide installation using one of the supported methods, then re-check with command -v linear.

Auth or API errors on read commands

Confirm linear auth login completed successfully.
Confirm API key is valid and not revoked.
Confirm workspace and team_id / defaults match the user’s intent (linear config and env vars).

Wrong issue or empty “current issue”

For git, verify the branch name contains the expected Linear issue id.
For Jujutsu, verify Linear-issue trailers on the relevant commits.
Offer linear issue view <id> when current-issue detection is unreliable.

Platform differences

Treat path and config locations as different on Windows vs Unix; follow upstream config search order instead of assuming POSIX-only paths.

Success Criteria

The skill is working correctly when:

the user understands that execution is performed by the local linear CLI against Linear,
missing CLI, auth, or config is identified before task execution,
a lightweight API read succeeds before heavier workflows when appropriate,
write operations wait for explicit confirmation when required,
and the real task runs only after the environment is truly ready.

Files

SKILL.md and 1 other file in skills/linear-cli of Peiiii/nextclaw.

SKILL.md
marketplace.json

Open the folder on GitHubat commit 973722e

Compare with similar skills

Linear CLI 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 CLI compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Linear CLI this skillPeiiii/nextclaw	260	—	~1.6k	Automated safety check: Pass	MIT	today
Orca Linear Ticket Workflowstablyai/orca	87k	1 repos	~522	Automated safety check: Pass	MIT	today
Review Triage Phaseprisma/orm	48k	—	~995	Automated safety check: Pass	Apache-2.0	today
Commitdinerojs/dinero.js	6.8k	—	~667	Automated safety check: Pass	MIT	2 days ago
Draft Pull Request Creatorwordpress-mobile/WordPress-Android	3.2k	—	~881	Automated safety check: Notes	GPL-2.0	today
Linear Tickets via Orcastablyai/orca	87k	—	~558	Automated safety check: Pass	MIT	today

Similar skills

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…
87k GitHub starsUsed in 1 repo~522 tokens
Productivity & AutomationAuto-check passed
Review Triage Phase
prisma/orm
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 today
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 Tickets via Orca
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…
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 today
MobileAuto-check: warnings

Questions about Linear CLI

What does Linear CLI do?

A skill your agent uses when the user wants to list, view, start, create, or update Linear issues from the terminal via schpet/linear-cli, including setup, auth, repo config, and safe read/write…. Linear CLI is an agent skill from Peiiii/nextclaw. Use when the user wants to list, view, start, create, or update Linear issues from the terminal via schpet/linear-cli, including setup, auth, repo config, and safe read/write boundaries.

When should I use Linear CLI?

Linear CLI fits situations like: the user wants to list; update Linear issues from the terminal via schpet/linear-cli; including setup; safe read/write boundaries.

How do I install Linear CLI in Claude Code?

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

How do I install Linear CLI in Codex?

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

Can I use Linear CLI 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 Peiiii/nextclaw --skill linear-cli -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-cli, .gemini/skills/linear-cli, .github/skills/linear-cli and .opencode/skills/linear-cli in your project.

What does Linear CLI need to run?

Going by SKILL.md and its folder, Linear CLI needs the command-line tools its instructions call (brew, npx, pnpm, bunx and deno). Our summary lists: Node.js.

Does Linear CLI access the network?

SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.

Is Linear CLI 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. Review the folder before installing.

What licence does Linear CLI use?

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

How many tokens does Linear CLI use?

About 1.6k tokens (SKILL.md is roughly 6.2k 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 CLI?

Skills that share tags, products or a category with Linear CLI: 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 CLI?

Peiiii (a GitHub user) maintains it in Peiiii/nextclaw, which has 260 GitHub stars. The repository holds 70 skills in this directory. The repository was last updated on October 7, 2026.

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

Install Linear CLI

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Linear CLI (schpet/linear-cli)

Overview

What This Skill Covers

What This Skill Does Not Cover

First-Use Workflow

1. Classify the task

2. Check whether the CLI exists

3. Confirm CLI version

4. Authentication and configuration

5. Readiness check

6. Respect “current issue” rules

Safe Execution Rules

Troubleshooting

linear not found

Auth or API errors on read commands

Wrong issue or empty “current issue”

Platform differences

Success Criteria

Files

Compare with similar skills

Similar skills

More from Peiiii/nextclaw

Related

Questions about Linear CLI

`linear` not found