Obsidian Project Sync Manager

Problem: project knowledge gets buried in ephemeral conversation

Useful engineering facts usually come from repositories, docs, tests, configs, and verification commands, not from assistant chat. Saving conversations into Obsidian can turn a vault into a narrative log, making it harder to answer questions about architecture, key paths, status, and how to verify the project. This skill redirects note creation toward durable project facts.

How it works: maintain a project wiki, not a work diary

• Resolve the target wiki: prefer an explicit path, then look for SCHEMA.md, AGENTS.md, CLAUDE.md, or a handoff note; also consider OBSIDIAN_VAULT_PATH, WIKI_PATH, and an existing local Obsidian/Markdown folder. If ambiguity remains, it asks for confirmation.
• Scope the sync: write only project-type knowledge tied to a real local folder or repository. It avoids ordinary chat, status updates, tool-operation history, “what the agent did” logs, secrets, tokens, .env contents, credentials, and noisy logs.
• Search before creating: read index.md, log.md, and recent notes, search existing pages, and follow the wiki schema when one exists.
• Capture durable facts: update the project entity page with overview, architecture, tech stack, important paths, key files, current status, verification commands, open issues, and related projects. Append a change-log entry with modification time and content, and maintain index.md, log.md, and wikilinks.md where present.
• Link related knowledge: use [[wikilinks]] to connect projects, change logs, technologies, decisions, PRDs/specs, and reusable concepts, while keeping concepts/, comparisons/, and queries/ sparse.

Fit and cautions

This is suited for turning real project files into Obsidian-compatible knowledge pages, not for archiving conversations or agent traces. Provide a clear vault path or project root when possible; if the vault is inaccessible, the final response includes a compact Obsidian Memory Update block. Before considering the task done, verify expected notes exist, wikilinks are not broken, and sensitive-value scans do not expose credentials.