Menu
Use when an idea, workflow, topology, or boundary is easier to explain visually than in prose. Create simple diagrams, maps, or structured visual explanations that improve alignment and handoff quality.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when Wendy is onboarding a brand-new OpenClaw agent, defining a fresh role before first use, or preparing a new agent environment with canonical profile files, SOP ownership, skills assignment, and runtime setup. Use for new agent initialization only. Do not use for re-onboarding, legacy migration, or historical cleanup.
Use when new notes, inputs, or research items need to be connected into an existing knowledge graph or operating context. Helps turn scattered information into structure, patterns, and useful links.
| name | canvas-communication |
| description | Use when an idea, workflow, topology, or boundary is easier to explain visually than in prose. Create simple diagrams, maps, or structured visual explanations that improve alignment and handoff quality. |
Use visual structure when plain text is too abstract.
Treat this as a baseline communication capability, not a niche diagram tool.
Every agent should be able to switch from prose to visual explanation when that improves alignment, speed, or decision quality.
Do not draw for decoration.
Draw only when the visual makes the logic easier to understand.
Prefer compact visuals:
The visual should clarify the system, not add noise.
If a human would understand the system faster by seeing it than by reading it, use this skill.
Do not wait for a separate request for a diagram when the structure is the message.
