landing-page-generator

Generate deploy-ready static HTML/CSS/JS landing pages from repository README, docs, and assets.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Alamator/code-ultimate --skill landing-page-generator-alamator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: landing-page-generator
Source: https://github.com/Alamator/code-ultimate/tree/main/examples/skills/landing-page-generator
Command: npx skills add https://github.com/Alamator/code-ultimate --skill landing-page-generator-alamator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Generating polished, deployable landing pages from project repositories is time consuming and error prone when done manually; this skill automates extraction of README content, docs, assets and metadata to produce a consistent marketing-style site without hand-coding each section.

Core Features & Use Cases

  • Analyze repository sources (README, CHANGELOG, package.json/VERSION, docs/, assets/) to extract title, tagline, features, install steps, and screenshots.
  • Map extracted content into standard landing sections (Hero, Features, Quick Start, FAQ, Screenshots, Footer) and generate a responsive HTML/CSS/JS site with search and accessibility considerations.
  • Produce deploy-ready output including copied assets and a GitHub Actions workflow configured for GitHub Pages, with optional risk banner and pricing table features.
  • Use cases: convert an open-source README into a project homepage, standardize landing pages across many repos, or build marketing pages for library/tool releases.

Quick Start

Use the landing-page-generator on a local repository path to produce a deploy-ready site and include flags like --risk-banner or --pricing-table to enable optional sections.

Frequently Asked Questions about landing-page-generator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a README into a deploy-ready landing page for GitHub Pages?

To convert a README into a deploy-ready landing page, this tool extracts repository metadata, docs, and assets to generate a static HTML/CSS/JS site bundled with a configured GitHub Actions workflow for direct GitHub Pages deployment.

What is the best way to generate a static site from an open-source repository?

Generating a static site from an open-source repository involves extracting README content, package.json metadata, and assets, then mapping them into standardized landing sections like Hero, Features, and Quick Start for a responsive marketing homepage.

Can I add a pricing table or risk banner to a generated project homepage?

Yes, you can add a pricing table or risk banner to a generated project homepage by using optional flags during generation, allowing you to customize the static site output for specific marketing or library release contexts.

Does the generated static site include search indexing and accessibility checks?

The generated static site includes built-in search indexing and accessibility considerations, ensuring the extracted repository content produces a responsive, compliant marketing page without requiring manual frontend auditing.

What repository sources are needed to map content into standard landing sections?

Mapping content into standard landing sections requires repository sources like README, CHANGELOG, package.json, docs directories, and asset folders to accurately extract titles, features, and installation steps for the landing page.

Are there limitations when standardizing landing pages across many repos?

Standardizing landing pages across many repos relies on the presence of specific repository files like README, docs, or package.json; repositories lacking these structured metadata sources may not produce a complete static site output.