CtrlK
BlogDocsLog inGet started
Tessl Logo

web-to-app-funnel

When the user wants to design or optimize the funnel that takes web visitors into installing and onboarding the app — including smart app banners, web-to-app deep links, deferred deep links, web onboarding (Stripe-paid web flow before app install), QR codes, "open in app" CTAs, and the trade-off between paying on web vs in-app. Use when the user mentions "web to app", "smart app banner", "Stripe before app", "web paywall before install", "Branch web SDK", "web funnel for app", "AppsFlyer OneLink web", "Universal Links", "App Links", "QR code to app", "open in app", "deferred deep link from web", or "should I sell on web first then push to app". For pure in-app onboarding, see onboarding-optimization. For deep link infra, see attribution-setup.

72

Quality

88%

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

77%

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

A highly actionable, well-sequenced strategy skill with a strong output template and compliance checklist. Its main weaknesses are the dated, motivational "Why Web-to-App Matters in 2025" section and the absence of any progressive disclosure into reference files despite the body's length.

Suggestions

Drop or relocate the '## Why Web-to-App Matters in 2025' section: its drivers (App Store/Play fees, EU DMA, Korean law) are largely known to Claude, and the hardcoded '2025' is now stale; keep only genuinely decision-relevant, evergreen facts inline.

Add progressive disclosure by splitting the detailed compliance table and the full Output Template into reference files (e.g. references/compliance.md, references/output-template.md) and linking to them from SKILL.md, reducing the monolithic body.

Tighten the 'Smart Banners & Open-in-App' and quiz-mechanics sections by leading with the concrete tool/best-practice list and trimming explanatory framing.

DimensionReasoningScore

Conciseness

The body is mostly lean and information-dense, but the "## Why Web-to-App Matters in 2025" table explains drivers (App Store fees, EU DMA) Claude largely already knows and hardcodes a now-stale "2025" date outside any deprecated/old-patterns section, landing at the score-2 anchor of mostly efficient but with unnecessary explanation that could be tightened.

2 / 3

Actionability

Provides concrete, copy-paste-ready guidance: three named patterns with use-when criteria, a sequenced Pattern-B mechanic, specific critical engineering pieces (deferred deep link carrying email/token, backend mapping Stripe customer → app user, "already paid" check), quiz best practices (6–12 questions, 30–60s, Stripe Checkout same-tab on mobile), and a full output template — matching the score-3 anchor for specific, actionable instruction.

3 / 3

Workflow Clarity

Clear sequencing throughout — numbered Initial Assessment, step-by-step Pattern-B flow diagram, a structured Step 1–5 output template, plus an explicit COMPLIANCE CHECKLIST and MEASUREMENT section that serve as validation checkpoints for a complex process, meeting the score-3 anchor.

3 / 3

Progressive Disclosure

Well-organized into clear sections, but it is a single ~180-line monolithic SKILL.md with no bundle files; content that could be split (the compliance table, the full output template) is inline and the only file reference (app-marketing-context.md) is to an external/optional context file rather than a one-level-deep detail file, fitting the score-2 anchor.

2 / 3

Total

10

/

12

Passed

Description

100%

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 description: concrete capability list, extensive natural trigger terms, explicit what-and-when structure, and explicit disambiguation against sibling skills. It stays in third-person framing ("the user wants…") and avoids fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — "smart app banners", "web-to-app deep links", "deferred deep links", "web onboarding (Stripe-paid web flow before app install)", "QR codes", "'open in app' CTAs", and the web-vs-in-app payment trade-off — matching the score-3 anchor of multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers both what ("design or optimize the funnel that takes web visitors into installing and onboarding the app") and when ("Use when the user mentions…"), satisfying the score-3 anchor for explicit what-and-when triggers.

3 / 3

Trigger Term Quality

Broad coverage of natural phrases a user would say ("web to app", "smart app banner", "Stripe before app", "web paywall before install", "QR code to app", "open in app", "should I sell on web first then push to app") alongside tool names, matching the score-3 anchor for good coverage of natural terms.

3 / 3

Distinctiveness Conflict Risk

Carves a clear niche and actively disambiguates with "For pure in-app onboarding, see onboarding-optimization. For deep link infra, see attribution-setup.", making conflicts with adjacent skills unlikely.

3 / 3

Total

12

/

12

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.