AC saas-pricing-auditor
Audit a SaaS pricing page and return a scorecard, specific rewrites, and an A/B test priority queue. Diagnoses tier psychology (3-tier vs 4-tier, where the anchor sits), price points (charm vs round, currency formatting, decoy effect), feature-gating logic (the right and wrong reasons to gate a feature), the freemium-vs-trial decision, value-metric selection (per-seat, per-usage, hybrid, outcome-based), expansion-revenue mechanisms (overages, add-ons, tier upgrades, seat sprawl), monthly/annual toggle defaults, comparison-table clarity, and social-proof placement. Outputs a 1-10 score per dimension with specific rewrites and a ranked test backlog. Use when asked to review a pricing page, redesign tiers, raise prices, fix poor conversion, choose a value metric, decide between freemium and trial, or prep for a pricing repackage.
As a process C 62/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, running it twice
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: 2. 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 62/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 4 mutating operations with no state check
- 55Failures and branches. 1 branches
- 60Result and completion. Output format stated, no completion criterion
- 85Steps. 104 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3762 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 14 top-level sections: this looks like several domains in one skill
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 838: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +4Structure: 38 headings
- +3Step-by-step instructions: 104 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.