
Download Page Generator
Structure a download or get-the-app page that routes users to App Store, Play Store, or direct installers with trust signals and platform clarity.
Overview
Download Page Generator is an agent skill for the Launch phase that creates, optimizes, or audits download pages for desktop and mobile app installs.
Install
npx skills add https://github.com/kostja94/marketing-skills --skill download-page-generatorWhat is this skill?
- Covers desktop (Windows, macOS, Linux) and mobile (iOS, Android) distribution models
- Initial assessment for app type, traffic source, and store-only vs direct download
- Page goals framed as download, trust, and conversion with security and privacy signals
- Reads project-context for product, audience, and value proposition when available
- Points to app-ads skill for paid install campaigns instead of page structure
- 3 stated page purposes: download, trust, and conversion
Adoption & trust: 733 installs on skills.sh; 586 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Visitors land ready to install but bounce because platforms, store links, and trust proof are buried or confusing.
Who is it for?
Indie devs launching a desktop client, mobile app, or cross-platform product with mixed store and direct distribution.
Skip if: Paid user-acquisition creative and campaign setup—use app-ads when the ask is install ads, not the landing page.
When should I use this skill?
User wants to create, optimize, or audit a download page for desktop or mobile app; or mentions download page, app download, desktop download, mobile app download, App Store, Play Store, get the app, install app, or down
What do I get? / Deliverables
You get a download-page structure that surfaces the right store or binary per platform, builds pre-install trust, and sharpens conversion CTAs.
- Download page section plan
- Platform and store link placement guidance
- Trust and conversion optimization notes
Recommended Skills
Journey fit
Download pages sit at the moment users choose to install—core Launch work for desktop and mobile distribution. ASO subphase covers app-store and install paths, store badges, and conversion on download intent traffic.
How it compares
Focused on owned download landing pages, not full website IA or careers hiring pages.
Common Questions / FAQ
Who is download-page-generator for?
Solo builders and small teams shipping apps or desktop tools who need an install page that works for both store listings and direct downloads.
When should I use download-page-generator?
Use it at Launch when you add a /download route, refresh store badges, or audit install conversion; also when you mention download page, App Store, Play Store, get the app, or install app CTAs.
Is download-page-generator safe to install?
It provides marketing structure guidance only; check the Security Audits panel on this Prism page before installing.
Workflow Chain
Then invoke: app ads
SKILL.md
READMESKILL.md - Download Page Generator
# Pages: Download Page Guides download page structure and optimization for desktop and mobile app downloads. Purpose: convert visitors into installers by clearly presenting value, platform options, and trust signals. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Initial Assessment **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product, audience, and value proposition. Identify: 1. **App type**: Desktop (Windows, macOS, Linux) or mobile (iOS, Android, both) 2. **Traffic source**: Organic, paid, email, referral 3. **Distribution**: App Store / Play Store only, direct download, or both ## Page Purpose | Purpose | Goal | |---------|------| | **Download** | Guide users to install desktop or mobile app | | **Trust** | Build confidence before download (security, privacy, reviews) | | **Conversion** | Maximize download rate, store visits, install conversion | ## Download Page Structure | Step | Purpose | Elements | |------|---------|----------| | **1. Value proposition** | Why download | Headline, benefit-focused copy, key features | | **2. Platform selection** | Clear path | Desktop: OS detection or manual pick; Mobile: App Store / Play Store buttons | | **3. Trust signals** | Reduce friction | Ratings, download count, security badges, privacy note | | **4. Visual proof** | Show the app | Screenshots, app previews, video | | **5. CTA** | Primary action | Single, prominent download button | ## Platform-Specific Layout ### Desktop App - **OS detection**: Auto-detect OS or show "Download for Windows / macOS / Linux" - **Direct download**: One-click .exe / .dmg / .deb etc. - **Alternatives**: Optional "Other platforms" or "Command line" for power users ### Mobile App - **Dual store**: App Store + Play Store buttons side by side - **Smart redirect**: Detect device and show relevant store first; still show both - **QR code**: Optional for desktop visitors to scan and install on phone ## Optimization Best Practices ### Performance - **Load time**: Under 3 seconds; each extra second can cost ~7% conversion - **Mobile-first**: Most app download traffic is mobile; responsive, thumb-reachable CTAs - **Image optimization**: WebP, lazy loading, compression (e.g. TinyPNG, ImageOptim) ### Conversion - **Single primary CTA**: "Download Free Now," "Get on App Store," "Get for Windows" - **Above the fold**: CTA visible without scrolling - **Repeat CTA**: On longer pages, repeat at logical points - **A/B test**: CTA color, size, copy, placement ### Trust & Social Proof - **Star ratings**: Show App Store / Play Store ratings - **Download count**: "10M+ downloads," "Trusted by X users" - **Testimonials**: User quotes, media logos - **Security**: Security badges if collecting sensitive info ### Content - **Top 3–5 features**: Benefit-focused, scannable bullet points - **Screenshots**: High-quality, show app in action - **Video**: App preview or demo video ### Alignment with Traffic - **Ads**: If from PPC, ensure message matches ad (offer, platform); see **paid-ads-strategy** - **Email**: Match campaign message and CTA ## Output Format - **Headline** and subheadline - **Structure** (5-step flow sections) - **Platform layout** (desktop vs mobile) - **CTA** copy and placement - **Trust signals** placement - **SEO** metadata (if page is indexed) ## Related Skills ### Pages - **landing-pa