Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ar9av/graph-colorize
Color-code the Obsidian graph view by rewriting `.obsidian/graph.json` colorGroups.
Passed 16 of 19 test cases with the skill, and 6 of 19 without it.
and 18 more in the full report
11 fixed7 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
When generating color groups by top-level vault folders, what exact sequence of directories is evaluated and what color index is assigned to the 'skills' folder?
| Checked | Without skill | With skill |
|---|---|---|
| Evaluates folders in order: concepts, entities, skills, references, synthesis, projects, journal. | Missed | Passed |
| Assigns palette index 2 (red, rgb 14767961) to the 'skills' folder rule. | Missed | Passed |
The instructions your model reads when the skill loads.
You are rewriting $OBSIDIAN_VAULT_PATH/.obsidian/graph.json so Obsidian's graph view tints nodes by tag, folder, or visibility.
Obsidian stores graph settings in <vault>/.obsidian/graph.json. The colorGroups array is a list of {query, color} pairs; the first matching query wins per node. Queries use Obsidian's search syntax: tag:#foo, path:"concepts", file:foo, etc. Color is {"a": 1, "rgb": <packed-int>} where the int is (R << 16) | (G << 8) | B.
llm-wiki/SKILL.md (inline @name override → walk up CWD for .env → global config → prompt setup). This gives OBSIDIAN_VAULT_PATH.$OBSIDIAN_VAULT_PATH/.obsidian/ exists. If it doesn't, the vault has never been opened in Obsidian — tell the user to open the vault once in Obsidian, then re-run.graph.json on close. Tell them to close the vault first, or be ready to reload (Cmd/Ctrl+R) and not touch the graph settings until they reload.Infer the mode from the user's phrasing. If ambiguous, default to by-tag.
| User intent | Mode |
|---|---|
| "color by tag", "color my graph", "make it colorful" (default) | by-tag |
| "color by folder", "color by category", "color by directory" | by-category |
| "highlight visibility", "show internal/pii in graph", "visibility colors" | by-visibility |
User provides explicit mapping (tag:#foo = red, or JSON blob) | custom |
| "combine tag and visibility" / "both" | combined (visibility first, then tag) |
colorGroups ArrayUse in order. If more groups than colors, cycle and add a lightness shift by dividing brightness ~20% via a second pass — or just cap at 10 and tell the user the remaining tags share the "other" color.
| # | Hex | rgb (packed int) | Role |
|---|---|---|---|
| 0 | #4E79A7 | 5142951 | blue |
| 1 | #F28E2B | 15896107 | orange |
| 2 | #E15759 | 14767961 | red |
| 3 | #76B7B2 | 7780786 | teal |
| 4 | #59A14F | 5873999 | green |
| 5 | #EDC948 | 15583048 | yellow |
| 6 | #B07AA1 | 11565217 | purple |
| 7 | #FF9DA7 | 16751527 | pink |
test cases passed, vs 6 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.