Build, check, publish, and depend on a catalog of fraglet tools -- compile packs into skills, validate the result, render its website, and vendor pinned tools into another repository.
Compile a catalog of level-0 tools -- a tarball of pack directories, each an index.md plus fraglet files -- into its projections: one Agent Skill per pack (SKILL.md beside byte-identical copies of the tools), a Claude Code plugin per pack with a marketplace.json, llms.txt and llms-full.txt for agents arriving over HTTP, manifest.json with every tool's contract and procedure_hash, and an Open Knowledge Format bundle. Everything is derived from the tools' own headers and the pack index files; nothing is authored twice.
Render a compiled tools catalog (archived) into a static website: the catalog itself served verbatim -- llms.txt, manifest.json, every pack's SKILL.md and every tool file at the same paths -- plus an HTML layer over it: an explorer of every tool with search, tag and pack filters, grid and table views and a dark/light theme; one page per pack; one page per tool with its contract, provenance, a curl one-liner and its full source. Relative links throughout, so the result works from a file:// URL as well as a web root.
Validate a compiled tools catalog (archived): every pack's SKILL.md against the agentskills.io specification using skills-ref, the spec's own reference validator; every tool file present, executable, and hashing to the procedure_hash manifest.json records for it; every llms.txt link resolving; marketplace.json plugins matching the pack directories; and, if an okf/ bundle is present, every concept typed and every relative link resolving. Prints one line per finding and a summary; exit 0 only when clean.
Fetch the catalog tools a project depends on, verify each against its pinned procedure_hash, and pack them into vendor.tar.gz (executable, at their catalog paths, reproducible bytes). The lock file names where the tools are published ("source https://tools.ofthemachine.com") and lists one "<pack>/<stem>.<ext> sha256:<hex>" per line (# comments allowed); the hashes are what manifest.json and every receipt call procedure_hash. A file whose hash does not match is refused and nothing is written, so base_url may fetch from anywhere -- a mirror, or a local `make serve` -- without weakening the pin or changing the recorded source.