How do I install the Docs Reading skill?

Run npx skillmds@latest add theseus-run/docs-reading in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Docs Reading safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Docs Reading?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Docs Reading free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Docs Reading?

theseus-run (@theseus-run) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Docs Reading by theseus-run — Agent Skill

Name: Docs Reading
Author: theseus-run

File contents

Theseus Docs Reading

Use this skill before code changes when docs may contain the boundary contract. The goal is to read the right docs without treating drafts or brainstorms as implemented truth.

Read Order

Always start with:

docs/README.md
docs/maps/coding-agent-reading-map.md
the section README for the package or concept you are touching
the nearest current concept note in direction, primitives, runtime, or clients

Then read source code and tests. Docs guide what to inspect; code proves what exists.

Status Semantics

direction, primitives, runtime, clients: current doctrine or current implementation notes.
drafts: proposals, research, or POCs. Useful context, not authority.
brainstorms: speculative ideas. Never implementation authority.
archive: superseded history. Read only to avoid reintroducing old paths.
design-notes: adopted or active rationale. Use to understand why a current concept exists, then verify against current code.

If a draft conflicts with current docs or code, current docs/code win. Mention the conflict if it affects the task.

Package Pointers

Core primitives: docs/primitives/primitives.md, plus the specific note such as tool.md or agent-comm.md.
Runtime: docs/runtime/architecture.md, docs/runtime/mission-system.md, docs/runtime/isolation.md, docs/maps/runtime-truth-map.md, and docs/maps/not-real-yet.md.
Server: read runtime docs first, then server package code; server is a host adapter, not runtime owner.
Client/operator surfaces: docs/clients/README.md and runtime command, control, query contracts.
Design changes: also read docs/design-notes/self-editable-harness.md and relevant drafts only if the task is exploring new direction.

Coding-Agent Rules

Verify before asserting a doc is current.
Do not implement from drafts, brainstorms, or archive unless the user explicitly asks to promote that design.
When code and active docs disagree, report the mismatch and update docs if the task includes docs maintenance.
Do not import archived crew, lock-session, queue RuntimeBus, or plugin-host architecture into current runtime work.
Link docs with relative Markdown links when editing docs.

---name: docs-readingdescription: Use before coding or reviewing Theseus runtime, primitive, server, client, or architecture changes when docs may define the intended boundary, status, or domain vocabulary.---# Theseus Docs ReadingUse this skill before code changes when docs may contain the boundary contract.The goal is to read the right docs without treating drafts or brainstorms asimplemented truth.## Read OrderAlways start with:1. `docs/README.md`2. `docs/maps/coding-agent-reading-map.md`3. the section README for the package or concept you are touching4. the nearest current concept note in `direction`, `primitives`, `runtime`, or `clients`Then read source code and tests. Docs guide what to inspect; code proves whatexists.## Status Semantics- `direction`, `primitives`, `runtime`, `clients`: current doctrine or current implementation notes.- `drafts`: proposals, research, or POCs. Useful context, not authority.- `brainstorms`: speculative ideas. Never implementation authority.- `archive`: superseded history. Read only to avoid reintroducing old paths.- `design-notes`: adopted or active rationale. Use to understand why a current concept exists, then verify against current code.If a draft conflicts with current docs or code, current docs/code win. Mentionthe conflict if it affects the task.## Package Pointers- Core primitives: `docs/primitives/primitives.md`, plus the specific note such as `tool.md` or `agent-comm.md`.- Runtime: `docs/runtime/architecture.md`, `docs/runtime/mission-system.md`, `docs/runtime/isolation.md`, `docs/maps/runtime-truth-map.md`, and `docs/maps/not-real-yet.md`.- Server: read runtime docs first, then server package code; server is a host adapter, not runtime owner.- Client/operator surfaces: `docs/clients/README.md` and runtime command, control, query contracts.- Design changes: also read `docs/design-notes/self-editable-harness.md` and relevant drafts only if the task is exploring new direction.## Coding-Agent Rules- Verify before asserting a doc is current.- Do not implement from `drafts`, `brainstorms`, or `archive` unless the user explicitly asks to promote that design.- When code and active docs disagree, report the mismatch and update docs if the task includes docs maintenance.- Do not import archived crew, lock-session, queue RuntimeBus, or plugin-host architecture into current runtime work.- Link docs with relative Markdown links when editing docs.

Frequently asked questions

Docs Reading