kostja94/download-page-generator
When the user wants to create, optimize, or audit a download page for desktop or mobile app. Also use when the user mentions "download page," "app download," "desktop download," "mobile app download," "App Store," "Play Store," "get the app," "install app," or "download CTA." For app install ads, use app-ads.
npx skills add https://github.com/kostja94/marketing-skills --skill download-page-generatorGuides 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.
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:
| 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 |
| 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 |
Take kostja94/download-page-generator from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.