AC workflow-lite
轻量工作流是自动化的"5分钟入门版"。它不堆砌完整方法论，只解决一个问题： 我想试试自动化，但不想读5000字文档。给一个快速判断、三个最小模板、一张速查表， 立刻能用。 核心能力： - 30秒判断：该不该自动化（频次×耗时×重复度） - 5分钟搭建：3个最小可执行工作流模板（表单→表格、付款→开票、定时→发消息） - 单页速查：触发器/动作/常见坑一张表搞定 - 按需深入：需要复杂能力时跳转flow-architect或workflow-symphony 适用场景： - 从没做过自动化，想快速试一个 - 只需要最简单的2-3步工作流 - 不想读长文档，要立刻上手 - 评估某个任务值不值得自动化 差异化： - 原始版本与workflow-symphony内容重复且冗长，本版做真正的"轻量化" - 砍掉高级模式、长篇ROI计算、工具深度对比 - 聚焦"判断+3模板+速查表"三件事 - 提供到flow-architect/workflow-symphony的进阶路径 触发关键词：自动化入门、快速自动化、简单工作流、表单到表格、自动开票、定时通知
轻量工作流是自动化的"5分钟入门版"。它不堆砌完整方法论，只解决一个问题： 我想试试自动化，但不想读5000字文档。给一个快速判断、三个最小模板、一张速查表， 立刻能用。 核心能力： - 30秒判断：该不该自动化（频次×耗时×重复度） - 5分钟搭建：3个最小可执行工作流模板（表单→表格、付款→开票、定时→发消息）…
As a process C 53/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.
- 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-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "tools"
Process rating: all ten parameters 53/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
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 14 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 630 tokens
- 100Running it twice. No mutating operations
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +3Description length 481: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 14 items
- +4Has examples (3 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.