landing-page-generator

Generate deploy-ready landing pages from repository README and structure.

5.7k|744|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/FlorianBruniaux/claude-code-ultimate-guide --skill landing-page-generator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: landing-page-generator
Source: https://github.com/FlorianBruniaux/claude-code-ultimate-guide/tree/main/examples/skills/landing-page-generator
Command: npx skills add https://github.com/FlorianBruniaux/claude-code-ultimate-guide --skill landing-page-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Generating consistent, deploy-ready landing pages for any repository by automatically extracting content from documentation and structure.

Core Features & Use Cases

  • Analyze README, CHANGELOG, docs, and assets to extract title, tagline, features, and install instructions for landing pages.
  • Map content to a standardized landing layout (Hero, Features, Install, FAQ) and generate static HTML + CSS + JS with a GitHub Pages deployment workflow.
  • Ideal for open-source showcases, documentation portals, and marketing-ready project landing pages across multiple repositories.

Quick Start

Run the landing-page-generator from a local repository path to output a ready-to-deploy landing site.

Frequently Asked Questions about landing-page-generator

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

FAQPage Schema
How do I generate a landing page from a GitHub repository automatically?

To generate a landing page from a GitHub repository, this Skill analyzes your README, CHANGELOG, and directory structure to extract features and install instructions, then outputs static HTML, CSS, and a GitHub Pages deployment workflow.

Can I standardize landing pages across multiple open-source projects?

Yes, you can standardize landing pages across multiple open-source projects by extracting repository content and mapping it to a standardized layout featuring Hero, Features, Install, and FAQ sections.

What is the best way to create a static site for a documentation portal?

The best way to create a static site for a documentation portal is to auto-generate deploy-ready landing pages directly from your repository files, ensuring consistent project showcases without manual HTML coding.

Does the landing page generator include a GitHub Pages deployment workflow?

Yes, the landing page generator includes a GitHub Pages deployment workflow, producing an index.html, styles.css, and optional assets directory alongside the necessary deployment configuration.

Do I need to manually write HTML and CSS for my repo landing page?

No, you do not need to manually write HTML and CSS for your repo landing page, as the tool parses your documentation and repo structure to produce complete, deploy-ready static site files automatically.