技能库智客分类：其他 linear OpenClaw

Linear

查询和管理线性问题,项目,以及团队工作流程.

518 安装量 · 21 星标

官方网址：作者主页

技能介绍

先看中文介绍；官方 description 原文单独保留，不改写 SKILL.md。

做什么

查询和管理线性问题,项目,以及团队工作流程.

何时用

官方 description 未单独写出 Use when。按规范，代理会在用户任务与这段 description 的关键词匹配时激活本技能。

代理如何加载

按 Agent Skills 渐进披露：启动时只加载 name 与 description（约 100 token）；任务匹配后才读入整份 SKILL.md 正文；scripts/、references/、assets/ 仅在需要时再读。本文件正文结构：Linear、Setup、Optional: default team key used when a command needs a team、Quick Commands、My stuff、Browse。其中含规范建议的小节：分步指令。

文件分析

文件分析：除 SKILL.md 外，正文引用了 scripts/linear.sh，属于带资源的技能包，这些文件按需再读。

官方 description（原文）

Query and manage Linear issues, projects, and team workflows.

LinearSetupOptional: default team key used when a command needs a teamQuick CommandsMy stuffBrowseActionsOverviewCommon WorkflowsMorning StandupQuick Issue Creation (from chat)Triage Mode

来源与网址

市场来源：ClawHub

开源榜 Skill 分类

SKILL.md 与 Agent 调用

官方规范 ↗

name: linear
description: Query and manage Linear issues, projects, and team workflows.

发现技能客户端向 Agent 提供名称与描述目录。
匹配与调用用户指定或任务匹配后，载入 SKILL.md 指令。
按需加载按步骤读取参考文档、使用脚本与素材。

指令中引用的文件 · 1

scripts/linear.sh

以下路径提取自原文；文件是否齐全请以来源仓库中的完整目录为准。

具体调用语法与可用工具以目标 Agent 客户端为准。查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围，保留技能包的附属文件，安装后检查客户端能否发现该技能。

该技能引用了附属文件，请从来源获取完整目录；仅复制 SKILL.md 可能缺少依赖。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理，确认其中的目标目录与客户端匹配。

把 Agent Skill「linear」安装到我的项目：SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-71c66fb4f888862b-Linear.html
请存为 .cursor/skills/linear/SKILL.md 或 .claude/skills/linear/SKILL.md，frontmatter 的 name 与 description 保持原样，不要改写。
该技能还带 scripts/、references/、assets/ 等文件，请从 https://clawhub.ai/skills/linear 取完整目录，不要只建一个 SKILL.md。

当前没有明确的 GitHub 技能包地址，请按来源页面的安装器说明操作。

ClawHub ↗

SKILL.md 原文可复制，不会改动源文件

# Linear

Manage issues, check project status, and stay on top of your team's work.

## Setup

```bash
export LINEAR_API_KEY="your-api-key"
# Optional: default team key used when a command needs a team
export LINEAR_DEFAULT_TEAM="TEAM"
```

Discover team keys:

```bash
{baseDir}/scripts/linear.sh teams
```

If `LINEAR_DEFAULT_TEAM` is set, you can omit the team key in `team` and call:

```bash
{baseDir}/scripts/linear.sh create "Title" ["Description"]
```

## Quick Commands

```bash
# My stuff
{baseDir}/scripts/linear.sh my-issues          # Your assigned issues
{baseDir}/scripts/linear.sh my-todos           # Just your Todo items
{baseDir}/scripts/linear.sh urgent             # Urgent/High priority across team

# Browse
{baseDir}/scripts/linear.sh teams              # List available teams
{baseDir}/scripts/linear.sh team <TEAM_KEY>    # All issues for a team
{baseDir}/scripts/linear.sh project <name>     # Issues in a project
{baseDir}/scripts/linear.sh issue <TEAM-123>   # Get issue details
{baseDir}/scripts/linear.sh branch <TEAM-123>  # Get branch name for GitHub

# Actions
{baseDir}/scripts/linear.sh create <TEAM_KEY> "Title" ["Description"]
{baseDir}/scripts/linear.sh comment <TEAM-123> "Comment text"
{baseDir}/scripts/linear.sh status <TEAM-123> <todo|progress|review|done|blocked>
{baseDir}/scripts/linear.sh assign <TEAM-123> <userName>
{baseDir}/scripts/linear.sh priority <TEAM-123> <urgent|high|medium|low|none>

# Overview
{baseDir}/scripts/linear.sh standup            # Daily standup summary
{baseDir}/scripts/linear.sh projects           # All projects with progress
```

## Common Workflows

### Morning Standup
```bash
{baseDir}/scripts/linear.sh standup
```
Shows: your todos, blocked items across team, recently completed, what's in review.

### Quick Issue Creation (from chat)
```bash
{baseDir}/scripts/linear.sh create TEAM "Fix auth timeout bug" "Users getting logged out after 5 min"
```

### Triage Mode
```bash
{baseDir}/scripts/linear.sh urgent    # See what needs attention
```

## Git Workflow (Linear ↔ GitHub Integration)

**Always use Linear-derived branch names** to enable automatic issue status tracking.

### Getting the Branch Name
```bash
{baseDir}/scripts/linear.sh branch TEAM-212
# Returns: dev/team-212-fix-auth-timeout-bug
```

### Creating a Worktree for an Issue
```bash
# 1. Get the branch name from Linear
BRANCH=$({baseDir}/scripts/linear.sh branch TEAM-212)

# 2. Pull fresh main first (main should ALWAYS match origin)
cd /path/to/repo
git checkout main && git pull origin main

# 3. Create worktree with that branch (branching from fresh origin/main)
git worktree add .worktrees/team-212 -b "$BRANCH" origin/main
cd .worktrees/team-212

# 4. Do your work, commit, push
git push -u origin "$BRANCH"
```

**⚠️ Never modify files on main.** All changes happen in worktrees only.

### Why This Matters
- Linear's GitHub integration tracks PRs by branch name pattern
- When you create a PR from a Linear branch, the issue **automatically moves to "In Review"**
- When the PR merges, the issue **automatically moves to "Done"**
- Manual branch names break this automation
- Keeping main clean = no accidental pushes, easy worktree cleanup

### Quick Reference
```bash
# Full workflow example
ISSUE="TEAM-212"
BRANCH=$({baseDir}/scripts/linear.sh branch $ISSUE)

# Always start from fresh main
cd ~/workspace/your-repo
git checkout main && git pull origin main

# Create worktree (inside .worktrees/)
git worktree add .worktrees/${ISSUE,,} -b "$BRANCH" origin/main
cd .worktrees/${ISSUE,,}

# ... make changes ...
git add -A && git commit -m "fix: implement $ISSUE"
git push -u origin "$BRANCH"
gh pr create --title "$ISSUE: <title>" --body "Closes $ISSUE"
```

## Priority Levels

| Level | Value | Use for |
|-------|-------|---------|
| urgent | 1 | Production issues, blockers |
| high | 2 | This week, important |
| medium | 3 | This sprint/cycle |
| low | 4 | Nice to have |
| none | 0 | Backlog, someday |

## Teams (cached)

Team keys and IDs are discovered via the API and cached locally after the first lookup.
Use `linear.sh teams` to refresh and list available teams.

## Notes

- Uses GraphQL API (api.linear.app/graphql)
- Requires `LINEAR_API_KEY` env var
- Issue identifiers are like `TEAM-123`

## Attribution

Inspired by [schpet/linear-cli](https://github.com/schpet/linear-cli) by Peter Schilling (ISC License).
This is an independent bash implementation for Clawdbot integration.

阅读排版

--- name: linear description: Query and manage Linear issues, projects, and team workflows. homepage: https://linear.app metadata: {"clawdis":{"emoji":"📊","requires":{"env":["LINEAR_API_KEY"]}}} --- # Linear Manage issues, check project status, and stay on top of your team's work. ## Setup ```bash export LINEAR_API_KEY="your-api-key" # Optional: default team key used when a command needs a team export LINEAR_DEFAULT_TEAM="TEAM" ``` Discover team keys: ```bash {baseDir}/scripts/linear.sh teams ``` If `LINEAR_DEFAULT_TEAM` is set, you can omit the team key in `team` and call: ```bash {baseDir}/scripts/linear.sh create "Title" ["Description"] ``` ## Quick Commands ```bash # My stuff {baseDir}/scripts/linear.sh my-issues # Your assigned issues {baseDir}/scripts/linear.sh my-todos # Just your Todo items {baseDir}/scripts/linear.sh urgent # Urgent/High priority across team # Browse {baseDir}/scripts/linear.sh teams # List available teams {baseDir}/scripts/linear.sh team # All issues for a team {baseDir}/scripts/linear.sh project # Issues in a project {baseDir}/scripts/linear.sh issue # Get issue details {baseDir}/scripts/linear.sh branch # Get branch name for GitHub # Actions {baseDir}/scripts/linear.sh create "Title" ["Description"] {baseDir}/scripts/linear.sh comment "Comment text" {baseDir}/scripts/linear.sh status {baseDir}/scripts/linear.sh assign {baseDir}/scripts/linear.sh priority # Overview {baseDir}/scripts/linear.sh standup # Daily standup summary {baseDir}/scripts/linear.sh projects # All projects with progress ``` ## Common Workflows ### Morning Standup ```bash {baseDir}/scripts/linear.sh standup ``` Shows: your todos, blocked items across team, recently completed, what's in review. ### Quick Issue Creation (from chat) ```bash {baseDir}/scripts/linear.sh create TEAM "Fix auth timeout bug" "Users getting logged out after 5 min" ``` ### Triage Mode ```bash {baseDir}/scripts/linear.sh urgent # See what needs attention ``` ## Git Workflow (Linear ↔ GitHub Integration) **Always use Linear-derived branch names** to enable automatic issue status tracking. ### Getting the Branch Name ```bash {baseDir}/scripts/linear.sh branch TEAM-212 # Returns: dev/team-212-fix-auth-timeout-bug ``` ### Creating a Worktree for an Issue ```bash # 1. Get the branch name from Linear BRANCH=$({baseDir}/scripts/linear.sh branch TEAM-212) # 2. Pull fresh main first (main should ALWAYS match origin) cd /path/to/repo git checkout main && git pull origin main # 3. Create worktree with that branch (branching from fresh origin/main) git worktree add .worktrees/team-212 -b "$BRANCH" origin/main cd .worktrees/team-212 # 4. Do your work, commit, push git push -u origin "$BRANCH" ``` **⚠️ Never modify files on main.** All changes happen in worktrees only. ### Why This Matters - Linear's GitHub integration tracks PRs by branch name pattern - When you create a PR from a Linear branch, the issue **automatically moves to "In Review"** - When the PR merges, the issue **automatically moves to "Done"** - Manual branch names break this automation - Keeping main clean = no accidental pushes, easy worktree cleanup ### Quick Reference ```bash # Full workflow example ISSUE="TEAM-212" BRANCH=$({baseDir}/scripts/linear.sh branch $ISSUE) # Always start from fresh main cd ~/workspace/your-repo git checkout main && git pull origin main # Create worktree (inside .worktrees/) git worktree add .worktrees/${ISSUE,,} -b "$BRANCH" origin/main cd .worktrees/${ISSUE,,} # ... make changes ... git add -A && git commit -m "fix: implement $ISSUE" git push -u origin "$BRANCH" gh pr create --title "$ISSUE:

Linear

技能介绍

做什么

何时用

代理如何加载

文件分析

SKILL.md 与 Agent 调用

安装这个技能

相关技能

Self Improving Agent

Self Improving + Proactive Agent

Proactive Agent

Multi Search Engine