AC Atlas Conversion Rate Optimizer
Conversion rate optimization skill for SaaS, agencies, and product teams. Generates high-converting copy, A/B test plans, CRO roadmaps, and growth experiments. Use for landing pages, email signup flows, pricing pages, SaaS onboarding, and product conversion optimization.
As a process C 52/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Risky intent
intent-offensive-securitySKILL.md:132Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)"For bug bounty teams: first-pass audits in 20 minutes, not 20 hours"
quoted
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "changelog"
Process rating: all ten parameters 52/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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (Atlas Conversion Rate Optimizer) differs from the folder (atlas-conversion-rate-optimizer)
- 60Failures and branches. 2 branches
- 100Tools and files. No external tools needed
- 100Steps. 52 steps
- 100Execution cost. Instruction body is 1488 tokens
- low 10 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 271: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 52 items
- +4Has examples (5 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.