Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Generate diagrams from descriptions with Mermaid, PlantUML, or ASCII for architecture, flows, sequences, and data models.
Generate diagrams from descriptions with Mermaid, PlantUML, or ASCII for architecture, flows, sequences, and data models.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Diagrams should clarify, not complicate. Start simple, add detail only when needed. A 5-box flowchart beats a 50-node sprawl.
Identify diagram type โ Is this a flow, architecture, sequence, or data model? Choose format โ Mermaid (default), PlantUML (complex), ASCII (inline), SVG (custom) Draft minimal version โ Core elements only, no decoration Iterate โ Add detail based on feedback
TypeUse ForFormatFlowchartProcesses, decisions, workflowsMermaid flowchartSequenceAPI calls, interactions, protocolsMermaid sequenceDiagramArchitectureSystem components, infrastructureMermaid flowchart or C4ER/Data modelDatabase schemas, relationshipsMermaid erDiagramClassObject structure, inheritanceMermaid classDiagramStateLifecycles, status transitionsMermaid stateDiagram-v2TimelineProject phases, historyMermaid timelineMindmapBrainstorming, concept mappingMermaid mindmap
MethodWhenMermaid code blockUser can render (docs, GitHub, Notion)Render to PNG/SVGUser needs image fileASCII inlineQuick sketch in chatHTML + Mermaid.jsInteractive viewing
# Using mmdc (mermaid-cli) npx -y @mermaid-js/mermaid-cli mmdc -i diagram.mmd -o diagram.png -b transparent # Or via browser tool # Write HTML with Mermaid, screenshot the rendered diagram
Flowchart: flowchart LR A[Start] --> B{Decision} B -->|Yes| C[Action] B -->|No| D[End] Sequence: sequenceDiagram User->>API: Request API->>DB: Query DB-->>API: Result API-->>User: Response ER Diagram: erDiagram USER ||--o{ ORDER : places ORDER ||--|{ ITEM : contains
Left-to-right (LR) for processes, top-to-bottom (TB) for hierarchies Max 10-15 nodes per diagram, split if larger Consistent naming โ all caps for systems, lowercase for actions Subgraphs to group related components Color sparingly โ highlight critical paths only
RequestInterpret As"Draw my API flow"Sequence diagram: client โ API โ services"Show the architecture"Flowchart with subgraphs for components"Database schema"ER diagram with relationships"How the auth works"Sequence or flowchart depending on complexity"User journey"Flowchart with decision points
โ Too many nodes (split into multiple diagrams) โ Decorative icons without meaning โ Mixing abstraction levels (database tables next to business concepts) โ Arrows in all directions (confuses flow) โ Labels too long (use short names, add legend if needed)
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.