AC clinch-progression-strategy
Use when a live deal is stuck or stalled and the rep needs an overall advancement plan — not a single-call debrief, not a live objection reply, not a closing push, but a forward plan from current state to signed contract. Triggers: '这个单卡住了怎么推', '从现在到签约还要过哪几关', '推进思路', 'deal progression', 'advancement plan', 'next steps roadmap', 'stuck deal path forward', '商机推进路径', '分阶段动作清单'. Do NOT use for single-communication debrief, live objection handling, final-mile closing sequence, invest-or-not decision, or deal health diagnosis.
Use when a live deal is stuck or stalled and the rep needs an overall advancement plan — not a single-call debrief, not a live objection reply, not a closing…
As a process C 57/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
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: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 57/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
- 50When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 40 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1642 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
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 527: enough signal without eating the budget
- +4Structure: 27 headings
- +3Step-by-step instructions: 40 items
- +4Has examples (1 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: 93.