moc-update — Claude Code skill: what it does, how to install
moc-update finds the Maps of Content (MOCs) in an Obsidian vault that should link to a freshly created Engineering/ note. Fires on prompts like “update MOC” or “which MOCs”.
ISC ★ 102 updated 2026-10-25
npx skills add thoreinstein/gemini-obsidian --skill moc-update -a claude-codeWhat moc-update does
Given the path to a new note, the skill runs a semantic search through obsidian_rag_query using the note title with a limit of 10 results, then falls back to obsidian_search_notes on key terms from the title to catch MOCs that haven't been indexed yet. It recognizes MOC-style notes by a path containing "MOC", a filename ending in "-MOC", or type: moc frontmatter.
For each candidate MOC it surfaces, the skill shows the file path, the heading the link belongs under, and a ready-made line such as - [[NoteName]] — one-line description. Nothing gets written until the user approves; the actual edit goes through obsidian_insert_at_heading or obsidian_append_note.
If the vault has no MOCs at all, it offers to start one at MOCs/<Topic>-MOC.md. Daily Notes get filtered out of the results since they aren't MOCs.
What it helps with
- locate which MOCs should link to a new note
- insert a note link under the right MOC heading
- bootstrap a starter MOC when none exist yet
- filter out Daily Notes from MOC search results
Example prompts for the agent
- /moc-update Engineering/AuthPatterns.md
- Which MOCs should link to this note?
- Add this note to the right MOC
How to install moc-update
1Skills CLI (Vercel)
npx skills add thoreinstein/gemini-obsidian --skill moc-update -a claude-code2Manually: put the files in place
~/.claude/skills/moc-update/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/moc-update/
1Skills CLI (Vercel)
npx skills add thoreinstein/gemini-obsidian --skill moc-update -a codex2Manually: put the files in place
.agents/skills/moc-update/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add thoreinstein/gemini-obsidian --skill moc-update -a cursor2Manually: put the files in place
.cursor/skills/moc-update/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install thoreinstein/gemini-obsidian skills/moc-update2Manually: put the files in place
.github/skills/moc-update/SKILL.md1Skills CLI (Vercel)
npx skills add thoreinstein/gemini-obsidian --skill moc-update -a gemini-cli2Platform CLI
gemini skills install https://github.com/thoreinstein/gemini-obsidian --path skills/moc-updateManually: put the files in place
.devin/skills/moc-update/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about moc-update
How do I install moc-update for Claude Code?
Run npx skills add thoreinstein/gemini-obsidian --skill moc-update -a claude-code; it lands at ~/.claude/skills/moc-update/SKILL.md.
What does moc-update do?
It searches an Obsidian vault for Maps of Content that should reference a newly created Engineering/ note and proposes link additions, writing nothing until you approve.
How does moc-update tell MOCs apart from regular notes?
It checks for "MOC" in the path, filenames ending in "-MOC", or type: moc frontmatter, and excludes Daily Notes from its results.
Source text
SKILL.md · ISC
--- name: moc-update description: >- Use after creating a new Engineering/ note to suggest which Maps of Content (MOCs) it belongs in. Triggers on "update MOC", "add to MOC", "which MOCs", or when the user has just created an Engineering/ note. --- # MOC Update After New Note Find the Maps of Content (MOCs) that should link to a newly created note and suggest the additions. ## Workflow 1. **Identify the new note** — Path follows the skill invocation. If not provided, ask. 2. **Semantic MOC search** — Call `obsidian_rag_query` with the note title as query, `limit: 10`. Flag results that are MOC-style notes (path contains "MOC", filename ends in "-MOC", or `type: moc` frontmatter). 3. **Keyword fallback** — Call `obsidian_search_notes` with key terms from the note title to catch MOCs that aren't yet indexed. 4. **Present suggestions** — For each candidate MOC, show: - The MOC path - Which heading the link should go under (if readable) - A proposed link line: `- [[NoteName]] — one-line description` 5. **Append on confirmation** — Call `obsidian_insert_at_heading` (preferred) or `obsidian_append_note` to add the link. Never edit without user approval. ## Arguments New note path: `/moc-update Engineering/AuthPatterns.md` ## Tips - If the vault has no MOCs yet, offer to create a starter one at `MOCs/<Topic>-MOC.md` - Daily Notes are not MOCs — skip them in results
© thoreinstein · ISC · thoreinstein/gemini-obsidian