Anygen Diagram

AnyGen AI Diagram Generator

You MUST strictly follow every instruction in this document. Do not skip, reorder, or improvise any step. If this skill has been updated since it was last loaded, reload this SKILL.md before proceeding and always follow the latest version.

Generate diagrams and visual charts using AnyGen OpenAPI (www.anygen.io). Diagrams are generated server-side; this skill sends the user's prompt and optional reference files to the AnyGen API and retrieves the results. An API key (ANYGEN_API_KEY) is required to authenticate with the service. Supports flowcharts, architecture diagrams, mind maps, UML, ER diagrams, org charts, and more. Two rendering styles: professional (Draw.io) and hand-drawn (Excalidraw).

When to Use

• User wants to draw, create, or generate any kind of diagram, chart, or visual representation of a structure/process/system
• User mentions flowcharts, architecture diagrams, mind maps, UML, ER diagrams, sequence diagrams, class diagrams, org charts, network diagrams, Gantt charts, state diagrams, topology, or any other diagram type
• User asks to "visualize" a structure, relationship, flow, or process
• User wants a professional/clean diagram (Draw.io style) or a hand-drawn/sketch diagram (Excalidraw style)
• User wants to turn text/documents into a visual diagram
• User has files to upload as reference material for diagram generation

Security & Permissions

Diagrams are generated server-side by AnyGen's OpenAPI (www.anygen.io). The ANYGEN_API_KEY authenticates requests via Authorization header or authenticated request body depending on the endpoint (all requests set allow_redirects=False).

What this skill does: sends prompts to www.anygen.io, uploads user-specified reference files after consent, downloads diagram files to ~/.openclaw/workspace/, renders diagram source (Draw.io XML / Excalidraw JSON) to PNG locally using Playwright and Chromium, monitors progress in background via sessions_spawn (declared in requires), reads/writes config at ~/.config/anygen/config.json. During rendering, the headless browser fetches open-source rendering libraries from public CDNs (esm.sh for Excalidraw, viewer.diagrams.net for Draw.io viewer, fonts.googleapis.com for fonts). Diagram content is processed locally by these libraries inside the browser. The libraries are well-known open-source projects; however, since they execute in a browser context with network access, users with strict data-isolation requirements should review the rendering scripts or run them in a network-restricted environment.

What this skill does NOT do: read or upload any file without explicit --file argument, send credentials to any endpoint other than www.anygen.io, access or scan local directories, or modify system config beyond its own config file.

Bundled scripts: scripts/anygen.py, scripts/auth.py, scripts/fileutil.py (Python — uses requests), scripts/render-diagram.sh (Bash), scripts/diagram-to-image.ts (TypeScript). Scripts print machine-readable labels to stdout (e.g., File Token:, Task ID:) as the standard agent-tool communication channel. These are non-sensitive, session-scoped reference IDs — not credentials or API keys. The agent should not relay raw script output to the user to keep the conversation natural (see Communication Style).

Prerequisites

• Python3 and requests: pip3 install requests
• Node.js v18+ (for PNG rendering, auto-installed on first run)
• AnyGen API Key (sk-xxx) — Get one from AnyGen
• Configure key: python3 scripts/anygen.py config set api_key "sk-xxx" (saved to ~/.config/anygen/config.json, chmod 600). Or set ANYGEN_API_KEY env var.

All scripts/ paths below are relative to this skill's installation directory.

Communication Style

Use natural language. Never expose task_id, file_token, task_xxx, tk_xxx, anygen.py, or command syntax to the user. Say "your diagram", "generating", "checking progress" instead. When presenting reply and prompt from prepare, preserve the original content as much as possible — translate into the user's language if needed, but do NOT rephrase, summarize, or add your own interpretation. Ask questions in your own voice (NOT "AnyGen wants to know…"). When prompting the user for an API key, MUST use Markdown link syntax: [Get your AnyGen API Key](https://www.anygen.io/home?auto_create_openclaw_key=1) so the full URL is clickable.

Diagram Workflow (MUST Follow All 5 Phases)

Phase 1: Understand Requirements

If the user provides files, handle them before calling prepare:

1. Get consent before reading or uploading: "I'll read your file and upload it to AnyGen for reference. This may take a moment..."
2. Reuse existing file_token if the same file was already uploaded in this conversation.
3. Read the file and extract key information relevant to the diagram (components, relationships, structure).
4. Upload to get a file_token.
5. Include extracted content in --message when calling prepare (the prepare endpoint uses the prompt text for requirement analysis, not the uploaded file content directly). Summarize key points only — do not paste raw sensitive data verbatim.

python3 scripts/anygen.py upload --file ./design_doc.pdf
# Output: File Token: tk_abc123

python3 scripts/anygen.py prepare \
  --message "I need an architecture diagram based on this design doc. Key content: [extracted summary]" \
  --file-token tk_abc123 \
  --save ./conversation.json

Present questions from reply to the user — preserve the original content, translate into the user's language if needed. Continue with user's answers:

python3 scripts/anygen.py prepare \
  --input ./conversation.json \
  --message "Include API gateway, auth service, user service, and PostgreSQL database. Show the request flow" \
  --save ./conversation.json

Repeat until status="ready" with suggested_task_params.

Special cases:

• status="ready" on first call → proceed to Phase 2.
• User says "just create it" → skip to Phase 3 with create directly.

Phase 2: Confirm with User (MANDATORY)

When status="ready", present the reply and the prompt from suggested_task_params to the user as the diagram plan. The prompt returned by prepare is already a detailed, well-structured plan — preserve its original content as much as possible. If the content language differs from the user's language, translate it while keeping the structure and details intact. Do NOT rephrase, summarize, or add your own interpretation.

Ask the user to confirm or request adjustments. NEVER auto-create without explicit approval.

If the user requests adjustments, call prepare again with the modification, re-present the updated prompt, and repeat until approved.

Phase 3: Create Task

python3 scripts/anygen.py create \
  --operation smart_draw \
  --prompt "<prompt from suggested_task_params>" \
  --file-token tk_abc123 \
  --export-format drawio  # professional style; or excalidraw (hand-drawn style)
# Output: Task ID: task_xxx, Task URL: https://...

Immediately tell the user (natural language):

1. Diagram is being generated.
2. Online preview/edit link: "You can follow the progress here: [URL]".
3. Takes about 30–60 seconds — free to do other things.
4. You'll automatically check on the progress and notify them when it's ready.