obsidian-global-knowledge

Obsidian Global Knowledge

Use this skill to answer questions from the configured Obsidian vault through the littlebird-obsidian-mcp server.

Trigger Phrases

• "Check my global directory."
• "Search global knowledge."
• "Search Obsidian for this."
• "What do we know about Example Project?"
• "Look in my knowledge base."
• "Check project memory."

Required Tool

Preferred MCP server: littlebird_obsidian

Useful tools:

• search_notes
• read_note
• list_vault_folder

If those tools are unavailable, tell the user the Littlebird Obsidian MCP server is not registered in the active Codex session and point them to the setup docs.

Workflow

1. Convert the user request into 2-5 targeted search terms.
   • Include obvious aliases from the user's routing config, for example project names, company names, abbreviations, and alternate spellings.
2. Call search_notes for the highest-signal terms first.
3. Read the most relevant notes with read_note.
4. Prefer routed knowledge notes over raw/ledger notes:
   • Projects/
   • company or organization folders configured by the user
   • People/
   • Decisions/
   • Tasks/
   • Open Loops/
   • Daily/
5. Use 03_Agent_Context/Littlebird Ingest Ledger/ only to verify import provenance, not as the main evidence source.
6. Answer with a concise synthesis and cite the note paths used.

Safety And Quality Rules

• Do not claim the vault is exhaustive. Say what was found in the searched notes.
• If search returns weak matches, say so and ask whether to broaden the search.
• Do not use raw Littlebird captures as primary context when routed notes exist.
• When the user asks for current state, favor the newest dated sections in project/company/task/open-loop notes.
• If a note appears stale or conflicting, call that out.

Response Shape

Use this structure when the answer is more than a sentence:

Here is what I found in global knowledge:

<answer>

Sources:
- <vault-relative path>
- <vault-relative path>