Moc update
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.From its SKILL.md
npx -y skills add thoreinstein/obsidian-rag --skill moc-updateAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
- runs commandsInstructs the agent to run 4 commands, including `obsidian_rag_query` and 3 more.
SKILL.md
1.4 KB, 308 tokens by cl100k_base, as published. Nobody here has run it
MOC Update After New Note
Find the Maps of Content (MOCs) that should link to a newly created note and suggest the additions.
Workflow
-
Identify the new note — Path follows the skill invocation. If not provided, ask.
-
Semantic MOC search — Call
obsidian_rag_querywith the note title as query,limit: 10. Flag results that are MOC-style notes (path contains "MOC", filename ends in "-MOC", ortype: mocfrontmatter). -
Keyword fallback — Call
obsidian_search_noteswith key terms from the note title to catch MOCs that aren't yet indexed. -
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
-
Append on confirmation — Call
obsidian_insert_at_heading(preferred) orobsidian_append_noteto 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
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.