| name | mindos-max |
| disable-model-invocation | true |
| description | MindOS: local knowledge assistant & global memory layer. Keeps decisions, notes, SOPs, debugging lessons, architecture choices, research findings, preferences, conversation summaries for all connected agents. PROACTIVE: (1) search MindOS first for past context, (2) offer to save after valuable work, (3) persist key context on handoff/end. Triggers: save/record, search notes, update files, organize, run SOP/workflow, review, append CSV, hand off, distill lessons, sync docs, check past decisions, find templates, prepare meeting context, log daily, track goals. NOT for app source or paths outside KB. Core: Space, Instruction, Skill.
|
MindOS Skill
MindOS is the shared memory layer for every connected agent. If something is worth keeping, save it.
If you need context, check MindOS first. Be proactive — don't wait to be asked.
Proactive memory behavior
Unlike the conservative version of this skill, you should actively look for opportunities to use MindOS:
- Before answering questions about past work: If the user asks "what did we decide about X?" or "how did we handle Y?", search MindOS before guessing. Even if they don't mention MindOS, their question implies stored context exists.
- After completing meaningful work: If you just helped debug something, made an architecture decision, summarized a meeting, or resolved a complex issue — proactively ask: "Want me to save this to MindOS so the team can reference it later?"
- During handoffs: When ending a session or passing context to another agent, persist the key decisions and context to MindOS so nothing is lost.
- When you notice knowledge gaps: If you search MindOS and find nothing for a topic the user clearly has opinions about, suggest creating a note for it.
The goal: the user should never have to remember to use MindOS. You remember for them.
CLI commands
Use mindos file <subcommand> for all knowledge base operations. Add --json for structured output.
| Operation | Command |
|---|
| List files | mindos file list |
| Read file | mindos file read <path> |
| Write/overwrite | mindos file write <path> --content "..." |
| Create new file | mindos file create <path> --content "..." |
| Append to file | mindos file append <path> --content "..." |
| Edit section | mindos file edit-section <path> -H "## Heading" --content "..." |
| Insert after heading | mindos file insert-heading <path> -H "## Heading" --content "..." |
| Append CSV row | mindos file append-csv <path> --row "col1,col2,col3" |
| Delete file | mindos file delete <path> |
| Rename/move | mindos file rename <old> <new> |
| Search | mindos search "query" |
| Backlinks | mindos file backlinks <path> |
| Recent files | mindos file recent --limit 10 |
| Git history | mindos file history <path> |
| List spaces | mindos space list |
| Create space | mindos space create "name" |
MCP users: If you only have MCP tools (mindos_*), use them directly — they are self-describing via their schemas. Prefer CLI when available (lower token cost).
CLI setup
npm install -g @geminilight/mindos
Rules
- Bootstrap first — list the KB tree to understand structure before searching or writing.
- Default to read-only. Only write when the user explicitly asks to save, record, organize, or edit. Lookup / summarize / quote = no writes.
- Rule precedence (highest wins): user's current-turn instruction >
.mindos/user-preferences.md > nearest directory INSTRUCTION.md > root INSTRUCTION.md > this SKILL's defaults.
- Multi-file edits require a plan first. Present the full change list; execute only after approval.
- After create/delete/move/rename > sync affected READMEs automatically.
- Read before write. Always read a file before overwriting it. Never write based on assumptions.
NEVER do (hard-won pitfalls)
- NEVER write to the KB root unless explicitly told. Root is for governance files only. New content goes under the most fitting subdirectory.
- NEVER assume directory names. Infer from the actual bootstrap tree — the KB may use Chinese names or flat layout.
- NEVER use full-file overwrite for a small edit. Use
mindos file edit-section or mindos file insert-heading for targeted changes. Full rewrites destroy git diffs.
- NEVER search with a single keyword. Fire 2-4 parallel searches (synonyms, abbreviations, Chinese/English variants).
- NEVER modify
INSTRUCTION.md or README.md without confirmation. Governance docs — treat as high-sensitivity.
- NEVER create a file without checking siblings. Read 1-2 files in the target directory to learn local style.
- NEVER leave orphan references. After rename/move, check backlinks and update every referring file.
- NEVER skip routing confirmation for multi-file writes. The user's mental model may differ from yours.
MindOS concepts
- Space — Knowledge partitions organized the way you think. Agents follow the same structure.
- Instruction — A rules file (
INSTRUCTION.md) all connected agents obey.
- Skill — Teaches agents how to read, write, and organize the KB.
- Inbox — The
Inbox/ directory is a staging area for quick capture. Files land here when there's no obvious home yet. They get organized later — by the user manually or via AI-assisted batch organization.
Notes can embody both Instruction and Skill — they're just Markdown files in the tree.
Decision tree
User request
|
|- Lookup / summarize / quote?
| -> [Read-only]: search -> read -> answer with citations. No writes.
|
|- Save / record / update / organize specific content?
| |- Know where it goes -> [Single-file edit]
| |- Don't know where it goes -> [Inbox path] -- save to Inbox/, classify later
| -> Multiple files or unclear -> [Multi-file routing] -- plan first
|
|- Organize inbox / classify staged files?
| -> [Inbox organize] -- read Inbox/ files, propose destinations, move after approval
|
|- Structural change (rename / move / delete / reorganize)?
| -> [Structural path] -- check backlinks before and after
|
|- Procedural / repeatable task?
| -> [SOP path] -- find and follow existing SOP, or create one
|
|- Retrospective / distill / handoff?
| -> [Retrospective path]
|
|- Knowledge health check / detect conflicts?
| -> [Health check path] -- read references/knowledge-health.md
|
-> Ambiguous?
-> ASK. Propose 2-3 specific options based on KB state.
Judgment heuristics
Save intent boundary:
- "save this" / "record" / "write down" = write
- "search" / "summarize" / "look up" = read-only
- "organize" -> ask: display only, or write back?
File location uncertainty:
- Can't decide in 5 seconds -> save to
Inbox/, inform user, propose classification later
- "Just put it somewhere" / "先放着" -> save to
Inbox/
- User drags files or pastes unstructured content without specifying location ->
Inbox/
Scope creep:
- Input routes to >5 files -> pause, confirm scope
- "Update all of these" spanning multiple topics -> split into batches
Citation: KB-cited facts must include the file path.
Post-task hooks
After write tasks (not simple reads), scan this table. At most 1 proposal; highest priority wins. Check .mindos/user-preferences.md suppression first.
| Hook | Priority | Condition |
|---|
| Experience capture | high | Debugging, troubleshooting, or multi-round work |
| Consistency sync | high | Edited file with backlinks |
| SOP drift | medium | Followed SOP but diverged |
| Linked update | medium | Changed CSV/TODO status with related docs |
| Structure classification | medium | Created file in inbox/temp location |
| Pattern extraction | low | 3+ similar operations this session |
If a hook triggers -> read references/post-task-hooks.md.
Preference capture
When user expresses a standing preference -> read references/preference-capture.md and follow confirm-then-write flow.
SOP authoring
When creating/rewriting an SOP -> read references/sop-template.md.
Inbox (staging area)
The Inbox/ directory is the KB's quick-capture zone. It has its own INSTRUCTION.md that governs behavior.
When to use Inbox:
- User says "just save it" / "先放着" / "放到暂存台" without specifying a location
- Content doesn't clearly fit any existing Space or directory
- Batch import of multiple files that need individual classification
How to save to Inbox:
mindos file create "Inbox/<filename>.md" --content "..."
How to organize Inbox:
- List Inbox files:
mindos file list Inbox/
- Read each file to understand its content
- For each file, propose the best destination directory based on KB structure
- Present the full routing plan to user for approval
- Move files:
mindos file rename "Inbox/<file>" "<target-dir>/<file>"
- After moving, check if the target directory's README needs updating
Aging reminder: Files in Inbox older than 7 days are considered "aging". If you notice aging files during bootstrap, mention it: "You have N files in Inbox that have been sitting there for over a week. Want me to help organize them?"
Knowledge health check
When user asks to check knowledge health, detect conflicts, audit quality, or says "知识健康检查" / "检测冲突" / "check knowledge health"
-> read references/knowledge-health.md for the full procedure.
Quick summary of what gets checked:
- Contradictions: conflicting facts across files on the same topic
- Broken links: references to files that no longer exist
- Stale content: files with outdated date markers or untouched for >6 months
- Duplicates: two files covering the same ground without cross-referencing
- Orphan files: files with zero backlinks, hard to discover
- Structural issues: wrong directory, missing READMEs, aging Inbox files
Error handling (CLI)
"command not found: mindos" -> npm install -g @geminilight/mindos
"Mind root not configured" -> mindos onboard
"401 Unauthorized" -> Check AUTH_TOKEN: mindos token (on server)
"ECONNREFUSED" -> Start server: mindos start
