AgriciDaniel/claude-obsidian / skills/wiki
wiki
VerifiedInitialize, adopt, and route work for a separate Obsidian knowledge vault through the portable claude-obsidian core. Use for vault setup, scaffolding, workspace selection, cross-project configuration, or choosing the correct wiki sub-skill. Triggers: /wiki, set up wiki, scaffold vault, create knowledge base, adopt this vault, Obsidian vault, second brain setup, persistent wiki.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.1 KB |
| references/coordination.md | markdown | 1.9 KB |
| references/css-snippets.md | markdown | 4.3 KB |
| references/dataview.md | markdown | 1.6 KB |
| references/frontmatter.md | markdown | 2.7 KB |
| references/git-setup.md | markdown | 2.5 KB |
| references/install-modes.md | markdown | 1.9 KB |
| references/knowledge-recipes.md | markdown | 3.3 KB |
| references/mcp-setup.md | markdown | 1.9 KB |
| references/model-guidance.md | markdown | 1.6 KB |
| references/modes.md | markdown | 3.1 KB |
| references/operation-transactions.md | markdown | 6.0 KB |
| references/plugins.md | markdown | 2.7 KB |
| references/provenance.md | markdown | 3.2 KB |
| references/rest-api.md | markdown | 1.4 KB |
references/css-snippets.md
View on GitHub# Visual Customization
Apply during scaffold. This makes the file explorer color-coded by folder type and adds custom callout styles.
---
## CSS Snippet
Create this file at `.obsidian/snippets/vault-colors.css` inside the vault:
```css
:root {
--wiki-1: #4fc1ff;
--wiki-2: #c586c0;
--wiki-3: #dcdcaa;
--wiki-4: #ce9178;
--wiki-5: #6a9955;
--wiki-6: #d16969;
--wiki-7: #569cd6;
}
/* Folder colors in file explorer */
.nav-folder-title[data-path^="wiki/domains"] { color: var(--wiki-1); }
.nav-folder-title[data-path^="wiki/entities"] { color: var(--wiki-2); }
.nav-folder-title[data-path^="wiki/concepts"] { color: var(--wiki-3); }
.nav-folder-title[data-path^="wiki/sources"] { color: var(--wiki-4); }
.nav-folder-title[data-path^="wiki/questions"] { color: var(--wiki-5); }
.nav-folder-title[data-path^="wiki/comparisons"] { color: var(--wiki-6); }
.nav-folder-title[data-path^="wiki/meta"] { color: var(--wiki-7); }
.nav-folder-title[data-path=".raw"] { color: #808080; opacity: 0.6; }
/* Custom callouts */
.callout[data-callout='contradiction'] {
--callout-color: 209, 105, 105;
--callout-icon: lucide-alert-triangle;
}
.callout[data-callout='gap'] {
--callout-color: 220, 220, 170;
--callout-icon: lucide-help-circle;
}
.callout[data-callout='key-insight'] {
--callout-color: 79, 193, 255;
--callout-icon: lucide-lightbulb;
}
.callout[data-callout='stale'] {
--callout-color: 128, 128, 128;
--callout-icon: lucide-clock;
}
```
---
## Enable the Snippet
Tell the user: Settings > Appearance > CSS Snippets > open folder > paste the file > click the refresh icon > toggle it on.
---
## Graph View Groups
Guide the user to set these in Graph View settings (click the settings icon in the graph view):
| Query | Color |
|-------|-------|
| `path:wiki/domains` | Blue (`#4fc1ff`) |
| `path:wiki/entities` | Purple (`#c586c0`) |
| `path:wiki/concepts` | Yellow (`#dcdcaa`) |
| `path:wiki/sources` | Orange (`#ce9178`) |
| `path:wiki/questions` | Green (`#6a9955`) |
| `path:.raw` | Gray (dimmed) |
---
## Custom Callouts
This vault defines **four custom callout types** beyond Obsidian's built-in set (`note`, `tip`, `warning`, `info`, `todo`, `success`, `question`, `failure`, `danger`, `bug`, `example`, `quote`). They render correctly **only when `vault-colors.css` is enabled**. Without the snippet, they fall back to default callout styling (still readable, just plain).
| Custom callout | Color | Icon | Use for |
|---|---|---|---|
| `contradiction` | reddish-brown (rgb 209,105,105) | `lucide-alert-triangle` | New source conflicts with existing claim |
| `gap` | beige (rgb 220,220,170) | `lucide-help-circle` | Topic has no source yet |
| `key-insight` | bright blue (rgb 79,193,255) | `lucide-lightbulb` | Important takeaway worth highlighting |
| `stale` | gray (rgb 128,128,128) | `lucide-clock` | Claim may be outdated, source older than threshold |
### Usage
Use these in wiki pages to flag important states:
```markdown
> [!contradiction] Title
> [[Page A]] claims X. [[Page B]] says Y. Needs resolution.
> [!gap] Title
> This topic has no source yet. Consider finding one.
> [!key-insight] Title
> The most important takeaway from this section.
> [!stale] Title
> This claim may be outdated. Source was from 2022.
```
### Why custom callouts (vs built-in)
The four custom types map to wiki-specific concepts that don't fit cleanly into Obsidian's default set:
- `contradiction` is more specific than `warning`: it signals a **resolvable conflict** between two wiki pages, not a generic warning.
- `gap` is more specific than `question`: it signals a **missing source**, an actionable improvement.
- `key-insight` is more specific than `tip`: it marks **the** most important takeaway from a section, used sparingly.
- `stale` has no built-in equivalent: it signals time-based decay of a claim.
If you don't want custom callouts, replace them with built-ins:
- `[!contradiction]` → `[!warning] Contradiction`
- `[!gap]` → `[!question] Gap`
- `[!key-insight]` → `[!tip] Key insight`
- `[!stale]` → `[!warning] Stale`
---
## Theme compatibility
The snippet uses standard CSS variables and does not require a community theme.
If the user chooses a theme, verify contrast and selector behavior in the
installed Obsidian version before recommending it for accessibility-sensitive
work.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |