agentleFS
mindroom-aimindroom-ai/mindroom/skills/mindroom-docs/SKILL.md

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
  1. Very specific:

    Use this skill when the user asks how MindRoom works, how to configure it, or which commands/workflows to follow.

    line 9
  2. Distinctive:

    Use the current conversation request.

    line 13
  3. Very specific:

    Use llms.txt for high-level navigation only.

    line 19
  4. Very specific:

    Use llms-full.txt only when the answer spans many sections and page-level references are insufficient.

    line 20
  5. Very specific:

    Keep the Matrix homeserver, Matrix client, and MindRoom dashboard distinct.

    line 22
  6. Very specific:

    Use the runtime context for the active homeserver instead of assuming one.

    line 23
  7. Very specific:

    Prefer page-level references (page__*.md) over llms-full.txt.

    line 30
  8. Distinctive:

    Do not invent behavior not present in the references.

    line 31
  9. Distinctive:

    If information is missing, state that it is not documented in this skill corpus.

    line 33

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Load reference-index.md first to discover the best page files.
  2. Load the smallest number of page references needed with get_skill_reference(...).
  3. Use llms.txt for high-level navigation only.
  4. Use llms-full.txt only when the answer spans many sections and page-level references are insufficient.
  5. For setup or administration requests, inspect the available capabilities before claiming the change cannot be performed. Discover and use config_manager for changes it supports, then use the documented config-file workflow for other requested changes.
  6. 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.chat supports custom homeservers. For questions about the MindRoom-hosted service, load page__deployment__hosted-matrix__index.md; for dashboard questions, load the dashboard page reference.
  7. Answer with concrete steps and include the exact reference filenames used.

Rules

  • Prefer page-level references (page__*.md) over llms-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.

Download now (ZIP)

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.