CtrlK
BlogDocsLog inGet started
Tessl Logo

custom-product-pages

When the user wants to design, deploy, or measure Apple Custom Product Pages (CPP) — the alternate App Store product pages with different screenshots, preview videos, and promo text shown to users coming from specific URLs (typically ad campaigns or social posts). Use when the user mentions "Custom Product Page", "CPP", "alternate product page", "App Store URL variant", "ASA CPP", "campaign-specific landing page", "product page per audience", "App Store Connect CPP", "ppoUrl", "?cpp=" parameter, or "show different screenshots to different ad audiences". For App Store A/B tests on the default page, see ab-test-store-listing. For paid ad campaigns that route to CPPs, see apple-search-ads or ua-campaign.

70

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

75%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.

A well-structured, actionable skill body that leverages tables and templates to stay efficient while covering strategy, anatomy, measurement, and pitfalls. The main opportunities are minor: trimming redundancy, deepening the measurement steps, and adding an Apple-review-rejection recovery path.

Suggestions

Consolidate the overlapping 'not worth it' guidance between the 'When CPPs Are Worth It', 'Common Mistakes', and 'are NOT' table sections to remove redundancy.

Add concrete steps for pulling per-CPP metrics (e.g., specific App Store Connect Analytics filters or an API call) so the Measurement section is as actionable as the Output Template.

Add a short recovery branch in the review/launch plan for when Apple rejects a CPP variant (fix resubmit vs. drop variant).

DimensionReasoningScore

Conciseness

Mostly lean and efficient using tables and lists, assuming Claude's competence without explaining what the App Store is; minor redundancy between the 'are NOT worth it', 'Common Mistakes', and 'are NOT' table entries could be tightened.

4 / 5

Actionability

Provides a copy-paste output template and concrete navigation paths (App Store Connect → Analytics → Custom Product Pages; ASA → Ad Group → Creative Sets), with minor gaps such as the high-level measurement section lacking specific console/API query steps.

4 / 5

Workflow Clarity

Clear sequence from Initial Assessment through build, submit, wire URL, 14-day wait, and monitor, with explicit validation checkpoints (≥1,000 page views, kill criteria); minor gap is the absence of an Apple-review-rejection recovery loop.

4 / 5

Progressive Disclosure

Single well-organized SKILL.md with clear section headers and one-level cross-skill handoffs, no nested references; at ~150 lines with no bundle files, content is appropriately placed though a couple of dense sections could in principle be split out.

4 / 5

Total

16

/

20

Passed

Description

95%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.

A strong, well-targeted description that clearly states what the skill does, when to use it, and how it differs from neighboring skills. The only soft spot is that the action verbs (design/deploy/measure) are slightly more abstract than the most concrete anchor examples.

DimensionReasoningScore

Specificity

Names the domain and concrete actions ('design, deploy, or measure') plus the specific changeable elements (screenshots, preview videos, promo text), but the three verbs are somewhat abstract compared to the highly concrete anchor-5 examples.

4 / 5

Completeness

Explicitly answers both what (alternate App Store product pages with screenshots/videos/promo text shown via specific URLs) and when (a full 'Use when the user mentions...' clause with concrete trigger phrases).

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including synonyms and parameter forms ('Custom Product Page', 'CPP', 'alternate product page', 'ASA CPP', 'ppoUrl', '?cpp=', 'show different screenshots to different ad audiences').

5 / 5

Distinctiveness Conflict Risk

Clear niche with distinct CPP-specific triggers and explicit disambiguation handoffs to ab-test-store-listing, apple-search-ads, and ua-campaign, minimizing overlap risk.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Eronred/aso-skills
Reviewed

Table of Contents

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.