linear
by JoannisLinear skill for issue tracking and project coordination from the command line. Use it to list issues, check status, triage work, update states, and link day-to-day engineering output back to Linear with less guesswork.
This skill scores 78/100, which means it is a solid directory candidate for users who need a Linear CLI workflow for issue tracking and ticket management. The repository gives enough trigger guidance and command examples to justify installation, though users should expect some environment/setup assumptions and a narrower scope than a full workflow toolkit.
- Explicit trigger guidance in the frontmatter for Linear issues, ticket triage, status changes, and PR-to-issue linking.
- Concrete command examples for listing, viewing, and updating issues, which helps an agent act with less guesswork.
- Operational prerequisite is stated clearly: `LINEAR_ISSUE_SORT=priority` must be set, reducing hidden failure modes.
- Workflow coverage is narrower than ideal: the excerpt shows common commands, but few broader decision rules or edge-case instructions.
- No install command, support files, or references are provided, so adoption depends on the user already having the Linear CLI available.
Overview of linear skill
What the linear skill does
The linear skill helps an agent use Linear from the command line for issue tracking, triage, and lightweight project coordination. It is most useful when the task is not “write a nice prompt about Linear,” but “actually find, inspect, update, or close an issue in a predictable way.”
Best fit for issue-tracking workflows
Use the linear skill if you need Linear for Issue Tracking tasks such as listing tickets, checking status, triaging work, or linking day-to-day engineering output back to tracked issues. It fits developers, agents, and ops workflows where issue state matters more than UI navigation.
What makes it worth installing
This linear guide is practical when you want a repeatable CLI workflow, not a generic assistant answer. The main value is reducing ambiguity around issue states, team selection, and the required environment setup that can block commands from working.
How to Use linear skill
Install and verify the command
Install with npx skills add Joannis/claude-skills --skill linear, then confirm the CLI is available in your environment. The source notes that Linear is installed via Homebrew at /opt/homebrew/bin/linear, so path assumptions matter on Apple Silicon setups.
Set the required environment first
Before most commands will work, set LINEAR_ISSUE_SORT:
export LINEAR_ISSUE_SORT=priority
This is not optional in practice. If you skip it, the linear install may succeed but the usage will fail, which is the most common blocker to adoption.
Read the right files in the right order
Start with SKILL.md, because it contains the actual operational rules. Then inspect the rest of the repo only if needed. In this repository, there are no supporting rules/, resources/, or scripts/ folders, so the main install decision depends on the skill body itself rather than hidden helper assets.
Turn a rough goal into a usable prompt
For best linear usage, specify four things up front: team, action, state filter, and output intent. For example: “Use linear skill to list active issues for team WDY, filter to started and unstarted, and summarize blockers.” That is stronger than “check Linear,” because it gives the skill enough structure to choose the right command path.
linear skill FAQ
Is this linear skill only for developers?
No. It is for anyone who needs Linear for Issue Tracking, but it is especially helpful for developers and technical agents who already work in terminal-based workflows. If you just need occasional status checks, the CLI may be more tool than you need.
What is the main boundary of the skill?
The linear skill is about CLI-driven issue operations, not full project management strategy or rich workspace administration. If your task depends on UI-only actions, complex permissions, or custom org-specific workflows, expect to supplement the skill with local conventions.
Do I need special context before using it?
Yes. You need the correct team name or issue key, plus the required LINEAR_ISSUE_SORT setting. Without those inputs, the skill can only guess, and guesswork is exactly what slows issue-tracking workflows down.
Is a plain prompt enough instead of a skill?
Sometimes, but a dedicated linear skill is better when you want repeatable commands and fewer missed assumptions. A generic prompt can ask for a ticket update; the skill is more valuable when you need the same action done consistently across multiple issues or teams.
How to Improve linear skill
Give the skill the exact issue context
The best way to improve linear skill output is to include the team, issue key, and desired state transition. “Update WDY-123 to started and show the next command if the update fails” is much better than “move the ticket.” Specificity reduces back-and-forth and makes the CLI path deterministic.
State the workflow goal, not just the command
If you only ask for a command, you may get a narrow answer. If you ask for a workflow—such as “triage new issues, list active items, then close completed work”—the skill can choose better defaults and avoid suggesting irrelevant states or filters.
Watch for the common failure modes
The biggest failure modes are missing LINEAR_ISSUE_SORT, using the wrong team identifier, and confusing Linear state labels like unstarted, started, and completed. If results look off, check those inputs before changing the prompt.
Iterate using a real example
When refining the linear guide for your team, reuse one real issue and one real team name as the test case. If the first pass cannot list, view, and update that issue cleanly, tighten the prompt with the exact command goal, expected state, and any pager or output constraints.