Documentation logo

Documentation

OrganizationPopular
agent0ai
Documentation

Read the supplemental project documentation module

Overview

Publisheragent0ai
Repositoryspace-agent
Skill nameDocumentation
Stars
1.4K
Forks
323
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by agent0ai on GitHub. Read the source before you install it.

Installation

Install the Documentation AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/agent0ai/space-agent.git /tmp/space-agent
mkdir -p .claude/skills
cp -r /tmp/space-agent/app/L0/_all/mod/_core/documentation/ext/skills/documentation .claude/skills/Documentation
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Documentation in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Documentation on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Documentation is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Use this skill when you need project orientation before editing or answering architecture questions.

helper

  • Import /mod/_core/documentation/documentation.js
  • read("path/to/file.md") reads a nested markdown doc relative to docs/
  • url("path/to/file.md") builds the resolved /mod/... URL for a doc file

workflow

  • Start with the built-in documentation index below unless you already know the exact doc path
  • Use one focused read("path/to/file.md") call instead of loading many large docs blindly
  • Treat /README.md as the public product source of truth for the project pitch, quick starts, release links, community links, and DeepWiki discovery
  • After orientation, walk the DOX chain from /AGENTS.md to the owning AGENTS.md file and then inspect code when needed
  • For visual or modal work, confirm app/L0/_all/mod/_core/visual/AGENTS.md before changing dialog shells, buttons, cards, popovers, or other shared UI primitives
  • For dashboard panel creation, panel manifests, or panel-navigation helpers, start with app/modules-and-extensions.md
  • Keep the repo's frontend-first rule in mind while reading: backend docs explain constraints and existing contracts, not default permission to edit server/
  • If the change appears to require backend work and the user did not explicitly ask for backend edits, ask for permission and explain the security, integrity, or stability reason before changing backend files
  • When you change a stable contract or workflow, update the relevant DOX AGENTS.md files, including affected Child DOX Index entries, and the matching docs in /mod/_core/documentation/docs/
  • When you add, remove, rename, or substantially repurpose a doc file, update this skill's in-file index in the same session

recommended starting points

  • overall system shape: architecture/overview.md
  • desktop host or packaging flow: architecture/desktop-host-and-packaging.md
  • documentation rules: architecture/documentation-system.md
  • frontend runtime and layers: app/runtime-and-layers.md
  • admin agent runtime: app/admin-agent-runtime.md
  • modules, routing, extensions, or dashboard panels: app/modules-and-extensions.md
  • browser-side Hugging Face testing: app/huggingface-browser-runtime.md
  • browser-side WebLLM testing: app/webllm-browser-runtime.md
  • spaces and widgets: app/spaces-and-widgets.md
  • overlay agent runtime: agent/onscreen-agent-runtime.md
  • memory or promptinclude-backed agent memory: agent/memory-and-prompt-includes.md
  • prompt or execution protocol: agent/prompt-and-execution.md
  • skills or this documentation surface: agent/skills-and-documentation.md
  • server routing or pages: server/request-flow-and-pages.md
  • server jobs or maintenance loops: server/jobs-and-maintenance.md
  • app-file APIs: server/api/files.md
  • module, login, or runtime endpoints: server/api/modules-and-runtime.md
  • auth and sessions: server/auth-and-sessions.md
  • layered filesystem, CUSTOMWARE_PATH, or writable-layer history: server/customware-layers-and-paths.md
  • CLI commands or runtime params: cli/commands-and-runtime-params.md

docs path|name|description↓ architecture/overview.md|Runtime Overview|Browser-first architecture, major entry surfaces, and the layered runtime model. architecture/desktop-host-and-packaging.md|Desktop Host And Packaging|Electron host startup, free-port binding, packaged single-user behavior, and desktop build outputs. architecture/documentation-system.md|Documentation System|How DOX AGENTS.md, the documentation module, and code fit together, plus update rules. app/runtime-and-layers.md|App Runtime And Layers|Frontend boot flow, space runtime namespaces, entry shells, and L0/L1/L2 rules. app/admin-agent-runtime.md|Admin Agent Runtime|Admin chat ownership, config persistence, shared execution loop, and API-versus-local-Hugging-Face transport switching. app/modules-and-extensions.md|Modules And Extensions|/mod/... delivery, router path resolution, dashboard panel manifests, ext/html, ext/js, and <x-component> behavior. app/huggingface-browser-runtime.md|Hugging Face Browser Runtime|The routed Transformers.js test surface, its worker split, direct Hub model loading contract, and throughput metrics. app/webllm-browser-runtime.md|WebLLM Browser Runtime|The routed WebLLM test surface, its worker split, model-loading modes, and throughput metrics contract. app/spaces-and-widgets.md|Spaces And Widgets|Space storage, widget renderer contracts, widget-shell defaults, and the main space.current / space.spaces helpers. agent/onscreen-agent-runtime.md|Onscreen Agent Runtime|Overlay ownership, persistence, defaults, UI/runtime surfaces, and prompt file ownership. agent/memory-and-prompt-includes.md|Memory And Prompt Includes|Prompt-include-backed persistent memory workflow, standard ~/memory files, and the memory-skill contract. agent/prompt-and-execution.md|Prompt And Execution|Prompt assembly order, message markers, execution transcript rules, and compaction behavior. agent/skills-and-documentation.md|Skills And Documentation|Skill discovery rules, top-level versus nested skills, conflict rules, and the documentation skill/helper contract. server/request-flow-and-pages.md|Request Flow And Pages|Exact server routing order, page shell contracts, auth gating, and direct app-file fetches. server/jobs-and-maintenance.md|Jobs And Maintenance|Primary-owned periodic jobs, interval scheduling, mutation publishing, and guest cleanup maintenance rules. server/api/files.md|File APIs|The authenticated file endpoints, path forms, writable discovery, folder downloads, and optional local history APIs. server/api/modules-and-runtime.md|Module And Runtime APIs|Module endpoints, login/runtime endpoints, extensions_load, and identity helpers. server/auth-and-sessions.md|Auth And Sessions|User storage layout, sealed password/session records, and login/runtime auth behavior. server/customware-layers-and-paths.md|Customware Layers And Paths|Logical-versus-disk paths, permission rules, optional writable-layer history, override order, and maxLayer. cli/commands-and-runtime-params.md|Commands And Runtime Params|space.js, command families, runtime-param precedence, and the current schema surface.

examples Reading the frontend runtime docs _____javascript const documentation = await import("/mod/_core/documentation/documentation.js") return await documentation.read("app/runtime-and-layers.md")

Frequently asked questions

What does the Documentation AI skill do?

Read the supplemental project documentation module

Why use Documentation on TypingMind?

Because you install it once and use it with any model. Documentation is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Documentation in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/agent0ai/space-agent/tree/main/app/L0/_all/mod/_core/documentation/ext/skills/documentation. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Documentation?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Documentation?

As many as you like. As long as a model supports skills, you can use Documentation with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Documentation AI skill free?

Yes. It is published on GitHub by agent0ai under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇