--- name: colibri-obsidian-integration description: HERITAGE skill documenting the donor-era Obsidian plugin (integrations/obsidian-plugin, Control Plane views, task/session sync via unified_* and gsd_* tools). DO NOT invoke in Phase 0 — the live Obsidian plugin is not part of Phase 0 or Phase 1. In Phase 0, the only Obsidian story is the read-only docs mirror at `C:\Users\Kamal\Documents\Obsidian Vault\Colibri`, synced via `E:\AMS\temp\sync-full.bat`. For active Phase 0 ν integrations, see the p0.9-nu-integrations task prompts (MCP Broker, Anthropic client, Notification hub). status: heritage round: R74.5 updated: 2026-04-10 --- # Colibri Obsidian Integration — HERITAGE (not in Phase 0) > ⚠ **Heritage skill. Not in Phase 0. Not in Phase 1.** Everything below describes a donor-era Obsidian plugin (`integrations/obsidian-plugin/`), a vault projection model with `Dashboard.md` + `Projects/*/TODOS.md`, and Control Plane views that consumed donor tools (`unified_help`, `gsd_workflow_status`, `memory_map`, `memory_pack`, `audit_get_actions`). **None of this exists in the Phase 0 target tree.** The `integrations/obsidian-plugin/` directory is not in the Phase 0 repo layout (CLAUDE.md §9.1), the donor tools it called are not in the 19-tool Phase 0 surface (see `colibri-mcp-server` skill), and the Control Plane / Agent Roster / Pipeline Overview concepts depend on runtime capabilities deferred to Phase 1.5. > > **The only Obsidian story in Phase 0** is the **read-only docs mirror**: `docs/` is rsync'd into `C:\Users\Kamal\Documents\Obsidian Vault\Colibri\docs\` via `E:\AMS\temp\sync-full.bat`. Claude must **never** edit files in the vault mirror zone (CLAUDE.md §3, §12). Vault planning lives in `_vault/` only, and the mirror is one-way (repo → vault). > > **Forbidden donor references you will see below** — none of these exist in Phase 0: > - `unified_init`, `unified_vitals`, `unified_help` > - `gsd_workflow_status`, `memory_map`, `memory_pack`, `audit_get_actions` > - `task_deps` (replaced by `task_depends_on`) > - `src/server.js` (replaced by `src/server.ts` target, P0.2.1) > - `src/domains/tasks/markdown-sync.js` (not in Phase 0 tree) > - `AMS_ROOT`, `AMS_WATCH_MODE`, `COLIBRI_MCP_SERVER` (env replaced by COLIBRI_DB_PATH + COLIBRI_MODE — see `colibri-mcp-server` skill) > - `integrations/obsidian-plugin/` directory (not in Phase 0 repo layout) > > **For active Phase 0 ν (Integrations) work**, see: > - `docs/guides/implementation/task-prompts/p0.9-nu-integrations.md` — the three real Phase 0 integration tasks (MCP Broker, Anthropic client, Notification hub) > - `colibri-mcp-server` skill — for the 19-tool Phase 0 MCP surface > - `colibri-task-management` skill — for β Task Pipeline sync contracts
Heritage content (read-only, Phase 1.5+ reference) Use this skill for Obsidian-specific work around the Colibri plugin. ## Core Capabilities - Configure the Obsidian plugin in `integrations/obsidian-plugin/` - Validate the plugin package, build output, and sideload flow - Troubleshoot MCP startup from Obsidian to `src/server.js` - Explain and maintain the vault projection model: - `Colibri/Dashboard.md` - `Colibri/Projects//TODOS.md` - `Colibri/Projects//PROGRESS.md` - `Colibri/Sessions//.md` - **Control Plane** - Native Obsidian interface for Colibri management: - Tool Surface Manager - Browse and inspect Colibri tools - Cryptographic Audit Log - Verify action signatures - Agent Roster - Configure agent capabilities - Pipeline Overview - Monitor GSD workflows in real-time - Memory Inspector - Browse Colibri memory frames - Extend the plugin while preserving the current rules: - checkbox-only task status writeback - command-driven session writeback - Colibri remains the source of truth for structured fields - startup/manual sync model, not timer-driven background sync ## Tool Contract Registry Plugin integration contracts are documented in `data/tool-contracts/`. Reference for: - MCP message schemas - Sync operation contracts - Vault projection formats ## Execution Rules 1. Treat `integrations/obsidian-plugin/` as the plugin package root. 2. Treat `src/server.js` as the production MCP server entrypoint. 3. Keep the plugin desktop-only unless the user explicitly changes that scope. 4. Do not introduce bridge scripts, REST shims, or alternate transports unless the user explicitly requests a new design. 5. Reuse the shared markdown task helpers in `src/domains/tasks/markdown-sync.js` instead of duplicating parser or renderer logic. 6. Validate both sides when editing the integration: - `npm test` and `npm run lint` in project root - `npm run check` and `npm run build` in `integrations/obsidian-plugin` ## Quick Start 1. `unified_init` 2. `unified_vitals` 3. Check Obsidian MCP client config points to `src/server.js` 4. Set `AMS_WATCH_MODE=none` in Obsidian client config ## When to Use This Skill - Installing or updating the Obsidian plugin - Configuring MCP client connection to Colibri server - Validating plugin health and functionality - Troubleshooting sync issues between Obsidian and Colibri - Extending plugin features (UI components, commands, views) - Maintaining vault structure and project notes - Debugging MCP communication or message formats ## Core Integration Points ### Control Plane Views - **Tool Surface Manager** - Lists all available tools from `unified_help` - **Cryptographic Audit Log** - Displays signed audit records from `audit_get_actions` - **Agent Roster** - Shows active agents and pool membership - **Pipeline Overview** - Real-time workflow and phase status via `gsd_workflow_status` - **Memory Inspector** - Browse memory frames via `memory_map` and `memory_get` ### Task Sync - Checkbox state in markdown → `task_update` with status - Task notes in Obsidian → `task_update` with description - Dependencies formatted in markdown → synced via `task_deps` - Bidirectional sync on demand (no background timers) ### Session Management - Session command in Obsidian → `audit_session_start` - Session notes collected → `memory_pack` and `thought_record` - Manual flush to Colibri via slash command ### Vault Structure ``` Colibri/ ├── Dashboard.md (overview, pinned tasks) ├── Projects/ │ ├── colibri/ │ │ ├── TODOS.md (task list) │ │ └── PROGRESS.md (roadmap/phase status) │ └── other-project/ ├── Sessions/ │ ├── colibri/ │ │ └── session-id.md (session notes) ``` ## Configuration ### Obsidian Client Config ```env AMS_ROOT= AMS_WATCH_MODE=none COLIBRI_MCP_SERVER=/src/server.js DOTENV_CONFIG_QUIET=true ``` ### Plugin Settings - MCP server path: `/src/server.js` - Vault sync folder: `Colibri/` - Auto-refresh on open: disabled (manual sync only) ## Operating Rules 1. Always validate plugin build before sideloading 2. Check MCP connection in Obsidian console before troubleshooting 3. Use manual sync commands rather than auto-refresh 4. Preserve Obsidian as read-optimized view, Colibri as write authority 5. Document custom views or commands in plugin README ## Common Issues | Issue | Cause | Resolution | |-------|-------|-----------| | MCP connection fails | Server path wrong or server not running | Check plugin settings, restart MCP server | | Tasks don't sync | Watch mode conflict | Set `AMS_WATCH_MODE=none` in client config | | Build fails | Dependency version mismatch | Run `npm install` in plugin folder | | Views don't render | Missing tool data from server | Run `unified_vitals` to confirm server health | ## Integration with Other Skills - **colibri-mcp-server**: Use for server health and tool inventory - **colibri-task-management**: Use for task sync validation - **colibri-gsd**: Use for workflow status in Control Plane views ## Typical Requests - "Set up the Obsidian plugin for Colibri" - "Validate the plugin build and connection" - "Sync Colibri tasks to Obsidian" - "Show me the Control Plane dashboard" - "Troubleshoot MCP connection issues" - "Extend the plugin with a custom view" ## References - Plugin source: `integrations/obsidian-plugin/` - Tool contracts: `data/tool-contracts/` - Vault structure: `docs/integrations/obsidian.md` - Markdown sync helpers: `src/domains/tasks/markdown-sync.js`