ktl-website

Installation
SKILL.md

ktl-website

Lay down a website for the knowledge bundle in the repository this skill is invoked from. It is an Astro Starlight site under website/, built from the bundle and from the repository's README, docs and changelog, with a workflow that publishes it to GitHub Pages. Every file is copied from templates/ (paths below are relative to this skill's directory), never retyped. The site shows a page per concept with the trust label knowledge-report.sh gives it, a health page, a knowledge graph, and search that filters by trust and type. It serves the four files lokf export writes under /knowledge/, so the repository becomes a producer node for the bundle's IRIs.

Model: a small or mid-tier model is enough here: Step 1 copies templates and substitutes placeholders, and Step 0 is structured file lookup. Mistakes are caught by Step 3's grep, Step 4's build and Step 6's hand-off.

Scope

  • This skill runs once, to lay website/ down, or again to repair or update it: copy each template over a copy that is missing or differs. It writes nothing into the bundle, the README, the docs or the changelog.
  • ktl-sidecar runs first: the site builds from the sidecar's scripts and toolkit. ktl-librarian and ktl-curator change what the pages say.

Guardrails: three files are the repository's own once written, and a repair never replaces them: website/site.config.mjs, website/README.md and website/src/styles/custom.css. A website/ that is not this skill's (no site.config.mjs in it) is never written into; stop and ask. Stop too when the sidecar's preflight reports the bundle unhealthy, and send that to ktl-sidecar or ktl-librarian first. Deployment is GitHub Actions and GitHub Pages; elsewhere, references/deploy.md says what the host does itself.

Step 0 - Gather the facts

First, the preflight. Run bash scripts/website-preflight.sh <repo-root> from this skill's directory and read its screen before anything else. It runs the sidecar's own preflight inside it, then checks the report script, the toolkit and its lock, Node.js and npm, and the origin remote and the default branch. It says whether another publisher already holds the repository's Pages, whether website/ exists, and which of the README, docs/, CHANGELOG.md and .assets/ the site can show. Its last line names what is missing and which steps that disables; repeat that line in the Step 6 hand-off. When the person cannot act on a missing or warn line, write them a request note from references/prerequisites.md.

Resolve every placeholder from real sources before writing anything; never leave a <...> token behind.

Installs
9
GitHub Stars
3
First Seen
Oct 15, 2026