mindos-max
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.
npx skills add GeminiLight/MindOS --skill mindos-max --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# MindOS Skill <!-- version: 3.2.0-max — aggressive global memory mode --> > **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:
- Proactive memory behavior
- CLI commands
- CLI setup
- Rules
- NEVER do (hard-won pitfalls)
- MindOS concepts
- Decision tree
- Judgment heuristics
- Post-task hooks
- Preference capture
- SOP authoring
- Inbox (staging area)
- Knowledge health check
- Error handling (CLI)
npm install -g @geminilight/mindos Remote mode: mindos config set url http://<IP>:<PORT> && mindos config set authToken <token> mindos file create "Inbox/<filename>.md" --content "..."
What does the mindos-max skill do?
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.
How do I install it?
Run `npx skills add GeminiLight/MindOS --skill mindos-max --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From GeminiLight/MindOS, a repository with 657 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.