AB payment-funnel-monitor
Monitor the payment last mile — initiate → success reconciliation → local method gaps — to recover conversion lost to failed checkouts. Use when payment success rate is below ~95%, specific countries (e.g. Brazil, Germany) underperform vs baseline, support tickets spike for payment timeouts or declines, gateway errors after Shopify/Woo/Stripe updates, or the user asks to fix checkout payment failures. Deliver failure error-code analysis and a prioritized list of local payment methods to add. Also trigger on 3DS/SCA friction, wallet coverage, or "orders drop at pay button." Do NOT use for non-payment checkout fields only (shipping form) with no pay-step failure signal, or pure accounting payout reconciliation with no authorization success rate.
As a process B 68/100 · Nearly there — weak spots: result and completion, inputs and preconditions, running it twice
How to improve
- 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: 6. 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 68/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 3 mutating operations with no state check
- 85Steps. 14 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 766 tokens
- medium 3 test cases, all positive: not one "should refuse" or "should ask first"
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
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 753: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 14 items
- +4Reference files are cited in the instructions (1 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.