thoreinstein/gemini-obsidian/knowledge

Compound Knowledge Promotion

Identify knowledge that has crystallized across multiple projects and promote it to a global Engineering/ note.

Workflow

1. Scan project knowledge dirs — Call obsidian_list_notes with subfolder: "working".

Filter results to paths matching working/*/knowledge/*.md.

1. Semantic clustering — For each knowledge note path, call obsidian_rag_query

with the note filename (without extension) as query, limit: 8. Track which notes appear in results from 2+ different projects — these are candidates.

1. Read candidates — Call obsidian_read_note on shortlisted files.

Look for shared definitions, patterns, or insights worth generalizing.

1. Draft global note — Compose a new Engineering/<ConceptName>.md with:

• Frontmatter: type: concept, created: <today>
• Synthesized body (not copy-paste — rewrite for clarity)
• ## Source Notes section with [[wikilinks]] back to originating notes

1. Show draft to user — Present the proposed note content and path before creating.

Ask for confirmation.

1. Create on approval — Call obsidian_create_note with the approved content.

1. Report cross-links — List which project knowledge notes should now add [[ConceptName]]

to avoid re-discovering this knowledge next time.

Arguments

Optional topic hint: /compound authentication patterns

Tips

• If obsidian_rag_query returns no results, suggest running /obsidian:index first
• If no notes appear in 2+ projects, report that and suggest manual promotion