Docs written by agents

Alec Reynolds, co-founder of SaturnDocs, on documentation whose readers are now mostly agents: llms.txt, MCP, authenticated docs and skills.

Alec Reynolds, Co-founder, SaturnDocs · with Luca Berton

Not filmed yet.

Alec Reynolds is co-founder of SaturnDocs, with Sean Knight. He created Lando, a local development environment used by more than 50,000 developers.

Follow the show and the episode arrives the morning it's published.

In brief

Most readers of modern technical and customer-facing documentation are now agents, and they often evaluate a product through its docs.
If an agent cannot find the docs and complete its first task with them, it will not recommend the product.
A copy-this-prompt button or a chat bot is still a feature built for people.
SaturnDocs starts with agent-ready surfaces: llms.txt, a good MCP server, and authenticated MCP and docs where content must not be scraped.
Those surfaces are table stakes, like old-school SEO; the work is shortening an agent's time to first task.
Platforms such as Mintlify, Docusaurus, GitBook and Read the Docs came of age around 2020, built for human editors and readers.
Skills help agents get started, but agent harnesses guard against prompt injection, so they must be offered in a way agents trust.
SaturnDocs is early and works with pilot customers; the name comes from co-founder Sean Knight's time at NASA's Jet Propulsion Laboratory.

Chapters

0:00 Docs written by agents, for agents
1:23 Agent surfaces: llms.txt and MCP
1:53 Beyond Mintlify, GitBook and Docusaurus
2:53 From discoverability to first task
3:35 Skills without prompt injection
4:09 Pilots, and why Saturn

Why this conversation

Documentation used to be written for people who read it. At Cloudflare Connect 2026 in San Francisco, Alec Reynolds explained why its main readers are now agents, what that asks of a docs site, from llms.txt and MCP to skills, and why platforms built around 2020 struggle with it. The written version is SaturnDocs: documentation written for agents.