<!doctype html>
<html lang="en"><head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width,initial-scale=1">
<title>Skills - NumericalOS</title>
<meta name="description" content="Agentic skills for building NumericalOS targets locally or via Cloudflare.">
<link rel="stylesheet" href="/assets/site.css">
</head><body>
<header><a class="brand" href="/">NumericalOS</a><nav><a href="/">home</a><a href="/docs/">docs</a><a href="/graph/">graph</a><a href="/whitepaper/">whitepaper</a><a href="/principles/">principles</a><a href="/skills/" class="on">skills</a><a href="/browse/">source</a></nav></header>
<main>
<h1>Agentic build skills</h1>
<p class="lead">These skills support <em>you</em> building NumericalOS targets on
your own machine, or via Cloudflare Sandbox + R2 when the host has no local
Linux/WSL. This site does not ship prebuilt OS images as the primary product.</p>
<p>Point your agent at <a href="/AGENTS.md">AGENTS.md</a> for the protocol, or
take the whole bundle: <a href="/skills.zip">skills.zip</a>.</p>
<table class="skills"><thead><tr><th>skill</th><th>when it fires</th></tr></thead>
<tbody><tr><td><a href="/skills/numericalos-algoblocker-enterprise/SKILL.md">numericalos-algoblocker-enterprise</a></td><td>&gt; Export and operate the NumericalOS privacy-workstation profile that is Algoblocker enterprise layer 3 (3+2+1). Use when the user asks to complete Algoblocker workstation support, stamp or validate algoblocker-privacy-posture receipts, merge privacy units into a seed, or wire NumericalOS to algoblocker.com/enterprise. Not an ISO build and not a boot claim.</td></tr><tr><td><a href="/skills/numericalos-build-initramfs/SKILL.md">numericalos-build-initramfs</a></td><td>Build a NumericalOS initramfs (cpio.gz) whose /init is the graph-driven bootstrap. Use when numericalos-target-classifier routed here, or when the user asks for a NumericalOS initramfs, initrd, or the userspace half of bootable media. Assembles graph-resolved numos-floor (tool multi-call binary), the boot chain, and a verified numos.state — prefer profile self-init for offline complete boots.</td></tr><tr><td><a href="/skills/numericalos-build-iso/SKILL.md">numericalos-build-iso</a></td><td>Build NumericalOS bootable media - a hybrid ISO that boots from optical or USB, pairing a kernel with the graph-driven initramfs. Use when numericalos-target-classifier routed here, or when the user asks for a NumericalOS ISO, USB stick, bootable image, or bare-metal media. Builds the initramfs first, then wraps kernel plus initramfs in a BIOS/UEFI-bootable image.</td></tr><tr><td><a href="/skills/numericalos-build-iso-cf/SKILL.md">numericalos-build-iso-cf</a></td><td>&gt; Produce NumericalOS Linux ISO/initramfs artifacts via Cloudflare (Containers Sandbox + R2), not WSL and not a local Linux host. Use when the user asks to build NumericalOS ISO on Cloudflare, avoid WSL, generate boot media without installing Linux locally, or when numericalos-target-classifier routes here because the machine has no local cpio/xorriso/WSL but has Cloudflare access. Triggers: &quot;Cloudflare ISO&quot;, &quot;build ISO without WSL&quot;, &quot;CF Sandbox initramfs&quot;, &quot;R2 ISO artifacts&quot;, &quot;/numericalos-build-iso-cf&quot;. Honesty: Workers alone cannot mkisofs; a Linux container under CF does the pack. Artifact built ≠ boot verified.</td></tr><tr><td><a href="/skills/numericalos-build-oci/SKILL.md">numericalos-build-oci</a></td><td>Build a NumericalOS OCI container image runnable by Docker, Podman, containerd, or nerdctl. Use when numericalos-target-classifier routed here, or when the user asks for a NumericalOS container/Docker/Podman image. Covers the OCI, rootless-Podman, and LXC/system-container differences honestly rather than flattening them, and states plainly what a container can and cannot prove about a boot.</td></tr><tr><td><a href="/skills/numericalos-publish-site/SKILL.md">numericalos-publish-site</a></td><td>&gt; Build and publish the full NumericalOS self-hosted site to numericalos.com (Cloudflare Pages project numericalos, production branch main). Use after any content, docs, skills, or status change that should go live; when the user says &quot;update the site&quot;, &quot;deploy numericalos.com&quot;, &quot;publish pages&quot;, &quot;redeploy site&quot;, &quot;sync the website&quot;, or after finishing a NumericalOS docs/status cycle without a git remote. Triggers: &quot;/numericalos-publish-site&quot;, &quot;publish site&quot;, &quot;update numericalos.com&quot;, &quot;deploy Pages&quot;, &quot;site is stale&quot;. This is the site publish path — not ISO build and not boot verification.</td></tr><tr><td><a href="/skills/numericalos-target-classifier/SKILL.md">numericalos-target-classifier</a></td><td>Use FIRST, before any NumericalOS build skill, to decide which target the user&#x27;s machine can actually produce - OCI container image, initramfs, hybrid ISO/USB, Cloudflare remote ISO (no WSL), or nothing buildable here. Triggers - &quot;build NumericalOS&quot;, &quot;make a NumericalOS image&quot;, &quot;boot NumericalOS&quot;, &quot;which NumericalOS target&quot;, &quot;NumericalOS on my machine&quot;, &quot;ISO without WSL&quot;, &quot;Cloudflare ISO&quot;, or any request to produce NumericalOS bootable media or a container image. Probes the real toolchain rather than assuming, and routes to exactly one build skill.</td></tr><tr><td><a href="/skills/numericalos-verify-boot/SKILL.md">numericalos-verify-boot</a></td><td>Boot a NumericalOS artifact under QEMU and report what actually happened. Use after any NumericalOS build skill, or when the user asks to verify, test, smoke-test, or prove a NumericalOS image boots. This is the ONLY skill in the family permitted to make a boot claim, and only about the exact artifact and architecture it observed. Closes the verification gate the NumericalOS repository itself cannot close.</td></tr></tbody></table>
<h2>The honesty contract</h2>
<p>Only <code>numericalos-verify-boot</code> may claim a boot, and only for the
artifact and architecture it observed. Build skills produce artifacts and say
exactly that. A prior QEMU observation on x86_64 does not generalize to other
arches, metal, or a new ISO you just built &mdash; re-run verify-boot.</p>
</main>
<footer>
<p>NumericalOS &mdash; a Linux userspace whose init is a graph.
<strong>Status: bootstrap logic tested; x86_64 QEMU self-init PASS (degraded=0) on kernel+initrd and hybrid ISO/GRUB serial; fleet bare-QEMU PASS-degraded; metal and non-x86_64 unverified.</strong></p>
<p><a href="/LICENSE">MIT</a> &middot;
<a href="/numericalos.git">git</a> &middot;
<a href="/llms.txt">llms.txt</a> &middot;
<a href="/AGENTS.md">AGENTS.md</a> &middot;
<a href="/index.json">index.json</a> &middot;
<a href="/skills.zip">skills.zip</a></p>
</footer>
</body></html>
