Name: Linear
Author: MaTriXy

據 AlphaMoat 統計,截至 2026-09,Linear 累計下載 4,365 次、獲 7 個星標,在全部 5,078 個 AI 技能中排名第 2,241 位,在「商業營運」分類(297 個)中排名第 124 位。

累計安裝

143

累計下載

4365

星標

全站排名

#2,241

全站前 45% · 「商業營運」前 42%

平台	累計安裝	累計下載	星標	評論
ClawHub ↗	143	4331	6	-
SkillHub ↗	140	4365	7	—

各平台的計數口徑不同,統計時間不一致。

這個技能是做什麼的

操作前應先讀取當前團隊、專案和事項狀態，再按明確範圍執行變更。文件列出的 CLI 能力包括專案與團隊、issue、評論、狀態和標籤；釋出資料指出文件聲稱支援的部分資源可能未由當前 CLI 實現，使用前需確認具體命令覆蓋範圍。API key 可讀取並修改工作項；應使用最小許可權金鑰，避免把金鑰寫入評論，並對批次變更先審閱分組和目標。需要 Node.js、npm 和 LINEAR_API_KEY。

資料釋出於 2026-10-29

可以用來做什麼

檢視 Linear 專案、團隊、事項和工作流狀態
在明確範圍內建立或更新事項、專案及評論
整理標籤、狀態和後續跟進任務

什麼時候用

已明確目標團隊、專案和變更範圍時
已讀取當前狀態且能核實目標 ID 時
使用最小許可權 API key 並可稽核擬議變更時

示例提示詞

以下是根據技能文件生成的示例,不代表實際執行結果。

先讀取指定 Linear 團隊和專案的當前事項，再提出一份範圍狹窄的更新計劃；不要執行寫入或把金鑰放入評論。

月度資料趨勢

累計下載4365

星標7

2026-09 起統計方法調整:同名技能按作者分別統計,並覆蓋全部技能。圖中虛線為調整前的月份,與之後的資料不直接比較,也不計算跨越調整的增長。

月份	累計下載	環比	星標
2026-09	4365	—	7
2026-08	4207	+5.0%	7
2026-07	4005	+7.7%	7
2026-06	3720	+4.3%	6
2026-05	3568	—	6
2026-03	3124	—	6

SKILL.md 原文

以下是作者釋出的原始檔案,按純文字顯示,本站未做修改或稽核;其中的連結不可點選,命令請核實後再執行。抓取於 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`.

展開全部(共 91 行)

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