Create GitHub Pages Site

Turn "put this on GitHub Pages" into a correct, building, auto-deploying repo. The hard part of GitHub Pages isn't the HTML — it's the deploy plumbing and the base-path trap. This skill owns both: it stamps a vetted template, sets the base path for the exact repo, ships the current official Pages workflow, and walks the user through enabling Pages.

It also never stops at the template's demo content. A stamped template is a skeleton, not the deliverable — the skill reads the target repo and authors a site about that project: real name and pitch, the right kind of reference (CLI, library, app, or catalog), real install/usage pulled from the repo, and labeled image placeholders the user can drop real art into. Shipping a site that still says "Hello, Astro" for someone's CLI is a failure, even if it deploys.

When to use which template

Pick by what the user is building. If unsure, ask one question (content vs. app) and default to static-html for the simplest ask.