BC workflow-symphony
工作流交响曲是面向一人公司的无代码自动化编排能力包。它不只罗列Zapier/Make/n8n的对比表， 更解决四个高频痛点：不知道该自动化什么、选错工具反复迁移、上线后维护负担失控、 测试不充分就上线导致生产事故。 核心能力： - 自动化机会雷达图：用频次×耗时×重复度三维定位高价值机会 - 工具决策树：按工作流复杂度、预算、技术能力分层推荐Zapier/Make/n8n - 维护日历：周/月/季度三级维护节奏，避免自动化"上线即腐烂" - 上线前checklist：12项强制检查，杜绝带病上线 - 静默失败防护：错误告警统一路由 + 健康度巡检 - 工作流文档模板：每个自动化一份文档，未来自己也能看懂 适用场景： - 一人公司想自动化但不知从何下手 - 已用Zapier但卡在限流，纠结要不要迁n8n - 自动化上线后经常静默失败 - 自动化越攒越多，维护失控 - 想向老板证明自动化投入划算 差异化： - 原始版本只给工具对比表，本版补齐"选前决策树+选后维护日历" - 新增自动化机会雷达图（频次×耗时×重复度三维定位） - 新增12项上线前checklist - 新增静默失败防护与统一告警路由 - 新增工作流文档模板与ROI实战案例 触发关键词：无代码自动化、一人公司、Zapier、Make、n8n、自动化机会、工具选型、维护、上线检查
工作流交响曲是面向一人公司的无代码自动化编排能力包。它不只罗列Zapier/Make/n8n的对比表， 更解决四个高频痛点：不知道该自动化什么、选错工具反复迁移、上线后维护负担失控、 测试不充分就上线导致生产事故。 核心能力： - 自动化机会雷达图：用频次×耗时×重复度三维定位高价值机会 -…
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: 0. 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. 73 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1591 tokens
- 100Running it twice. No mutating operations
- low 13 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
- +2Single-language instructions
- +3Description length 582: enough signal without eating the budget
- +4Structure: 45 headings
- +3Step-by-step instructions: 73 items
- +4Has examples (11 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.