agentleFS
Sign inStart free
InjectiveLabsInjectiveLabs/agent-skills/skills/linear-cli/SKILL.md

linear-cli

Skill6 starsChanged 4 months agoApache-2.0View on GitHub

Enables management of Linear issues, teams, projects, comments, or configuration via the `linear` CLI

  • Reads credentials
  • Installs packages

7 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. 0 are common, 3 are distinctive, and 12 are very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 12

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the linear CLI to manage Linear issues, teams, and projects from the terminal.

    line 14
  2. Very specific:

    Verify the CLI is available: linear --version.

    line 18
  3. Very specific:

    Use linear issue list, linear issue start, and linear issue view for day-to-day workflows.

    line 21
  4. Distinctive:

    Prefer NPM-distributed version from Injective Labs:

    line 25
  5. Very specific:

    Create a personal API key in Linear account settings: https://linear.app/settings/account/security.

    line 39
  6. Very specific:

    If linear auth login exists, run it to authenticate.

    line 40
  7. Very specific:

    Run linear config inside the repo to generate .linear.toml interactively.

    line 41
  8. Very specific:

    Use linear auth token or linear auth whoami to verify authentication.

    line 42
  9. Very specific:

    Start work on an issue: linear issue start ABC-123 (use -b to specify a branch).

    line 48
  10. Very specific:

    Create an issue: linear issue create --title "..." --team TEAM (add --project, --label, --priority, or --estimate as needed).

    line 50
  11. Very specific:

    Update an issue: linear issue update ABC-123 --state STATE --assignee USER.

    line 51
  12. Very specific:

    Add a comment: linear issue comment add ABC-123 --body "...".

    line 52
  13. Distinctive:

    Instead of guessing flag and command arguments, check the reference.

    line 57
  14. Very specific:

    When some command feels missing try npx @injectivelabs/linear-cli@latest completions bash to refresh the completions.

    line 61
  15. Distinctive:

    Avoid raw schema dumps unless needed.

    line 66

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Linear CLI, Skill Guide

Overview

Use the linear CLI to manage Linear issues, teams, and projects from the terminal. Prefer CLI flows over raw GraphQL when a command exists.

Quick Start

  1. Verify the CLI is available: linear --version.
  2. Install the CLI if needed (see Install Linear CLI).
  3. Configure the API key and repo settings (see Configure API Key).
  4. Use linear issue list, linear issue start, and linear issue view for day-to-day workflows.

Install Linear CLI

Prefer NPM-distributed version from Injective Labs:

npm i -g @injectivelabs/linear-cli

One-time commands can be run via npx @injectivelabs/linear-cli.

If NPM is not available

Fetch binary for current platform using https://github.com/InjectiveLabs/linear-cli/releases/latest install it so it available in $PATH.

Configure API Key

  • Create a personal API key in Linear account settings: https://linear.app/settings/account/security.
  • If linear auth login exists, run it to authenticate. Otherwise export the key for the CLI session: export LINEAR_API_KEY=....
  • Run linear config inside the repo to generate .linear.toml interactively.
  • Use linear auth token or linear auth whoami to verify authentication.
  • Note: API key creation requires member access (not guest).

Common Workflows

  • List issues: linear issue list with filters like --state, --assignee, --team, or --limit.
  • Start work on an issue: linear issue start ABC-123 (use -b to specify a branch).
  • View an issue: linear issue view ABC-123 (use -w for web or -a for app).
  • Create an issue: linear issue create --title "..." --team TEAM (add --project, --label, --priority, or --estimate as needed).
  • Update an issue: linear issue update ABC-123 --state STATE --assignee USER.
  • Add a comment: linear issue comment add ABC-123 --body "...".
  • Browse teams/projects: linear team list, linear project list, then linear project view.

Command Reference

Instead of guessing flag and command arguments, check the reference.

See references/commands.md for the full command and flag list extracted from linear completions bash.

When some command feels missing try npx @injectivelabs/linear-cli@latest completions bash to refresh the completions.

Safety

  • Confirm destructive actions explicitly before running linear issue delete.
  • Avoid raw schema dumps unless needed; prefer regular commands to inspect data.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free