graph-colorize

Update Obsidian graph.json colorGroups from vault tags and folders.

Updated Feb 2, 2016
One-click install
npx skills add https://github.com/zjykzk/blog --skill graph-colorize-zjykzk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: graph-colorize
Source: https://github.com/zjykzk/blog/tree/main/.agents/skills/graph-colorize
Command: npx skills add https://github.com/zjykzk/blog --skill graph-colorize-zjykzk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Colorize Obsidian's graph view by automatically assigning colorGroups to nodes based on tags, folders, and visibility, improving readability without manual tweaking.

Core Features & Use Cases

  • Automatically derives colorGroups from vault tags and folder structure to tint nodes in Obsidian's graph.
  • Merges colorGroups into existing graph.json without clobbering other settings.
  • Provides a backup mechanism and safe replacement workflow to prevent data loss.

Quick Start

Run the colorize skill to colorize your Obsidian graph based on the vault's tags.

Frequently Asked Questions about graph-colorize

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I color-code Obsidian graph nodes automatically based on tags?

You can color-code the Obsidian graph by updating the vault's graph.json colorGroups based on actual tags and categories. This Skill automatically derives colorGroups from vault tags and folder structure to tint nodes without manual tweaking.

Can I update graph.json colorGroups without losing my existing graph settings?

Yes, updating graph.json colorGroups merges new color settings into the existing file without clobbering other graph configurations. It also provides a backup mechanism and safe replacement workflow to prevent data loss.

How does automatic graph colorization handle folder structure and vault tags?

Graph colorization handles folder structure and vault tags by reading the vault path from the environment config, deriving colorGroups from actual tags and folders, and safely replacing existing colorGroups while preserving other settings.

Does this graph colorization approach work with varied Obsidian vault configurations?

Yes, this approach applies to Obsidian vaults where users want visual differentiation of nodes by tag, folder, or visibility across varied graph configurations. It requires reading the vault path from the environment or config.

What is the best way to back up graph.json before applying new colorGroups?

The best way to back up graph.json before applying new colorGroups is using the built-in backup mechanism provided by the colorization workflow. It safely backs up existing graph.json before replacing colorGroups to prevent data loss.

Why are my Obsidian graph nodes not showing different colors after updating tags?

Obsidian graph nodes may not show different colors if graph.json colorGroups are not updated to reflect actual tags and categories. Running the colorization skill safely replaces colorGroups based on current vault tags and folder structure.