download-page-generator

kostja94/marketing-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/kostja94/marketing-skills --skill download-page-generator
0 commentsdiscussion
summary

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.

skill.md

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-page-generator: Download page is a type of landing page; apply LP principles
  • homepage-generator: Homepage often links to download page
  • features-page-generator: Feature copy for "Explain value" section

Components

  • hero-generator: Hero section (value proposition)
  • cta-generator: Download button design
  • trust-badges-generator: Social proof, ratings
  • testimonials-generator: User testimonials

SEO

  • title-tag, meta-description, page-metadata: Download page metadata
how to use download-page-generator

How to use download-page-generator on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add download-page-generator
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/kostja94/marketing-skills --skill download-page-generator

The skills CLI fetches download-page-generator from GitHub repository kostja94/marketing-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/download-page-generator

Reload or restart Cursor to activate download-page-generator. Access the skill through slash commands (e.g., /download-page-generator) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.451 reviews
  • Mia Robinson· Dec 24, 2024

    download-page-generator has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Chinedu Agarwal· Dec 20, 2024

    Registry listing for download-page-generator matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Naina Srinivasan· Dec 12, 2024

    Useful defaults in download-page-generator — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Aisha White· Nov 19, 2024

    Useful defaults in download-page-generator — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Henry Bansal· Nov 15, 2024

    Solid pick for teams standardizing on skills: download-page-generator is focused, and the summary matches what you get after install.

  • Rahul Santra· Nov 7, 2024

    Useful defaults in download-page-generator — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Pratham Ware· Oct 26, 2024

    Registry listing for download-page-generator matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Ava Jain· Oct 10, 2024

    Registry listing for download-page-generator matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Mia Taylor· Oct 6, 2024

    I recommend download-page-generator for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Diego Tandon· Sep 17, 2024

    I recommend download-page-generator for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

showing 1-10 of 51

1 / 6