Token导航 LogoToken导航TokenDH.com
效率只读clawhub未标认证来源可访问clear审计通过

drawiodrawio 命令行

Agent Skill

drawio 用于处理数据库查询、表结构、迁移和数据维护任务,适合在 OpenClaw 中需要分析 schema、编写 SQL 或排查数据问题时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

50,729

周安装

2,067

GitHub Stars

4

下载量

16,205
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:drawio(drawio 命令行)
来源仓库:https://github.com/romanmeclazcke/drawio
安装命令:
openclaw skills install drawio
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install drawio

简介

将数据库结构等转换为 draw.io 图表并导出 PNG。

  • 支持 ERD、类图、流程图等多种图形类型生成。
  • 输入 SQL 或表定义即可自动生成可视化文档。
  • 需安装 draw.io 命令行工具作为前置依赖。
  • 输出分辨率可自定义以满足不同展示需求。drawio 属于效率类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

name
drawio
description
Generate professional draw.io diagrams (ERD/database tables, class diagrams, sequence diagrams, flowcharts, architecture diagrams) and export them as PNG. Use when the user requests any kind of diagram, database model, class structure, flow, or system visualization.
metadata
openclaw
requires
bins
["drawio"]

Draw.io Diagram Generation Skill

When to use this skill

  • User requests a database diagram, ERD, or entity-relationship diagram
  • User requests a class diagram or UML class structure
  • User requests a sequence diagram or interaction diagram
  • User requests a flowchart or process flow
  • User requests an architecture diagram or system overview
  • User mentions "draw.io", "diagram", "table", "entity", "class", "sequence", "flow"

⚠️ MANDATORY RULES — READ BEFORE GENERATING ANYTHING

  1. ALWAYS detect the diagram type first before writing any XML
  2. NEVER mix styles between diagram types — each type has its own strict XML structure
  3. ALWAYS assign unique sequential IDs to every mxCell starting from 0
  4. **NEVER use `\

inside a value` attribute** — use separate rows/cells instead

  1. ALWAYS calculate table/class heights correctly using the formulas provided
  2. ALWAYS validate the XML structure before saving
  3. ALWAYS export to PNG and include the PNG in the response before asking about other formats — this step is non-negotiable
  4. NEVER use generic rounded rectangles for database tables or class entities
  5. ALWAYS apply consistent spacing between diagram elements

- Horizontal spacing between elements: minimum 120px - Vertical spacing between rows or steps: minimum 100px - Tables/classes must not overlap - Relationship lines must not cross through table headers


STEP 0 — Diagram Type Detection

Before generating any XML, identify the diagram type from the user's request:

User says...Diagram type
"database", "ERD", "tables", "entities", "foreign key"TYPE 1: ERD
"class", "UML", "inheritance", "attributes", "methods"TYPE 2: Class Diagram
"sequence", "interaction", "lifeline", "actor calls"TYPE 3: Sequence Diagram
"flowchart", "flow", "process", "decision", "steps"TYPE 4: Flowchart
"architecture", "system", "services", "components"TYPE 5: Architecture

Diagram Type References

Use the detailed rules/templates in these files based on the detected type.

  • ERD / Database: ERD.md
  • UML Class: CLASS.md
  • Sequence: SEQUENCE.md
  • Flowchart: FLOWCHART.md
  • Architecture: LAYOUT.md

Generation Workflow — ALWAYS follow this exact order

Step 1 — Identify diagram type

Determine TYPE 1–5 from the user's message before writing any XML.

Step 2 — Plan all elements

List every entity/class/participant and all relationships before coding.

Step 3 — Create output folder

mkdir -p ./diagrams

Step 4 — Write and save the XML

Save to ./diagrams/<diagram-name>.drawio

Mandatory pre-save checklist:

  • [ ] All mxCell elements have unique sequential numeric IDs
  • [ ] ERD tables use shape=table with shape=tableRow rows (never generic shapes)
  • [ ] Class diagrams use swimlane with attribute block, divider line, and method block
  • [ ] Sequence diagrams have lifelines, activation boxes, and correct arrow styles
  • [ ] ERD relationship arrows connect to row cell IDs, not table container IDs
  • [ ] Heights calculated correctly: 30 + (columns x 30) for ERD tables
  • [ ] No literal `\

in value attributes (use &#xa;` for multiline text cells only)

  • [ ] XML is well-formed and all tags are closed

Step 5 — Export to PNG

# macOS
/Applications/draw.io.app/Contents/MacOS/draw.io -x -f png --scale 2 -o ./diagrams/<name>.png ./diagrams/<name>.drawio

# Linux / headless
xvfb-run -a drawio -x -f png --scale 2 -o ./diagrams/<name>.png ./diagrams/<name>.drawio

Step 6 — Verify output

ls -lh ./diagrams/<name>.png

Step 7 — Show PNG first (MANDATORY)

Always respond with the PNG image first (embed/attach it in the response).

Step 8 — Ask the user for delivery format (MANDATORY)

After showing the PNG, ALWAYS ask the user which additional format they want:


The diagram is ready! Which format would you like?

1 - PNG image (ready to view) 2 - .drawio file (editable in draw.io) 3 - SVG (scalable vector) 4 - PDF 5 - All of the above

Reply with the number(s) of your choice.


Then based on the response:

  • 1 → send the PNG file
  • 2 → send the .drawio file
  • 3 → export SVG and send it
  • 4 → export PDF and send it
  • 5 → send all formats
  • Multiple numbers (e.g. "1 2") → send all requested formats

Other export formats

# SVG (scalable vector)
/Applications/draw.io.app/Contents/MacOS/draw.io -x -f svg -o ./diagrams/<name>.svg ./diagrams/<name>.drawio

# PDF
/Applications/draw.io.app/Contents/MacOS/draw.io -x -f pdf -o ./diagrams/<name>.pdf ./diagrams/<name>.drawio

# High-res PNG (scale 3)
/Applications/draw.io.app/Contents/MacOS/draw.io -x -f png --scale 3 -o ./diagrams/<name>_hd.png ./diagrams/<name>.drawio

# Transparent background
/Applications/draw.io.app/Contents/MacOS/draw.io -x -f png -t --scale 2 -o ./diagrams/<name>_transparent.png ./diagrams/<name>.drawio

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

71.08%
按下载量换算11,519

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

未展示

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills