AC pitch-visit-proposal
Use when the rep has an upcoming on-site or virtual client visit/meeting where they need to present a proposal or solution to one or more stakeholders — and they need help preparing before, navigating during, and following up after. Triggers include '下周要去客户拜访', '帮我准备提案演示', '客户约了 30/60 分钟会', '怎么准备拜访', '拜访现场怎么应对反对', '临走怎么定下一步', '拜访完怎么复盘', 'visit proposal', 'customer pitch meeting', 'on-site presentation', 'executive briefing prep', 'pre-visit brief', 'field presentation'. Do NOT use for product elevator pitch only, proposal document/Word/PDF generation, PPT layout, demo scripts, single-meeting-only objection deep-dive across many calls, post-call structured debrief, or deal progression/closing (use clinch-progression-strategy).
Use when the rep has an upcoming on-site or virtual client visit/meeting where they need to present a proposal or solution to one or more stakeholders — and…
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: 10. 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. 39 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1463 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
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 735: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 39 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (9 of 9)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 93.