BC flow-architect
流程架构师是跨平台自动化工作流的设计与执行能力包。它不只给JS示例，更解决四个高频 痛点：复杂分支逻辑难以调试、字段映射错位导致数据串列、重复触发造成重复处理、 API限流未处理导致批量失败。 核心能力： - YAML工作流DSL：用声明式YAML替代JS片段，可版本化、可diff、可dry-run - 干跑校验模式：先跑2-3条样本数据验证全链路，再放量 - 幂等键设计：每个工作流强制幂等键，杜绝重复触发重复处理 - 字段映射校验器：双向校验源字段→目标字段，缺失字段告警 - 限流处理模式：令牌桶 + 退避重试 + 批量请求 - 文档自动生成：从YAML生成工作流文档与可视化图 适用场景： - 电商价格监控、库存同步、订单处理 - 内容素材收集、格式转换、多平台发布 - 数据抓取、清洗、报告生成 - 客户服务自动回复、工单处理 - 项目进度跟踪、状态同步、提醒通知 差异化： - 原始版本用JS对象字面量定义工作流，本版改用YAML DSL可版本化 - 新增dry-run干跑校验章节 - 新增幂等键设计与重复触发防护 - 新增字段映射校验器与限流处理模式 - 增加工作流文档自动生成模板 - 增加故障排查表与FAQ 触发关键词：工作流构建、自动化流程、触发器、条件分支、YAML工作流、干跑、幂等、字段映射、限流
流程架构师是跨平台自动化工作流的设计与执行能力包。它不只给JS示例，更解决四个高频 痛点：复杂分支逻辑难以调试、字段映射错位导致数据串列、重复触发造成重复处理、 API限流未处理导致批量失败。 核心能力： - YAML工作流DSL：用声明式YAML替代JS片段，可版本化、可diff、可dry-run -…
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. 17 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2996 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 567: enough signal without eating the budget
- +4Structure: 33 headings
- +3Step-by-step instructions: 17 items
- +4Has examples (15 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.