From mos
Data Room awareness, filing intelligence, and passive monitoring. Active when room/ exists -- gives Larry project structure context and filing guidance.
npx claudepluginhub jsagir/mindrian-os-pluginThis skill uses the workspace's default tool permissions.
This skill activates when `scripts/resolve-room` finds any active room. The resolver checks (in order): central registry at `~/MindrianRooms/.rooms/registry.json`, directory scan under `~/MindrianRooms/`, workspace registry, and legacy `room/` fallback. If any strategy returns a path, this skill is active.
Conducts multi-round deep research on GitHub repos via API and web searches, generating markdown reports with executive summaries, timelines, metrics, and Mermaid diagrams.
Dynamically discovers and combines enabled skills into cohesive, unexpected delightful experiences like interactive HTML or themed artifacts. Activates on 'surprise me', inspiration, or boredom cues.
Generates images from structured JSON prompts via Python script execution. Supports reference images and aspect ratios for characters, scenes, products, visuals.
This skill activates when scripts/resolve-room finds any active room. The resolver checks (in order): central registry at ~/MindrianRooms/.rooms/registry.json, directory scan under ~/MindrianRooms/, workspace registry, and legacy room/ fallback. If any strategy returns a path, this skill is active.
The resolved room path (absolute) is the working room for all operations below.
Be aware of the active room's structure: reference specific sections, note empty sections as opportunities, use entry counts for completeness, read ROOM.md for section purpose. The room lives under ~/MindrianRooms/[name]/ (or legacy room/ for unmigrated workspaces).
8 DD-aligned sections: problem-definition, market-analysis, solution-design, business-model, competitive-analysis, team-execution, legal-ip, financial-model
Plus: team/ (members/mentors/advisors with ICM nested profiles), meetings/ (YYYY-MM-DD-{name}/ archives)
Every directory in the Data Room MUST have an identity file (ROOM.md). No exceptions. This is ICM Layer 0 -- it answers "Where am I? What belongs here? What does NOT belong here?"
When creating ANY new directory -- whether a room section, sub-room, team profile folder, meeting archive, opportunity bank, or any other folder -- ALWAYS create a ROOM.md inside it.
---
icm_layer: 0
section: {section-name or folder-type}
parent: {parent-room-or-directory}
---
# {Folder Display Name}
{One sentence: what this folder contains.}
## What Belongs Here
- {2-4 bullet points}
## What Does NOT Belong Here
- {2-3 redirects to correct locations}
Without Layer 0, Claude (on any surface -- CLI, Desktop, Cowork) cannot determine what belongs in a folder. This leads to misfiling, duplication, and lost context. ROOM.md is the folder's contract with every agent that touches it.
When methodology produces an artifact:
references/methodology/index.md)Rule: Whenever you write a new artifact into the active room (via any skill, command, or direct edit), the artifact MUST arrive with wikilinks already present. Do NOT leave wikilinking to a retroactive batch pass -- wikilinks are part of the artifact's birth, not a later cleanup.
How (preferred -- call the wrapper):
After writing a new file, immediately run:
node scripts/wikilink-file.cjs "$ROOM_DIR" "$NEW_FILE_PATH" \
[--filed-to-target="market-analysis/2026-04-09-tam.md"] \
[--meeting-slug="2026-04-09-align-strategy-session"]
The wrapper loads lib/vault/room-scanner.cjs + lib/vault/wikilink-builder.cjs, scans the room once, injects team-name wikilinks into the new file's body, and (if a meeting slug is given) appends a filed-to footer. Errors are logged to stderr but never abort filing -- backward compatibility is non-negotiable.
How (manual -- when running the wrapper is not feasible):
Inject wikilinks directly while writing the artifact:
[[team/{category}/{slug}/PROFILE.md|{Display Name}]]. Longer names beat prefixes (e.g., "Avital Leibovich" wins over "Avital"). Never self-link (the person's own PROFILE.md stays plain).[[{section}/ROOM.md|{section}]]meetings/{slug}/filed-to/) -> include BOTH lines:
-> Full artifact: [[{section}/{artifact-filename}.md]]
<- Source meeting: [[meetings/{slug}/summary.md|{Meeting Display Name}]]
YYYY-MM-DD- prefix stripped and the remainder title-cased ("2026-04-09-align-strategy-session" -> "Align Strategy Session").Graceful fallback (WIKI-06): If the room has zero team profiles or zero meetings, skip that link type. Do not crash, do not invent targets.
Idempotence: Never double-link. If [[...|Name]] already exists for a display name, don't add another occurrence of the same link. If a filed-to footer line already exists, do not duplicate it.
Canonical builder module: See lib/vault/wikilink-builder.cjs -- it exports buildTeamLinks, buildSectionLink, buildMeetingLink, buildFiledToFooter, injectFiledToFooter as pure functions. The scripts/wikilink-file.cjs wrapper is the preferred filing-time entry point. Phase 76's retroactive scripts/vault-wikilink-injector.cjs remains available for whole-room sweeps.
When .rooms/registry.json exists:
/mos:rooms open [target])Single-room mode (no registry): skip lock checks.
Every filed artifact MUST include frontmatter: methodology, created, depth, problem_type, venture_stage, room_section.
source: transcript artifacts carry extended metadata: speaker, speaker_role, meeting_date, segment_type, confidence, assumptions, perspective, cascade_sections.
cascade_sections: fieldFor ad-hoc meeting mentions, suggest /mos:file-meeting for structured filing.
When tengu_harbor env var is true or room/.mindrian/uds-active exists, check room/.mindrian/uds-inbox/ for cross-instance updates on session start. Surface new entries to user before standard greeting. This is a future capability -- currently a no-op until UDS ships.
When room has 2+ sections with content, mention wiki once per session after filing, analyzing, or first methodology output: "/mos:wiki for live wiki view." Sharing: /mos:wiki --export for static HTML bundle.