AC abandoned-checkout-monitor
Deep cart-to-checkout funnel monitoring, abnormal friction detection, and multi-touch recovery playbooks for e-commerce. Use this skill whenever the user mentions abandoned carts, checkout drop-off, low checkout conversion (under ~2%), why no orders, no sales, cart not converting, customers leaving at payment, shipping shock, high shipping cost by region, payment failed, gateway errors, high-AOV items stuck in cart without purchase, or wants recovery emails / win-back sequences for checkout leavers. Also trigger on real-time cart behavior, funnel leaks, or low checkout conversion — even if the merchant only asks vaguely ("why no orders," "nobody's buying"). Do NOT use for simple stock lookups, basic order status or detail-only views, or pure inventory questions without checkout context.
As a process C 59/100 · Has gaps — 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 59/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. 9 mutating operations with no state check
- 60Tools and files. Uses tools (node) that frontmatter does not declare
- 60Failures and branches. 2 branches
- 100Steps. 23 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1025 tokens
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
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +4Description says when NOT to use the skill
- +3Description length 797: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 23 items
- +4Reference files are cited in the instructions (1 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 93.