Shared by Luke

A small public shelf for the instruction sets I use with coding agents: how I run a site build, how I design a brand, and whatever else earns a stable procedure. They live here as plain files with no runtime dependency, because a skill that needs a framework to install is a skill nobody installs.

Why install-by-prompt

Skills are directories, not single documents — a SKILL.md plus the references and scripts it cites. Handing someone a markdown block plus a file tree to recreate is how bundles arrive half-installed. So each skill publishes a manifest with paths, modes, and sha256 hashes, and the prompt just points the agent at it. Update the skill, and every prompt already pasted into some other conversation still fetches the current version.

Versioning

The bundle hash on a skill page is the sha256 of its file list, modes, and contents. If two people quote different hashes, they are not running the same bundle. The copies served here are mirrored from my local skills directory by a script, and a check fails the build when the mirror drifts from the source.

What is not here

No accounts, no telemetry, no comments. Everything on the site is a static file, and every download is the same bytes the manifest describes.