Name: Linear
Author: MaTriXy

据 AlphaMoat 统计,截至 2026-09,Linear 累计下载 4,365 次、获 7 个星标,在全部 5,078 个 AI 技能中排名第 2,241 位,在「商业运营」分类(297 个)中排名第 124 位。

累计安装

143

累计下载

4,365

星标

全站排名

#2,241

全站前 45% · 「商业运营」前 42%

平台	累计安装	累计下载	星标	评论
ClawHub ↗	143	4,331	6	-
SkillHub ↗	140	4,365	7	—

各平台的计数口径不同,统计时间不一致。

这个技能是做什么的

操作前应先读取当前团队、项目和事项状态，再按明确范围执行变更。文档列出的 CLI 能力包括项目与团队、issue、评论、状态和标签；发布资料指出文档声称支持的部分资源可能未由当前 CLI 实现，使用前需确认具体命令覆盖范围。API key 可读取并修改工作项；应使用最小权限密钥，避免把密钥写入评论，并对批量变更先审阅分组和目标。需要 Node.js、npm 和 LINEAR_API_KEY。

资料发布于 2026-10-29

可以用来做什么

查看 Linear 项目、团队、事项和工作流状态
在明确范围内创建或更新事项、项目及评论
整理标签、状态和后续跟进任务

什么时候用

已明确目标团队、项目和变更范围时
已读取当前状态且能核实目标 ID 时
使用最小权限 API key 并可审核拟议变更时

示例提示词

以下是根据技能文档生成的示例,不代表实际运行结果。

先读取指定 Linear 团队和项目的当前事项，再提出一份范围狭窄的更新计划；不要执行写入或把密钥放入评论。

月度数据趋势

累计下载4,365

星标7

2026-09 起统计方法调整:同名技能按作者分别统计,并覆盖全部技能。图中虚线为调整前的月份,与之后的数据不直接比较,也不计算跨越调整的增长。

月份	累计下载	环比	星标
2026-09	4,365	—	7
2026-08	4,207	+5.0%	7
2026-07	4,005	+7.7%	7
2026-06	3,720	+4.3%	6
2026-05	3,568	—	6
2026-03	3,124	—	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.