excaliclaw

Create Excalidraw diagrams with export-ready editability metadata.

4|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/nickytonline/skills --skill excaliclaw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: excaliclaw
Source: https://github.com/nickytonline/skills/tree/main/excaliclaw
Command: npx skills add https://github.com/nickytonline/skills --skill excaliclaw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create diagrams with the Excalidraw MCP in a way that survives OpenClaw rendering and Excalidraw export.

Core Features & Use Cases

  • Provides a reliable workflow for diagram creation that remains editable in Excalidraw after export.
  • Supports architecture/system diagrams, flowcharts, and hand-drawn style visuals that are export-ready.
  • Use case: design an API system diagram and export a ready-to-share Excalidraw scene.

Quick Start

Describe the target architecture and request a ready-to-export Excalidraw diagram for your API or system.

Frequently Asked Questions about excaliclaw

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I export Excalidraw diagrams without losing editability metadata?

Excalidraw diagrams retain editability when you enforce a workflow that preserves containerId, boundElements, and startBinding/endBinding metadata while avoiding MCP-only elements. This ensures architecture diagrams and flowcharts remain fully editable after the export process completes.

What is the best way to create architecture diagrams that survive OpenClaw rendering?

Architecture diagrams survive OpenClaw rendering by starting with a preview via create_view, then exporting a full Excalidraw scene via export_to_excalidraw. This workflow guarantees system maps and flowcharts render clearly and remain editable in Excalidraw.

Why does my Excalidraw export break container and binding connections?

Excalidraw exports break connections when MCP-only elements are used or when editability metadata like containerId and boundElements is not preserved. Following a strict export_to_excalidraw workflow prevents these binding and connection losses.

Can I use the Excalidraw MCP to generate API system diagrams for OpenClaw?

Yes, you can use the Excalidraw MCP to design API system diagrams for OpenClaw. The workflow generates a ready-to-share Excalidraw scene by previewing the system map first and then exporting it with all structural metadata intact.

Does the Excalidraw export workflow support hand-drawn style flowcharts?

Yes, the Excalidraw export workflow supports hand-drawn style flowcharts and visuals. It enforces a reliable creation process that keeps the hand-drawn aesthetic intact while ensuring the exported scene remains fully editable in Excalidraw.