TVL AI Skills

Build Free Website Skill

tvl-build-free-website takes a site from brief to a live, free URL. It builds a static site, publishes it on GitHub Pages, and verifies the deployed page actually returns HTTP 200 with the right title, styles and navigation — the whole lifecycle, not just the build.

The workflow Install the skill
What it builds

Static sites that run on GitHub Pages

Anything that can be served as plain files. If it needs a server, it is out of scope on purpose.

One-page site

A compact company, service, event or campaign page with a clear offer, proof and contact path.

Portfolio & landing pages

A professional profile with projects, case studies, credibility signals and contact links.

Documentation site

A public project or resource site with quick start, guides, examples and reference links.

Project pages

A home for an open-source project or product — overview, status and links.

Resource hubs

A curated index of links, downloads and references around a single topic.

Lightweight apps

Client-side-only tools and demos that run entirely in the browser.

How it works

The ten-step workflow

From reading your content to handing back a verified live URL — every step is explicit, and it does not stop at "pushed to GitHub".

1

Content assessment

Examine your files, URLs and the current repository state.

2

Constraint identification

Classify the site type, deployment model (root, /docs, Actions) and ownership (user vs organization).

3

Reference loading

Consult the GitHub Pages rubric and the site blueprints.

4

Blueprint selection

Choose the right template for a new or redesigned site.

5

Build

Use plain HTML/CSS/JS or an existing static generator — no backend dependencies.

6

Deployment config

Pick branch deploy or GitHub Actions; add .nojekyll when needed.

7

Local verification

Serve locally and verify HTTP status and content rendering before publishing.

8

Publication

Create or reuse the repository, push to main and configure GitHub Pages.

9

Live URL verification

Confirm HTTP 200, title/H1, asset loading and navigation on the deployed URL.

10

Closeout

Deliver the final URL, repo link, deployment method, test results and limits.

Deployment

GitHub Pages modes

The skill picks the deployment model that fits the repository, then wires it up.

Branch · main root

Serve the site directly from the root of the main branch. Simplest for hand-written sites.

Branch · /docs

Serve from the /docs subdirectory of main, keeping source and site side by side.

GitHub Actions

A workflow builds the static output and deploys the artifact — for static generators.

.nojekyll

When static assets should bypass Jekyll processing (for example folders that start with an underscore), the skill adds a .nojekyll file so the files are served as-is.

The checks

Nothing ships unverified

Two gates: everything that must be true before publishing, and everything confirmed on the live URL after.

Pre-publish

  • Content is static only — HTML, CSS, JS, images, generated assets.
  • index.html is present at the publishing root.
  • Asset paths work from the deployed URL, including project-subpath cases.
  • No broken local navigation links.
  • Meaningful title, H1, meta description and social preview tags.
  • Accessibility: landmarks, labels, alt text, keyboard nav, focus, contrast.
  • Responsive on mobile and desktop; asset sizes optimized.
  • No secrets, tokens, keys or local-only paths committed.

Live-URL verification

  • The URL returns HTTP 200.
  • The expected title and H1 are visible.
  • CSS styling loads correctly.
  • Images render properly.
  • Internal navigation works.
  • The URL matches the selected GitHub Pages deployment mode.
Output

What it hands back

For a build-and-publish request, a fixed closeout — for planning-only requests, a concise build plan and blueprint name.

LIVE SITE: <url> REPOSITORY: <url> WHAT CHANGED: [bulleted list] DEPLOYMENT: GitHub Pages mode and source VERIFICATION: local, Actions/Pages, live URL results LIMITS: applicable constraints
Scope

What it will not do

GitHub Pages is a static host. The skill refuses anything that needs a server, on purpose.

No backend

No databases, server-side code, scheduled jobs or private APIs.

No secrets

No runtime secrets, auth or environment-dependent configuration.

No dynamic data

No payment processing, private data storage or user-submitted content systems.

Service limits

GitHub Pages enforces size, bandwidth and build-time limits. The skill states them at closeout so there are no surprises later.

Under the hood

What ships with the skill

references/github-pages-rubric.md

GitHub Pages guidelines and best practices the skill audits against.

references/site-blueprints.md

Templates for the common site architectures above.

Philosophy

Reach for the simplest durable static stack, reusing tools already in the repository when possible.

Install and run

Add the website builder skill

Use the public TVL Skills repository with the Agent Skills CLI.

Install only this skill

$ npx skills add danlex/tvl-skills --skill tvl-build-free-website

Install all TVL skills

$ npx skills add danlex/tvl-skills

Ask Claude Code to install it

Install the skill tvl-build-free-website from danlex/tvl-skills into Claude Code, then list the installed skills to confirm it is available.

Build and publish a one-page site

Use $tvl-build-free-website to build a one-page service website for this offer and publish it for free with GitHub Pages. Verify the live URL returns 200 with the right title and styles.

Deploy a docs site from /docs

Use $tvl-build-free-website to publish this documentation from the /docs folder on main, add .nojekyll if needed, and confirm the live navigation works.

Plan only

Use $tvl-build-free-website to give me a build plan and blueprint for a portfolio site, without building it yet.