Web To App Funnel

What it does

When your agent uses it

• Wants to design
• 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

Example prompts

• “open in app”
• “web to app”
• “smart app banner”
• “/web-to-app-funnel”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

1. 1Check for app-marketing-context.md
2. 2Ask: What web traffic does the user have or plan? (SEO, paid search, social ads with web destination, podcast, newsletter)
3. 3Ask: Monetization model — subscription (web payment is huge lever), IAP, ads, free
4. 4Ask: Current web property — landing page, full marketing site, none
5. 5Ask: Markets — US-only or global? (web payment rules differ in EU/Korea)
6. 6Ask: Current funnel metrics if available (web visit → install → activate → paid)

What it can do on your machine

Read from SKILL.md and the folder at commit 3919d7c. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • stripe

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Web To App Funnel loads about 2.1k tokens when it runs. Until then it costs about 193 tokens; SKILL.md has 836 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~193

When it runs · the whole SKILL.md, loaded when a task matches

~2.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from appeeky/aso-skills at commit 3919d7c, republished under its MIT licence (© appeeky). 836 words, ~2,132 tokens.

name

web-to-app-funnel

description

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.

metadata.version

1.0.0

Paid ad / SEO / TikTok bio
   ↓
Landing page with quiz (high conversion)
   ↓
Personalized result + plan
   ↓
Email capture
   ↓
Stripe checkout — PAID HERE
   ↓
"Get the app" page with QR + App Store / Play badges
   ↓
App install (deferred deep link carries paid status)
   ↓
App opens, calls backend with email/token, recognizes paid user
   ↓
Skip in-app paywall, go straight to product

WEB-TO-APP FUNNEL — <App Name>

PATTERN: <A / B / C> — Reason: <why this fits the model>

FUNNEL DESIGN:

Step 1: Traffic source
  Channels: <SEO / paid social / podcast / etc.>
  Landing URL: <URL>

Step 2: Landing / quiz
  Conversion target: visit → email capture <X%>
  Quiz length: <N> questions
  Personalization axes: <list>

Step 3: Payment (if Pattern B)
  Plan structure: <list>
  Stripe vs Paddle (if EU VAT): <choice>
  Conversion target: results → paid <X%>

Step 4: App install handoff
  Method: QR code + App Store / Play badges + SMS-me-the-link
  Deferred deep link tool: <Branch / OneLink / custom>

Step 5: App sign-in & activation
  Token / email-link sign-in
  Paid status verification: <flow>
  Skip in-app paywall: yes / no
  Activation event: <define>

COMPLIANCE CHECKLIST:
  [ ] No in-app links to web checkout (or External Purchase Link Entitlement requested)
  [ ] Privacy policy covers Stripe data + App data linkage
  [ ] App Store / Play app description doesn't reference web payment
  [ ] Universal Links / App Links domain verified

MEASUREMENT:
  - Visit → quiz start
  - Quiz start → email capture
  - Email capture → checkout
  - Checkout → paid (Stripe)
  - Paid → app install
  - App install → app sign-in
  - Sign-in → activation event

EXPECTED ECONOMICS:
  Saved fee per sub vs in-app: ~15-30% of LTV
  Higher CAC on web-first: typically yes, but offset by skipping App Store fee + email capture asset

© appeeky, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/web-to-app-funnel of appeeky/aso-skills.

Open the folder on GitHubat commit 3919d7c