KnowledgeBase

KnowledgeBase is the documentation building — a single Librarian agent who keeps your project’s docs organized, indexed, and easy to write into.

At a glance

• Default agents: Librarian
• Best for: Organizing a docs folder, indexing existing documents, and drafting user-facing documentation
• Skills it ships with: No KnowledgeBase-specific slash commands — the Librarian uses general-purpose tools (file system access, the Markdown Editor) and any skills you enable at the project or user level
• Place from: Building Type Drawer → KnowledgeBase

How It Works

The Librarian treats your project’s folder_path as a library. They scan whatever documents already exist (Markdown, plain text, READMEs in subdirectories), build a mental index of what’s there, and help you keep that collection coherent as it grows.

You talk to the Librarian the same way you talk to any agent. The difference is what they’re good at: rather than implementing features or running research, the Librarian is set up to read across many files, suggest a structure, fill in gaps, and write new pages that match the tone of what’s already there. When you ask “where should this go?” the Librarian has a real answer because they’ve read the surrounding material.

KnowledgeBase works equally well for product documentation (a docs/ folder you ship to users), internal knowledge (architecture notes, decision logs), or research outputs (the artifact folder from a MarketResearchers project). It is not specific to any docs framework — the Librarian writes plain Markdown.

Default agents

• Librarian. The Librarian is the docs caretaker. Talk to the Librarian when you want a docs folder organized into sections, when you have a pile of notes that need to become a coherent document, when you need a new page written in the style of existing ones, or when you want to find out where something is already documented before writing it again. The Librarian reads broadly before writing, which makes them slower than a freeform writer but much better at consistency.

Configuration

KnowledgeBase is a simple building. From its Building Window you can:

• Override the Librarian’s prompt — give them a specific style guide, a target audience, or rules about file naming and structure.
• Change the Librarian’s model. A long-context model is often a better fit because the Librarian regularly reads many files at once.
• Add additional directories if the docs you want managed live outside the project’s folder_path (for example, a separate wiki/ repo).
• Add skills and MCP servers at the building or agent level. Useful additions include the filesystem MCP server (for tighter file ops) or the linear MCP server (if you cross-reference issues from your docs).

Typical workflow

1. Place KnowledgeBase in your project’s territory and open it.
2. Send the Librarian an opening message describing what you want done — for example, “Walk through docs/ and tell me what’s there, what’s missing, and what’s stale.”
3. Read the Librarian’s index. If you don’t like the structure, say so; the Librarian will propose a new one and (with your go-ahead) reorganize files.
4. Ask for a specific document to be drafted, revised, or split. The Librarian writes into Markdown files in your project folder.
5. Open the result in the Markdown Editor from the Toolbox to read, tweak, and save.

Limitations

• The Librarian writes Markdown, not framework-specific docs. If your site uses MDX, Astro components, or a docs framework with custom directives, you’ll usually want to make a pass over the output yourself or extend the Librarian’s prompt with the framework’s conventions.
• KnowledgeBase has one agent. There’s no built-in reviewer for the Librarian’s drafts. If you want a review loop on docs, point a LoopReview building at the docs folder or hand drafts to a Reviewer in CodeForge.
• The Librarian works from what’s in the project folder. They can read related code, but they don’t have privileged access to anything off-disk (private wikis, external knowledge bases) unless you wire that in via MCP.
• Reorganizing files moves them on disk. Run the Librarian against a folder you’ve committed first, or be prepared to undo from version control.

Related

• Buildings & Agents — the building/agent model in general.
• Toolbox — the Markdown Editor you’ll use to read and tweak the Librarian’s output.
• CodeForge — pair when you want a Reviewer pass on technical documentation.