AC success-expansion
Use when a customer is already live and producing value, and the rep+CS need to identify account-expansion opportunities (upsell / cross-sell / seat / new-module / new-department) from usage and organizational signals, build a structured expansion case, run the expansion conversation, and hand off to renewal or downstream deal flow. Triggers: '增购', '向上销售', '交叉销售', '加坐席', '升级套餐', '加模块', '账户拓展', 'upsell', 'cross-sell', 'land and expand', 'NRR'. Do NOT use for new-logo acquisition, renewal itself (success-renewal-management), pricing negotiation (clinch-negotiation-pricing), contract signing, or first-value proof (its usage data is INPUT here).
Use when a customer is already live and producing value, and the rep+CS need to identify account-expansion opportunities (upsell / cross-sell / seat /…
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: 7. 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. 15 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1011 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
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 649: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 15 items
- +4Reference files are cited in the instructions (6 of 6)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.