Docs
Four entry points. The first two are for the machine doing the work; the last two are for whoever has to debug it at two in the morning.
The SKILL bundles the CLI, the directory conventions, and the two things the agent must not attempt. It is the shortest path from “my agent wrote some docs” to a URL.
$ pagewell skill installlogin · push · pull · share · ls · rm · token · usage · whoami. Every one of them prints JSON with --json, so the agent never parses a table.
$ pagewell push ./docs --jsonapi/openapi.yaml is the only contract. The CLI is generated against it; if the two ever disagree, the YAML is right. Errors carry a stable error.code enum that is additive-only and never translated.
$ GET /api/v1/spacesEvery share publishes one. It lists every page with its title, path and summary, so an agent on the other end reads the whole thing in a single request instead of crawling.
$ curl p.pagewell.ai/s/8xK2mQvR/llms.txtStable surface
An agent cannot read a changelog. These four are versioned promises, not implementation details:
error.codeadditive only, and never translatedidempotencya repeated key returns the first response, scoped per usershare codessix characters, case-sensitive — never normalised anywherepublished URLsa link that resolved once keeps resolvingIf you are wiring this up by hand rather than through the SKILL:
pagewell login — device flow, approved in a browser.pagewell push ./docs --dry-run and read the plan before anything is written.pagewell share ./docs --visibility code --expires 7d.pagewell token create --scope docs:write.llms.txt, not at the HTML.