graph-colorize edits .obsidian/graph.json so Obsidian’s graph view tints nodes by what they are. It supports five modes: by tag (the default), by folder category, by visibility, a combined visibility-then-tag mode, and a custom mapping you provide.
It uses a fixed ten-color palette, keeps every other graph setting as it was, writes a timestamped backup before each change and logs the run to the vault log.
What You Get
- A colored graph view after a reload of Obsidian
- A timestamped backup of graph.json made before each write
- Your zoom, physics, filter and display settings left as they were
- A log entry for each run, and a way to restore or clear the colors
Common Use Cases
- Color the graph by tag to see topic clusters
- Color by top-level folder to tell concepts from entities and projects
- Highlight pages tagged pii or internal before sharing a vault
- Apply your own tag to color mapping
What Makes It Unique
It is a narrow, safe config editor: it changes one field, backs up first, warns that Obsidian rewrites graph.json on close, and refuses to create the .obsidian folder itself. The palette matches the one used by the wiki export, so the Obsidian graph and the exported visualization look alike.
Under The Hood
The skill is instructions for the agent. It reads the vault config, globs markdown files and parses their frontmatter tags, then reads and rewrites .obsidian/graph.json inside the vault, copying the old file to a backup first, and appends a line to the vault log. It does not touch page content, runs no scripts of its own and makes no web requests.