Token导航 LogoToken导航

Agent Skill · 研究检索

linear-workflow-manager(Linear 工作流 manager)

用于处理 Linear 项目、Issue、团队、周期和产品开发任务流。它适合让 Agent 辅助查询任务状态、整理需求队列、创建缺陷或汇总迭代进展。使用时需要确认 workspace、team、label、assignee 和状态流转规则;涉及批量创建或修改任务时,应先核对字段和目标团队,避免把草稿需求直接写入正式项目。

linear-workflow-manager 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为接触敏感数据;许可证为 MIT,暂无第三方扫描结果,按安装量在研究检索类的 73,675 个 Skill 里排第 56,510。

总安装 449周安装 18GitHub Stars 公开资料未说明下载 145核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:linear-workflow-manager(Linear 工作流 manager)
来源仓库:https://github.com/synapz-org/linear-workflow-manager
仓库路径:skills/linear-workflow-manager
安装命令:
npx skills add synapz-org/linear-workflow-manager --skill "linear-workflow-manager"
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

AgentSkills.tonpx skills
npx skills add synapz-org/linear-workflow-manager --skill "linear-workflow-manager"

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

Linear Workflow Manager 技能自动化管理跨团队开发流程与审批链。适用于敏捷团队集成 CI/CD 与需求评审环节,提升交付效率。

通过 npx skills add synapz-org/linear-workflow-manager --skill "linear-workflow-manager" 安装。使用前需配置 webhook 与权限映射,确保触发器正确响应。建议在非高峰时段测试流程变更,避免影响正常迭代节奏。

来源仓库内路径:skills/linear-workflow-manager

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add synapz-org/linear-workflow-manager --skill "linear-workflow-manag…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

linear-workflow-manager 怎么安装?

在终端执行 npx skills add synapz-org/linear-workflow-manager --skill "linear-workflow-manager"。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

linear-workflow-manager 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

linear-workflow-manager 需要什么权限?

权限级别是接触敏感数据。该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

linear-workflow-manager 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

linear-workflow-manager 用的人多吗?

公开数据是累计安装 449 次,近一周安装 18 次,下载 145 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

linear-workflow-manager 安全吗?

没有查到第三方扫描结果,安全性无法从公开资料判断,安装前请自行审查源码、依赖和命令行为。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 许可证明确为 MIT,商用和分发边界好判断。

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 没有第三方扫描结果,安全性只能靠自己读源码判断。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 要求有安全扫描结论才肯安装的团队。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
linear-workflow-manager

Linear 工作流 manager · 本页

449—接触敏感数据MIT未收录

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
linear-workflow-manager
description
This skill should be used when organizing daily work with Linear, starting the work day, reviewing priorities, triaging issues, or managing status updates. Use it for daily standup preparation, automated issue triage, workload planning, and status reporting. Integrates with Linear GraphQL API for seamless issue management.

Linear Workflow Manager

Overview

This skill helps organize your work day with Linear by automating daily planning, issue triage, and status updates. It leverages autonomous Claude agents to process issues, analyze workload, and generate reports, while providing structured workflows for common Linear tasks.

Core Workflows

1. Daily Standup & Planning

Trigger: "Start my work day" or "Plan my day with Linear"

Workflow:

  1. Fetch high priority items - Query Linear for issues assigned to you filtered by priority (Urgent, High)
  2. Analyze workload - Review issue count, estimates, deadlines, and blockers
  3. Suggest daily priorities - Recommend which issues to tackle first based on:

- Priority level - Due dates - Dependencies and blockers - Project milestones - Team needs

  1. Create daily plan - Present organized plan with time estimates and suggested ordering

Agent Usage: Launch a planning agent with Task tool (subagent_type: general-purpose) to:

  • Analyze the full workload context
  • Identify dependencies and blockers
  • Generate prioritized task list
  • Estimate time allocations

Example interaction:

User: "Start my work day"
Assistant: I'll help you plan your day with Linear.
[Executes: linear.sh query queries/planning/my-priorities.json]
[Analyzes output and creates prioritized plan]

2. Issue Triage

Trigger: "Triage new Linear issues" or "Process unassigned issues"

Workflow:

  1. Fetch untriaged issues - Query Linear for new/unassigned issues or issues without labels/priority
  2. Categorize each issue - For each issue, analyze:

- Content and context - Urgency and impact - Appropriate team/assignee - Required labels and project

  1. Apply metadata - Set priority, add labels, assign to team/person, link to projects
  2. Document decisions - Add comment explaining triage decisions for transparency

Agent Usage: Launch a triage agent with Task tool (subagent_type: general-purpose) to:

  • Process multiple issues in batch
  • Apply consistent triage criteria
  • Update Linear issues via GraphQL mutations
  • Generate triage summary report

Example interaction:

User: "Triage new Linear issues"
Assistant: I'll process untriaged issues in your Linear workspace.
[Executes: linear.sh query queries/triage/untriaged-issues.json]
[Analyzes issues and updates via GraphQL mutations]

Triage Criteria: Load references/triage_criteria.md for team-specific guidelines on:

  • Priority assignment rules
  • Label taxonomy
  • Assignment routing
  • SLA expectations

3. Status Updates & Reporting

Trigger: "Generate status update" or "Create Linear progress report"

Workflow:

  1. Define scope - Ask user what to report on:

- Personal work (your issues) - Team work (team's issues) - Project work (specific project or milestone) - Custom filter

  1. Fetch relevant issues - Query Linear with appropriate filters
  2. Generate report - Create structured summary including:

- Completed work (since last report) - In-progress work (current status) - Blocked items (with blockers identified) - Upcoming work (next priorities) - Key metrics (velocity, completion rate)

  1. Format for audience - Adapt tone/detail for standup vs. stakeholder update

Agent Usage: Launch a reporting agent with Task tool (subagent_type: general-purpose) to:

  • Aggregate issue data across time periods
  • Identify trends and patterns
  • Generate clear, concise summaries
  • Format for different audiences

Example interaction:

User: "Generate my weekly status update"
Assistant: I'll create a status report for your Linear work this week.
[Executes: linear.sh query queries/reporting/completed-this-week.json]
[Analyzes data and generates formatted summary]

Report Templates: Load references/report_templates.md for standard formats like:

  • Daily standup updates
  • Weekly progress reports
  • Sprint retrospectives
  • Stakeholder summaries

Linear GraphQL Integration

This skill uses direct Linear GraphQL API access for all Linear operations. No MCP required.

Setup: Ensure Linear API key is configured in ~/.claude/.env:

LINEAR_API_KEY=lin_api_xxx

Helper Script: scripts/linear.sh provides command interface:

linear.sh query <query-file>           # Execute query template
linear.sh create-issue <title> <desc>  # Quick issue creation
linear.sh list-issues                  # List your issues
linear.sh my-day                       # Today's priorities

Query Templates: Pre-built GraphQL queries in queries/ directory:

  • planning/ - Daily standup, workload, deadlines
  • triage/ - Untriaged issues, priority updates, assignments
  • reporting/ - Completed work, blockers, velocity
  • common/ - Teams, search, CRUD operations

For Agents:

  • Start at references/query-index.md to find the right query
  • Use linear.sh query <template> for simple execution
  • Or construct custom GraphQL with curl for complex needs
  • See references/examples.md for patterns and workflows

Best Practices

Daily Workflow

  1. Start each work day with the planning workflow to set priorities
  2. Use triage workflow for any new issues that come in during the day
  3. End the day with a quick status update to track progress

Agent Coordination

  • Use agents for batch operations (triage multiple issues, generate reports)
  • Keep user in the loop with progress updates
  • Present agent findings for user review before bulk updates

Customization

  • Add team-specific triage criteria to references/triage_criteria.md
  • Customize report templates in references/report_templates.md
  • Adjust priority rules and workflows to match your team's process

Quick Reference

Start work day: "Start my work day" → Planning agent analyzes high priority items

Triage issues: "Triage new issues" → Triage agent processes untriaged items

Generate report: "Create status update" → Reporting agent summarizes work and progress

Custom query: "Show me [specific filter]" → Query Linear directly with helper script or GraphQL

平台分布

OpenCode

27.21%
按下载量换算39

Claude Code

24.69%
按下载量换算36

Cursor

17.39%
按下载量换算25

Codex

12.14%
按下载量换算18

Gemini CLI

8.65%
按下载量换算13

windsurf

3.89%
按下载量换算6

安全审计

暂无安全审计结果可展示。

权限和风险

接触敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills