canvas-communication
Skill1 starsChanged 8 months agoMITView on GitHub
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.
In this repository5 other files it gives its agents.
- agent-onboardingSkill
- brainstormingSkill
- connect-the-dotsSkill
- verification-before-completionSkill
- writing-plansSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use visual structure when plain text is too abstract.
- Distinctive: line 10
Treat this as a baseline communication capability, not a niche diagram tool.
- Distinctive: line 12
Every agent should be able to switch from prose to visual explanation when that improves alignment, speed, or decision quality.
- Distinctive: line 27
Do not draw for decoration.
- Distinctive: line 46
If a human would understand the system faster by seeing it than by reading it, use this skill.
- Distinctive: line 48
Do not wait for a separate request for a diagram when the structure is the message.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Canvas Communication
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.
When To Use
- topology explanation
- architecture boundary explanation
- workflow and SOP mapping
- handoff diagrams
- company and role structure
- skill-package activation maps
- before / after comparisons
- scope and ownership diagrams
Core Rule
Do not draw for decoration.
Draw only when the visual makes the logic easier to understand.
Output Standard
Prefer compact visuals:
- box-and-arrow diagrams
- layered maps
- step flows
- role-to-SOP mappings
- skill-to-workflow maps
- interactive canvases when needed
The visual should clarify the system, not add noise.
Default Expectation
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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.