BC linear-flow-cli-pro
Linear流程CLI（专业版）面向使用Linear进行复杂项目管理的工程团队与AI Agent运行时，在免费版基础上解锁全部高级能力：批量操作、dry-run预览、自动化策略、Slack/Ticket上下文集成、Git/JJ工作流联动、高级GraphQL查询模板、Webhook管理、跨团队Initiative管理。让AI Agent成为真正的Linear自动化中枢. 核心能力：批量Issue创建/更新/删除（CSV/JSON驱动）、dry-run预览所有写入操作、自动化策略（suggest-only/preview-required/autonomous）、Slack/Ticket上下文文件解析（--context-file + --apply-triage）、Git/JJ工作流联动（提交关联Issue自动更新状态）、高级GraphQL查询模板库、Webhook管理与通知配置、跨团队Initiative与里程碑管理、项目状态更新（project-update）、通知管理、超时感知写入语义、源邻近任务摄入. 适用场景：AI Agent深度自动化任务管理、大规模任务批量迁移与重构、跨团队协作的Initiative管理、Slack驱动的任务分流、Git提交自动关联任务状态、项目管理仪表盘、企业级Linear工作流定制. 差异化：在免费版基础上新增八大高级能力，针对Agent原生运行时场景设计完整工作流。提供多角色场景指南（开发者/Scrum Master/DevOps/项目经理/技术负责人）、性能优化策略、多平台集成示例、版本升级迁移指南。专业版通过SkillHub SkillPay发布。保留原始MIT-0版权声明. 适用关键词：批量操作、dry-run预览、自动化策略、Slack集成、Git联动、Webhook、Initiative、Agent运行时
Linear流程CLI（专业版）面向使用Linear进行复杂项目管理的工程团队与AI…
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 787 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
description-no-whenneither description nor a "## When to Use" section says when to use the skill - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "edition" - note
frontmatter-keyunknown frontmatter key "tools" - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 51/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 56 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3481 tokens
- low 12 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -5TODO / placeholder text left in the skill
- +2Single-language instructions
- +3Description length 787: enough signal without eating the budget
- +4Structure: 39 headings
- +3Step-by-step instructions: 56 items
- +4Has examples (20 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 59.