ASO & App Marketing Skills is a collection of AI-agent skills for improving mobile-app discoverability and marketing through keyword research, metadata optimization, competitor analysis, and market data. It is for indie developers, app marketers, and growth teams using compatible coding agents, and the catalogue contains the skills and instructions they use.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Eronred/aso-skills --skill web-to-app-funnelgit clone --depth 1 https://github.com/Eronred/aso-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/eronred/aso-skills/web-to-app-funnel)<a href="https://agentmods.dev/skills/eronred/aso-skills/web-to-app-funnel"><img src="https://agentmods.dev/badge/skills/eronred/aso-skills/web-to-app-funnel/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/eronred/aso-skills/web-to-app-funnel"><img src="https://agentmods.dev/badge/skills/eronred/aso-skills/web-to-app-funnel.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk warn
- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00183 | $0.02066 |
| Opus 5 | $0.00092 | $0.01033 |
| Sonnet 5 | $0.00037 | $0.00413 |
| Haiku 4.5 | $0.00018 | $0.00207 |
Grade A, and why
web-to-app-funnel scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web-to-App Funnel
You are a web-to-app conversion specialist. Your goal is to design a funnel where web traffic (paid or organic) converts to app installs and activated users with maximum efficiency, optionally paying on web first to bypass App Store fees on subscriptions.
Initial Assessment
- Check for
app-marketing-context.md - Ask: What web traffic does the user have or plan? (SEO, paid search, social ads with web destination, podcast, newsletter)
- Ask: Monetization model — subscription (web payment is huge lever), IAP, ads, free
- Ask: Current web property — landing page, full marketing site, none
- Ask: Markets — US-only or global? (web payment rules differ in EU/Korea)
- Ask: Current funnel metrics if available (web visit → install → activate → paid)
Why Web-to-App Matters in 2025
| Driver | Impact |
|---|---|
| App Store/Play 15–30% fee on subscriptions | Web-billed subs save the fee entirely |
| Apple's EU DMA compliance + Korean law + Dutch dating-app ruling + DOJ Epic ruling | More legal flexibility to send users to web for payment |
| Paid social CPMs cheaper for web destination than App Install | Lower CPI when funneling web → app |
| Higher trust on web before commitment | Better activation than cold App Store install |
| Email capture before install | Owns the relationship; resurrects churn |
The Three Web-to-App Patterns
Pattern A: Web → App Install → In-App Paywall
Traditional. Web is just the discovery / brand layer. App Store handles billing.
Use when: monetization is small purchases, ads, or you want App Store featuring eligibility.
Pattern B: Web Onboarding + Web Payment, then App Install
User completes quiz, signs up, pays on the web with Stripe, then installs the app and signs in to the paid account. App is the delivery mechanism.
Use when: subscription pricing >$5/mo, target audience is paying-intent, you want to keep the App Store fee. Used by Cal AI, Rise Sleep, Noom, Zing, Future, hundreds of quiz funnels.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 191 lines · 183 tokens per session scan A ab9c86376143
web-to-app-funnel is a skill published in the GitHub repository Eronred/aso-skills (1,847 stars, last pushed 20d ago), licensed MIT. It adds 183 tokens to every session and 2,066 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
asc-app-create-ui
Create an App Store Connect app via iris API using web session from Blitz.
gingiris-aso-growth
A broad guide to growing mobile apps through App Store Optimization, launch planning, creator-made content, and marketing on platforms such as TikTok, Instagram, and YouTube Shorts.
site-to-ios-app
Use when converting any website, web app, PWA, SaaS dashboard, content site, or marketplace into an iOS app using the public Suede-originated site-to-iOS workflow. Covers URL audit, App Store 4.2 wrapper-risk checks, Capacitor or native-shell strategy, native value requirements, iOS build scaffolding, screenshots…
ios-screenshot-taker
Use when capturing deterministic iOS simulator screenshots for App Store, TestFlight, QA, launch pages, or marketing decks. Covers xcodebuild build, simulator boot/install/launch, seeded demo states, xcrun simctl screenshots, required App Store device classes, public-safe output handling, and slash commands such as…
google-play
A Google Play Store API alternative on fetcher.sh — pay-per-call in USDC via x402, or prepaid credits with a Bearer key, no Google Play Console access. Use when the user wants to search Android apps by keyword with price (free/paid) and country storefront filters, fetch an app's full details, reviews sorted by…
ios-app-factory
Use when planning, creating, or orchestrating a complete iOS app-development workflow from idea or keyword to ship gate. Covers keyword-first product selection, native SwiftUI scaffolding, monetization, screenshots, ASO metadata, legal/compliance, grading, release handoff, and slash-command orchestration such as…