Plugin Orchestration Protocol (POP) for Obsidian integration. Use this skill when the user mentions "POP", "Obsidian plugin", "pipeline orchestration", "idea to publish", "websocket bridge", "plugin manifest", "Obsidian automation", "note-to-paper pipeline", "knowledge pipeline", or wants to orchestrate multi-step workflows through Obsidian. This skill implements the 5-phase JSON-RPC protocol over WebSocket for real-time plugin orchestration.
Plugin Orchestration Protocol (POP) for Obsidian integration. Use this skill when the user mentions "POP", "Obsidian plugin", "pipeline orchestration", "idea to publish", "websocket bridge", "plugin manifest", "Obsidian automation", "note-to-paper pipeline", "knowledge pipeline", or wants to orchestrate multi-step workflows through Obsidian. This skill implements the 5-phase JSON-RPC protocol over WebSocket for real-time plugin orchestration.
version
1.0.0
POP Super-Obsidian — Plugin Orchestration Protocol
The POP protocol enables real-time orchestration of multi-step pipelines through Obsidian.
It connects Claude (orchestrator), Obsidian (vault + UI), and the Rust TUI (monitoring dashboard)
via JSON-RPC over WebSocket at ws://127.0.0.1:8088.
Protocol Overview
POP operates in 5 phases, each with specific JSON-RPC message types:
Phase 1: Discovery
Message:GET_PLUGIN_MANIFESTPurpose: Ask the Obsidian plugin what capabilities are installed.
Response: Returns a manifest of all installed Obsidian plugins with their exposed actions.
Use this to understand what the vault can do before constructing a pipeline.
Phase 2: Orchestration
Message:EXECUTE_PIPELINEPurpose: Send a named pipeline with steps to execute.
Step references: Use $step_id.output.field to reference outputs from previous steps.
This creates a DAG of dependencies that the orchestrator resolves in topological order.
Phase 3: Progress
Message:STEP_COMPLETEDirection: Obsidian → Claude (notification)
