AC zmm-decide
📐 詹明明·拿不准的时候 ——拿不准的时候用。三种情况：①这件事要不要做（决策推演）②我这问题到底是什么问题（拆到本质）③知道该做但就是动不了（先排除结构性原因，再谈心理）。不替你决定，但会把问题问对、把约束摆平、把判据给死，最后落成一条到期会自动回来找你的承诺。 触发方式：/zmm-decide、/拿不准、/要不要做、/卡住了、「这个单接不接」「要不要开第二家」「该不该investment」「我这问题到底是什么」「知道该做但就是不动」「想不清楚」 For owner-operators facing a fork or a stall. Three modes: decide whether to do something, dissolve the question down to what is actually being asked, or diagnose why a known task is not moving — structural causes ruled out before psychological ones. Trigger: /zmm-decide, "should I take this deal", "should I open a second location", "what is my actual problem", "I know what to do but can't start" —— 📐 詹明明 · 不给公式，给判据。每条规则都标了实测代价。
📐 詹明明·拿不准的时候 ——拿不准的时候用。三种情况：①这件事要不要做（决策推演）②我这问题到底是什么问题（拆到本质）③知道该做但就是动不了（先排除结构性原因，再谈心理）。不替你决定，但会把问题问对、把约束摆平、把判据给死，最后落成一条到期会自动回来找你的承诺。…
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- 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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName"
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. 28 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2167 tokens
- 100Running it twice. No mutating operations
- low 11 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
- +1No license
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +3Description length 661: enough signal without eating the budget
- +4Structure: 35 headings
- +3Step-by-step instructions: 28 items
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.