BC yotta-workflow
跨会话/跨项目通用工作流标准：让任何 AI 智能体活过会话——开工必读状态、状态只存项目根目录的 .workflow、进行中自动记流水/任务/决策、收工必留交接锚点。项目根目录是状态锚点，源码目录可嵌套且 .git 不等于项目根目录。触发：开工/接手项目、续测、收工、跨会话恢复、要落盘、多步开发、项目状态变化、跨智能体协作。边界：只记录项目状态（进度/任务/决策/流水），不写 AI 人格、用户偏好、关系或跨项目通用知识；轻量一次性问答不强制初始化。所有 AI 智能体通用。
跨会话/跨项目通用工作流标准：让任何 AI 智能体活过会话——开工必读状态、状态只存项目根目录的 .workflow、进行中自动记流水/任务/决策、收工必留交接锚点。项目根目录是状态锚点，源码目录可嵌套且 .git…
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: 15. 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 "agent_created"
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. No external tools needed
- 100Steps. 49 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1572 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
- +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
- -5TODO / placeholder text left in the skill
- +2Single-language instructions
- +3Description length 238: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 49 items
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.