What problem does it solve? In a personal knowledge base, hub notes (MOCs) accumulate hundreds of incoming links until they become useless backlink dumps. This Skill diagnoses the tangle by in-degree, splits the hub into sub-MOCs based on its existing structure, and re-links incoming references so the graph becomes navigable again. ## Core Features & Use Cases - Tangle Diagnosis: Counts in-links and out-links across three distinct streams (out-neighbors, up-children in frontmatter, and body mentions) to determine whether a note qualifies as a tangle. - Sub-MOC Creation: Builds sub-MOCs from the hub's existing subheadings or a chosen categorization axis, preserving the author's mental model and keeping the original MOC as a general entry point. - Two-Iteration Re-linking: First re-links up frontmatter fields on neighbors (safe scaffold), then optionally redirects in-links inside resource note bodies, with a confirmation gate between iterations. - Use Case: Your [[DevOps]] map has 222 incoming links and is unreadable. Run this Skill to create sub-maps like DevOps – Деплой и релиз, re-link resource notes to the right sub-map, and cut the hub's in-degree by 50-70%. ## Quick Start Ask the AI to untangle the overloaded hub note [[DevOps]] in your Obsidian vault and redirect its incoming links to new sub-MOCs.
