AB subscription-churn-lifecycle
Churn prevention and lifecycle operations for subscription/recurring payment products (monthly coffee, beauty subscription boxes, pet supplies, content/software membership). Trigger when users mention subscription or recurring billing, renewal or retention rate, first-month or first-three-months churn, pause vs cancel decisions, lifecycle ops (onboarding, activation, pre-renewal reminder, win-back), improving LTV/CLV, "my subscribers keep canceling," "first-month churn is too high," "how to set up onboarding flow," "pause vs cancel," "renewal reminder timing," "dunning and failed payments," or "how do I keep subscribers longer." Output structured subscription diagnosis, churn-path analysis, and lifecycle playbooks—not generic "send more coupons." Use this skill even when the user says "nobody renews after the first box" or "how do I reduce subscription churn."
As a process B 77/100 · Nearly there — weak spots: inputs and preconditions, running it twice, progress reporting
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: 11. 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 77/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 15 mutating operations with no state check
- 60Failures and branches. 2 branches
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 65 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3051 tokens
- medium 4 test cases, all positive: not one "should refuse" or "should ask first"
- low No test case covers injection arriving through data
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 872: 120–800 characters recommended
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +5Description quotes 10 example trigger phrases
- +4Structure: 17 headings
- +3Step-by-step instructions: 65 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (4 of 5)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 92.