skillboardUpdated every 6 hours
skillboardWhen 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.
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.
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 |
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/download · pinned to the source commit
git clone https://github.com/kostja94/marketing-skills.git
cd marketing-skills
git checkout 70987bad4ebe9dce1f74858c1c64f3f8810f18e4
mkdir -p ".claude/skills/download"
cp -r "skills/pages/marketing/download" ".claude/skills/download"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit 70987bad4ebe. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.