mindroom-docs
Skill354 starsChanged todayApache-2.0View on GitHub
MindRoom documentation corpus for accurate product, configuration, and workflow guidance.
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 3 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Use this skill when the user asks how MindRoom works, how to configure it, or which commands/workflows to follow.
- Distinctive: line 13
Use the current conversation request.
- Very specific: line 19
Use llms.txt for high-level navigation only.
- Very specific: line 20
Use llms-full.txt only when the answer spans many sections and page-level references are insufficient.
- Very specific: line 22
Keep the Matrix homeserver, Matrix client, and MindRoom dashboard distinct.
- Very specific: line 23
Use the runtime context for the active homeserver instead of assuming one.
- Very specific: line 30
Prefer page-level references (page__*.md) over llms-full.txt.
- Distinctive: line 31
Do not invent behavior not present in the references.
- Distinctive: line 33
If information is missing, state that it is not documented in this skill corpus.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
MindRoom Docs
Use this skill when the user asks how MindRoom works, how to configure it, or which commands/workflows to follow.
Inputs
- Use the current conversation request.
Workflow
- Load
reference-index.mdfirst to discover the best page files. - Load the smallest number of page references needed with
get_skill_reference(...). - Use
llms.txtfor high-level navigation only. - Use
llms-full.txtonly when the answer spans many sections and page-level references are insufficient. - For setup or administration requests, inspect the available capabilities before claiming the change cannot be performed. Discover and use
config_managerfor changes it supports, then use the documented config-file workflow for other requested changes. - Keep the Matrix homeserver, Matrix client, and MindRoom dashboard distinct.
Use the runtime context for the active homeserver instead of assuming one.
MindRoom Chat at
https://chat.mindroom.chatsupports custom homeservers. For questions about the MindRoom-hosted service, loadpage__deployment__hosted-matrix__index.md; for dashboard questions, load the dashboard page reference. - Answer with concrete steps and include the exact reference filenames used.
Rules
- Prefer page-level references (
page__*.md) overllms-full.txt. - Do not invent behavior not present in the references.
- Inspect live configuration when the answer depends on current state; do not infer it from generic documentation.
- If information is missing, state that it is not documented in this skill corpus.
Available references
reference-index.md: mapping of docs pages to reference files.llms.txt: compact docs index.llms-full.txt: full combined docs corpus.page__*.md: per-page rendered markdown references.
In this repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/mindroom-docs/references/llms-full.txtllms.txt
- skills/mindroom-docs/references/llms.txtllms.txt
- address-pr-review-commentsSkill
- agent-cli-devSkill
- agent-cli-tmux-supervisionSkill
- code-debateSkill
- docs-reviewSkill
- duplication-auditSkill
- live-testSkill
- native-subagent-pr-loopSkill
- pr-reviewSkill
- agent-conversationsSkill
- open-knowledge-formatSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

