BC automation-workflow-builder
自动化工作流构建器，设计并执行跨平台自动化流程，支持触发器、条件判断、多步骤操作。\n\n核心能力:\n- 效率工具领域的专业化AI辅助工具\n\ - 基于高人气开源Skill深度优化升级\n- 移除风险代码,增强安全性和稳定性\n\n适用场景:\n- 工作流自动化、任务调度、批处理\n- 独立开发者与一人公司效率提升\n\ - 自动化工作流与智能决策辅助\n\n差异化:经过深度优化,去除原始风险代码,清理外部依赖引用,增强元数据和触发关键词,完全适配SkillHub平台规范。\n\n\ 触发关键词: builder, 平台自动化流, automation-workflow-builderï¼\x88è\x87ªå\x8A¨å\x8C\x96å·¥ä½\x9C\ æµ\x81æ\x9E\x84建å\x99¨ï¼\x8C设计并æ\x89§è¡\x8C跨平å\x8F°è\x87ªå\x8A¨å\x8C\ \x96æµ\x81ç¨\x8Bï¼\x8Cæ\x94¯æ\x8C\x81å®\x9Aæ\x97¶è§¦å\x8F\x91ã\x80\x81æ\x96\x87\ 件ç\x9B\x91æ\x8E§ã\x80\x81å¤\x9Aæ¥éª¤æ\x93\x8Dä½\x9Cã\x80\x82é\x80\x82ç\x94¨äº\x8E\ æ\x95°æ\x8D®å\x90\x8Cæ¥ã\x80\x81å\x86, 自动化工作流, automation, 设计并执行跨, 容å\x8F\x91\ å¸\x83ã\x80\x81æ\x8A¥å\x91\x8Aç\x94\x9Fæ\x88\x90ã\x80\x82ï¼\x89, workflow
自动化工作流构建器，设计并执行跨平台自动化流程，支持触发器、条件判断、多步骤操作。\n\n核心能力:\n- 效率工具领域的专业化AI辅助工具\n\ - 基于高人气开源Skill深度优化升级\n- 移除风险代码,增强安全性和稳定性\n\n适用场景:\n- 工作流自动化、任务调度、批处理\n-…
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. 26 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 612 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
- +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 740: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 26 items
- +4Has examples (4 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.