Name: Linear
Author: MaTriXy

According to AlphaMoat, as of 2026-09, Linear has 4,365 downloads and 7 stars — ranked #2,241 of 5,078 AI skills overall, and #124 of 297 in Business Ops.

Installs

143

Downloads

4.4K

Stars

Overall Rank

#2,241

Top 45% overall · Top 42% in Business Ops

Platform	Installs	Downloads	Stars	Comments
ClawHub ↗	143	4.3K	6	-
SkillHub ↗	140	4.4K	7	—

Platforms count differently and update at different times.

What this skill does

Read current team, project, and issue state before applying changes within a clearly defined scope. The documented CLI covers teams and projects, issues, comments, states, and labels; the release evidence warns that some claimed resource types may not be implemented by the current CLI, so confirm command coverage first. The API key can read and mutate work items; use least privilege, keep it out of comments, and review targets and grouping before bulk changes. Requires Node.js, npm and LINEAR_API_KEY.

Profile published 2026-10-29

What you can do with it

Inspect Linear projects, teams, issues, and workflow state
Create or update issues, projects, and comments within a defined scope
Organize labels, states, and follow-up work

When to use it

When the target team, project, and change scope are clear
When current state has been read and target IDs can be verified
When least-privilege API credentials are used and proposed changes can be reviewed

Example prompts

Generated from the skill’s documentation as examples; not results of actual runs.

Read current issues for the specified Linear team and project, then propose a narrowly scoped update plan. Do not perform writes or put credentials in comments.

Monthly Trend

Downloads4.4K

Stars7

The counting method changed in 2026-09: skills with the same name are now counted separately by author, and the full catalog is covered. Dashed lines show months before the change; they are not compared with later months, and no growth is computed across the change.

Month	Downloads	MoM	Stars
2026-09	4.4K	—	7
2026-08	4.2K	+5.0%	7
2026-07	4.0K	+7.7%	7
2026-06	3.7K	+4.3%	6
2026-05	3.6K	—	6
2026-03	3.1K	—	6

SKILL.md (original)

The author’s original file, shown as plain text without edits or review by AlphaMoat. Links are not clickable; check commands before running them. Fetched 2026-10-23.

3.6 KB · ClawHub v1.0.0

---
name: linear
description: Manage Linear projects, issues, and tasks via the bundled Node CLI and the official Linear API. Use when you need to read, create, update, or organize Linear issues, projects, teams, milestones, comments, cycles, labels, and documents.
metadata: {"gracebot":{"always":false,"emoji":"📐","homepage":"https://github.com/MaTriXy/linear-skill","requires":{"bins":["node","npm"],"env":["LINEAR_API_KEY"]},"primaryEnv":"LINEAR_API_KEY","install":[{"id":"node-brew","kind":"brew","formula":"node","bins":["node","npm"],"label":"Install Node.js (brew)"}]},"clawdbot":{"always":false,"emoji":"📐","homepage":"https://github.com/MaTriXy/linear-skill","requires":{"bins":["node","npm"],"env":["LINEAR_API_KEY"]},"primaryEnv":"LINEAR_API_KEY","install":[{"id":"node-brew","kind":"brew","formula":"node","bins":["node","npm"],"label":"Install Node.js (brew)"}]}}
---

# Linear Workflow Management

Manage Linear issues and projects through the bundled CLI at `{baseDir}/scripts/linear-cli.js`.

Show all (91 lines)

## Scope and Runtime Model

- This skill runs `node {baseDir}/scripts/linear-cli.js ...`.
- The CLI uses the official `@linear/sdk`.
- Authentication is `LINEAR_API_KEY` from the local environment.
- Expected API destination is Linear GraphQL (`https://api.linear.app/graphql`) through the official SDK.

## Prerequisites

1. Node.js and npm are installed.
2. Install script dependencies once:
   - `cd {baseDir}/scripts && npm install`
3. Set your API key:
   - `export LINEAR_API_KEY="lin_api_..."`

If dependencies or `LINEAR_API_KEY` are missing, stop and complete setup before issue/project operations.

## Authentication and Credentials

- Required credential: `LINEAR_API_KEY`.
- Get it from `https://linear.app/settings/api`.
- Use least-privilege access and a dedicated token for automation.

## Required Workflow

1. Clarify intent and scope:
   - Team/project, labels, cycle, assignee, due date, priority.
2. Read current state first:
   - List/get issues, projects, statuses, labels, users, cycles.
3. Apply mutations second:
   - Create/update issues, comments, projects, milestones, labels.
4. Summarize exactly what changed:
   - Mention IDs, states, assignees, blockers, and follow-up actions.

## Command Coverage

- Teams and projects:
  `teams`, `projects`, `createProject`
- Issues:
  `issues`, `issue`, `createIssue`, `updateIssue`
- Comments:
  `createComment`
- States and labels:
  `states`, `labels`
- User:
  `user`

## Quick Examples

```bash
node {baseDir}/scripts/linear-cli.js teams
node {baseDir}/scripts/linear-cli.js projects
node {baseDir}/scripts/linear-cli.js issues
node {baseDir}/scripts/linear-cli.js issue ENG-123
node {baseDir}/scripts/linear-cli.js createIssue "Title" "Description" "team-id" '{"priority":2}'
node {baseDir}/scripts/linear-cli.js updateIssue "issue-id" '{"stateId":"state-id"}'
```

## Practical Workflows

- Triage urgent bugs:
  list high-priority open issues, assign owners, move state to `In Progress`, add triage comments.
- Sprint planning:
  review cycle scope, create missing issues, set priorities and estimates, align assignees.
- Release prep:
  verify blockers, update project status, create milestone tasks, add rollout comments.
- Documentation cleanup:
  find stale docs/issues, open follow-up tasks, link related records.

## Safety and Operational Rules

- Never invent IDs; fetch and confirm before updates.
- Prefer narrow updates over broad bulk edits.
- For bulk edits, explain grouping logic before applying changes.
- Do not include secrets in issue comments or descriptions.
- Do not send data to endpoints outside Linear API scope for this skill.

## References

- `references/API.md` for priority values and workflow patterns.