AC biz-auto-hub
商业自动中枢是面向一人公司与小团队的自动化架构师能力包。它不只教你怎么搭工作流， 更解决三个高频痛点：自动化做完不知道省没省钱、自动化失败却无人察觉、不该自动化的 任务也硬自动化反而增加维护负担。 核心能力： - 自动化准入评分卡：用频次/时长/错误影响/复杂度/集成度五维打分，过滤低ROI任务 - 静默故障防护网：强制告警路由 + 健康度周报模板，杜绝"自动跑着跑着就坏了没人管" - ROI量化器：内置公式与真实数字示例，把"感觉省时间"变成可核算的月度收益 - 凭证保险柜模式：统一管理API Key/OAuth，避免散落在多个脚本里 - 六类工作流模板：线索、发票、入职、报告、客服、内容发布 适用场景： - 一人公司想自动化但不知从何下手 - 已有自动化但经常静默失败、无人察觉 - 需要向老板/合伙人证明自动化投入划算 - 凭证散落各处，难以轮换 差异化： - 原始版本只给设计模板，本版补齐"该不该自动化"的决策前置门和"自动化后健康吗"的 监控后置门，形成完整闭环 - 所有模板中文化并附带真实数字示例（发票处理月省36.7小时、节省1835美元） - 新增静默故障防护章节与凭证保险柜模式 - 压缩重复说明，按需加载高级模式章节 触发关键词：商业自动化、自动化架构、ROI量化、静默故障、凭证管理、工作流设计、自动化审计
商业自动中枢是面向一人公司与小团队的自动化架构师能力包。它不只教你怎么搭工作流， 更解决三个高频痛点：自动化做完不知道省没省钱、自动化失败却无人察觉、不该自动化的 任务也硬自动化反而增加维护负担。 核心能力： - 自动化准入评分卡：用频次/时长/错误影响/复杂度/集成度五维打分，过滤低ROI任务 -…
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. 33 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1989 tokens
- 100Running it twice. No mutating operations
- 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
- +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 3 example trigger phrases
- +3Description length 576: enough signal without eating the budget
- +4Structure: 39 headings
- +3Step-by-step instructions: 33 items
- +4Has examples (16 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.