Skip to content
SkillModel-led2,253 tokens in use

graph-colorize

Color-codes the Obsidian graph view by tag, folder, visibility or your own mapping by rewriting only the colorGroups of graph.json, after a backup.

3,792 stars on the repository MIT LicenseAr9av/obsidian-wiki · skills/graph-colorize
pip install obsidian-wiki
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing graph-colorize costs

42tokens idle
2,253tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter8/15
  • Structure25/25
  • Examples12/15
  • Output5/15
  • Size15/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Excellent
  • Development activity100
  • Maintenance100
  • Community60
  • Maturity28
  • Momentum40

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.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers