ab-test-store-listing

When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/ab-test-store-listing/SKILL.md

Quality

Content

63%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, actionable A/B testing playbook with clear sequencing and concrete templates, but it carries redundant tables, leaves the sample-size calculation as a placeholder, and inlines catalog content that would benefit from a separate reference file. No bundle files are provided to offload detail.

Suggestions

Provide an actual sample-size formula or a concrete lookup rule instead of the "~[N] impressions" placeholder so the Sample Size step is executable.

Deduplicate the "Common Test Ideas" tables against the "Impact x Effort Matrix" to trim tokens, or move the test-idea catalog into a referenced reference file.

Signal the `app-marketing-context.md` dependency as a real markdown link and clarify whether it is expected to exist in the bundle, since no `references/` files are present.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient tables and templates, but the "Common Test Ideas" tables restate lift ranges already in the "Impact x Effort Matrix", and explanatory lines like "You are an expert in..." add padding; it could be tightened without losing clarity, so it sits at the midpoint rather than 4.	3 / 5
Actionability	Concrete, copy-paste-ready templates (hypothesis formula, Test Plan output format) and specific App Store Connect steps cover common cases, but the sample-size section uses placeholders ("Required sample per variant: ~[N]") without an actual formula, leaving a minor executable gap.	4 / 5
Workflow Clarity	The 5-step Test Design Framework (Hypothesis, Variants, Sample Size, Run, Interpret) and the Initial Assessment are clearly sequenced with checkpoints like "don't stop early" and a significance checklist; it is not 5 because there is no explicit validate/fix/retry feedback loop.	4 / 5
Progressive Disclosure	Sections are well-organized, but the skill is ~220 lines with no bundle files, catalog content (Common Test Ideas) that could live in a reference is inlined, and the one external reference ("app-marketing-context.md") is mentioned in backticks rather than as a clearly signaled link; it is not 4 because references are not clearly signaled and content is not split out.	3 / 5
	Total	14 / 20 Passed

Description

82%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it explicitly covers both what the skill does and when to trigger it, with rich natural trigger terms and clear boundary guidance against sibling skills. The only gap is modest action specificity, since the full design/run/interpret workflow is not enumerated.

Dimension	Reasoning	Score
Specificity	It names the domain and a concrete action ("A/B test App Store product page elements to improve conversion rate") but lists only 1-2 actions and omits the full design/run/interpret workflow, so it is not comprehensive; it is not a 2 because the action and domain are concrete, and not a 4 because several specific actions are missing.	3 / 5
Completeness	It explicitly states both what it does ("A/B test App Store product page elements to improve conversion rate") and when to use it ("Also use when the user mentions ..."), with concrete trigger phrases, matching the anchor that requires both what and when.	5 / 5
Trigger Term Quality	Strong natural coverage with seven triggers including an abbreviation and its expansion ("CPP", "custom product pages", "A/B test", "test my screenshots", "test my icon"), but a few natural phrasings like "App Store Connect", "experiment", or "store listing" are absent, so it falls just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	It occupies a clear niche (App Store A/B testing) with distinct triggers and adds explicit boundary routing ("For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization."), minimizing conflict with adjacent skills.	5 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Eronred/aso-skills
Path: skills/ab-test-store-listing/SKILL.md
Commit: 4df730f

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.