Obsidian Canvas Creator
Transform text content into structured Obsidian Canvas files with support for MindMap and freeform layouts.
When to Use This Skill
- User requests to create a canvas, mind map, or visual diagram from text
- User wants to organize information spatially
- User mentions "Obsidian Canvas" or similar visualization tools
- Converting structured content (articles, notes, outlines) into visual format
Core Workflow
1. Analyze Content
Read and understand the input content:
- Identify main topics and hierarchical relationships
- Extract key points, facts, and supporting details
- Note any existing structure (headings, lists, sections)
2. Determine Layout Type
Ask user to choose or infer from context:
MindMap Layout:
- Radial structure from center
- Parent-child relationships
- Clear hierarchy
- Good for: brainstorming, topic exploration, hierarchical content
Freeform Layout:
- Custom positioning
- Flexible relationships
- Multiple connection types
- Good for: complex networks, non-hierarchical content, custom arrangements
3. Plan Structure
For MindMap:
- Identify central concept (root node)
- Map primary branches (main topics)
- Organize secondary branches (subtopics)
- Position leaf nodes (details)
For Freeform:
- Group related concepts
- Identify connection patterns
- Plan spatial zones
- Consider visual flow
4. Generate Canvas
Create JSON following the Canvas specification:
Node Creation:
- Assign unique 8-12 character hex IDs
- Set appropriate dimensions based on content length
- Apply consistent color schemes
- Ensure no coordinate overlaps
Edge Creation:
- Connect parent-child relationships
- Use appropriate arrow styles
- Add labels for complex relationships
- Choose line styles (straight for hierarchy, curved for cross-references)
Grouping (Optional):
- Create visual containers for related nodes
- Use subtle background colors
- Add descriptive labels
5. Apply Layout Algorithm
MindMap Layout Calculations:
Refer to references/layout-algorithms.md for detailed algorithms. Key principles:
- Center root at (0, 0)
- Distribute primary nodes radially
- Space secondary nodes based on sibling count
- Maintain minimum spacing: 320px horizontal, 200px vertical
Freeform Layout Principles:
- Start with logical groupings
- Position groups with clear separation
- Connect across groups with curved edges
- Balance visual weight across canvas
6. Validate and Output
Before outputting:
Validation Checklist:
- All nodes have unique IDs
- No coordinate overlaps (check distance > node dimensions + spacing)
- All edges reference valid node IDs
- Groups (if any) have labels
- Colors use consistent format (hex or preset numbers)
- JSON is properly escaped (Chinese quotes: 『』 for double, 「」 for single)
Output Format:
- Complete, valid JSON Canvas file
- No additional explanation text
- Directly importable into Obsidian
Node Sizing Guidelines
Text Length-Based Sizing:
- Short text (<30 chars): 220 × 100 px
- Medium text (30-60 chars): 260 × 120 px
- Long text (60-100 chars): 320 × 140 px
- Very long text (>100 chars): 320 × 180 px
Color Schemes
Preset Colors (Recommended):
"1" - Red (warnings, important)
"2" - Orange (action items)
"3" - Yellow (questions, notes)
"4" - Green (positive, completed)
"5" - Cyan (information, details)
"6" - Purple (concepts, abstract)
Custom Hex Colors:
Use for brand consistency or specific themes. Always use uppercase format: "#4A90E2"
Critical Rules
Quote Handling:
- Chinese double quotes → 『』
- Chinese single quotes → 「」
- English double quotes →
\"
ID Generation:
- 8-12 character random hex strings
- Must be unique across all nodes and edges
Z-Index Order:
- Output groups first (bottom layer)
- Then subgroups
- Finally text/link nodes (top layer)
Spacing Requirements:
- Minimum horizontal: 320px between node centers
- Minimum vertical: 200px between node centers
- Account for node dimensions when calculating
JSON Structure:
- Top level contains only
nodes and edges arrays
- No extra wrapping objects
- No comments in output
Examples
Simple MindMap Request
User: "Create a mind map about solar system planets"
Process:
- Identify center: "Solar System"
- Primary branches: Inner Planets, Outer Planets, Dwarf Planets
- Secondary nodes: Individual planets with key facts
- Apply radial layout
- Generate JSON with proper spacing
Freeform Content Request
User: "Turn this article into a canvas" + [article text]
Process:
- Extract article structure (intro, body sections, conclusion)
- Identify key concepts and relationships
- Group related sections spatially
- Connect with labeled edges
- Apply freeform layout with clear zones
Reference Documents
- Canvas Specification:
references/canvas-spec.md - Complete JSON Canvas format specification
- Layout Algorithms:
references/layout-algorithms.md - Detailed positioning algorithms for both layout types
Load these references when:
- Need specification details for edge cases
- Implementing complex layout calculations
- Troubleshooting validation errors
Tips for Quality Canvases
- Keep text concise: Each node should be scannable (<2 lines preferred)
- Use hierarchy: Group by importance and relationship
- Balance the canvas: Distribute nodes to avoid clustering
- Strategic colors: Use colors to encode meaning, not just decoration
- Meaningful connections: Only add edges that clarify relationships
- Test in Obsidian: Verify the output opens correctly
Common Pitfalls to Avoid
- Overlapping nodes (always check distances)
- Inconsistent quote escaping (breaks JSON parsing)
- Missing group labels (causes sidebar navigation issues)
- Too much text in nodes (use file nodes for long content)
- Duplicate IDs (each must be unique)
- Unconnected nodes (unless intentional islands)
1---
2name: obsidian-canvas-creator
3description: Create Obsidian Canvas files from text content, supporting both MindMap and freeform layouts. Use this skill when users want to visualize content as an interactive canvas, create mind maps, or organize information spatially in Obsidian format.
4metadata:
5 source: https://skillmd.com/skills/oldwinter/obsidian-canvas-creator
6---
7
8# Obsidian Canvas Creator
9
10Transform text content into structured Obsidian Canvas files with support for MindMap and freeform layouts.
11
12## When to Use This Skill
13
14- User requests to create a canvas, mind map, or visual diagram from text
15- User wants to organize information spatially
16- User mentions "Obsidian Canvas" or similar visualization tools
17- Converting structured content (articles, notes, outlines) into visual format
18
19## Core Workflow
20
21### 1. Analyze Content
22
23Read and understand the input content:
24- Identify main topics and hierarchical relationships
25- Extract key points, facts, and supporting details
26- Note any existing structure (headings, lists, sections)
27
28### 2. Determine Layout Type
29
30Ask user to choose or infer from context:
31
32**MindMap Layout:**
33- Radial structure from center
34- Parent-child relationships
35- Clear hierarchy
36- Good for: brainstorming, topic exploration, hierarchical content
37
38**Freeform Layout:**
39- Custom positioning
40- Flexible relationships
41- Multiple connection types
42- Good for: complex networks, non-hierarchical content, custom arrangements
43
44### 3. Plan Structure
45
46**For MindMap:**
47- Identify central concept (root node)
48- Map primary branches (main topics)
49- Organize secondary branches (subtopics)
50- Position leaf nodes (details)
51
52**For Freeform:**
53- Group related concepts
54- Identify connection patterns
55- Plan spatial zones
56- Consider visual flow
57
58### 4. Generate Canvas
59
60Create JSON following the Canvas specification:
61
62**Node Creation:**
63- Assign unique 8-12 character hex IDs
64- Set appropriate dimensions based on content length
65- Apply consistent color schemes
66- Ensure no coordinate overlaps
67
68**Edge Creation:**
69- Connect parent-child relationships
70- Use appropriate arrow styles
71- Add labels for complex relationships
72- Choose line styles (straight for hierarchy, curved for cross-references)
73
74**Grouping (Optional):**
75- Create visual containers for related nodes
76- Use subtle background colors
77- Add descriptive labels
78
79### 5. Apply Layout Algorithm
80
81**MindMap Layout Calculations:**
82
83Refer to `references/layout-algorithms.md` for detailed algorithms. Key principles:
84
85- Center root at (0, 0)
86- Distribute primary nodes radially
87- Space secondary nodes based on sibling count
88- Maintain minimum spacing: 320px horizontal, 200px vertical
89
90**Freeform Layout Principles:**
91
92- Start with logical groupings
93- Position groups with clear separation
94- Connect across groups with curved edges
95- Balance visual weight across canvas
96
97### 6. Validate and Output
98
99Before outputting:
100
101**Validation Checklist:**
102- All nodes have unique IDs
103- No coordinate overlaps (check distance > node dimensions + spacing)
104- All edges reference valid node IDs
105- Groups (if any) have labels
106- Colors use consistent format (hex or preset numbers)
107- JSON is properly escaped (Chinese quotes: 『』 for double, 「」 for single)
108
109**Output Format:**
110- Complete, valid JSON Canvas file
111- No additional explanation text
112- Directly importable into Obsidian
113
114## Node Sizing Guidelines
115
116**Text Length-Based Sizing:**
117- Short text (<30 chars): 220 × 100 px
118- Medium text (30-60 chars): 260 × 120 px
119- Long text (60-100 chars): 320 × 140 px
120- Very long text (>100 chars): 320 × 180 px
121
122## Color Schemes
123
124**Preset Colors (Recommended):**
125- `"1"` - Red (warnings, important)
126- `"2"` - Orange (action items)
127- `"3"` - Yellow (questions, notes)
128- `"4"` - Green (positive, completed)
129- `"5"` - Cyan (information, details)
130- `"6"` - Purple (concepts, abstract)
131
132**Custom Hex Colors:**
133Use for brand consistency or specific themes. Always use uppercase format: `"#4A90E2"`
134
135## Critical Rules
136
1371. **Quote Handling:**
138 - Chinese double quotes → 『』
139 - Chinese single quotes → 「」
140 - English double quotes → `\"`
141
1422. **ID Generation:**
143 - 8-12 character random hex strings
144 - Must be unique across all nodes and edges
145
1463. **Z-Index Order:**
147 - Output groups first (bottom layer)
148 - Then subgroups
149 - Finally text/link nodes (top layer)
150
1514. **Spacing Requirements:**
152 - Minimum horizontal: 320px between node centers
153 - Minimum vertical: 200px between node centers
154 - Account for node dimensions when calculating
155
1565. **JSON Structure:**
157 - Top level contains only `nodes` and `edges` arrays
158 - No extra wrapping objects
159 - No comments in output
160
161## Examples
162
163### Simple MindMap Request
164User: "Create a mind map about solar system planets"
165
166Process:
1671. Identify center: "Solar System"
1682. Primary branches: Inner Planets, Outer Planets, Dwarf Planets
1693. Secondary nodes: Individual planets with key facts
1704. Apply radial layout
1715. Generate JSON with proper spacing
172
173### Freeform Content Request
174User: "Turn this article into a canvas" + [article text]
175
176Process:
1771. Extract article structure (intro, body sections, conclusion)
1782. Identify key concepts and relationships
1793. Group related sections spatially
1804. Connect with labeled edges
1815. Apply freeform layout with clear zones
182
183## Reference Documents
184
185- **Canvas Specification**: `references/canvas-spec.md` - Complete JSON Canvas format specification
186- **Layout Algorithms**: `references/layout-algorithms.md` - Detailed positioning algorithms for both layout types
187
188Load these references when:
189- Need specification details for edge cases
190- Implementing complex layout calculations
191- Troubleshooting validation errors
192
193## Tips for Quality Canvases
194
1951. **Keep text concise**: Each node should be scannable (<2 lines preferred)
1962. **Use hierarchy**: Group by importance and relationship
1973. **Balance the canvas**: Distribute nodes to avoid clustering
1984. **Strategic colors**: Use colors to encode meaning, not just decoration
1995. **Meaningful connections**: Only add edges that clarify relationships
2006. **Test in Obsidian**: Verify the output opens correctly
201
202## Common Pitfalls to Avoid
203
204- Overlapping nodes (always check distances)
205- Inconsistent quote escaping (breaks JSON parsing)
206- Missing group labels (causes sidebar navigation issues)
207- Too much text in nodes (use file nodes for long content)
208- Duplicate IDs (each must be unique)
209- Unconnected nodes (unless intentional islands)