obsidian-graphlisted

# Obsidian Graph view Global graph configuration lives in `.obsidian/graph.json`. Local graph (Graph view opened from a single note) lives in `.obsidian/workspace.json` and **does not inherit** from global. This skill covers global graph unless explicitly noted. For diagnosing *what's wrong* with a graph (over-connection, render-only edges, false categories), use the paired `obsidian-graph-audit` skill first. ## Workflow when the user asks "configure my graph" 1. **Ask or read intent first.** What's bothering them, or what do they want to see? Color groups without a goal are pure aesthetics — skip them. 2. **⚠️ Have the user close Graph view (or quit Obsidian).** This is mandatory — Obsidian rewrites `graph.json` when Graph view closes, wiping external edits. See Caveats. 3. **Read the current `.obsidian/graph.json`.** Don't reset settings the user has tuned (especially `scale`). 4. **Measure vault size:** `find . -name '*.md' -not -path './.obsidian/*' -not -path './.trash/*' -not -path './.claude/*' | wc -l`. Forces depend on this. 5. **Apply minimum changes**, explain each. 14 color groups on 600 notes is too many — 3-8 is the proven range. 6. **Keep only what adds signal.** Filter > group when you don't want to see something; group > filter when you want to differentiate. 7. **Verify decimal RGB math.** A wrong byte in a color value silently renders as a different color. Always round-trip HEX↔decimal (see below). 8. **Have the user open Graph view after edits.** Chang