You MUST strictly follow every instruction in this document. Do not skip, reorder, or improvise any step.

• Deep Research — Long-form research reports and industry analysis
• Slide / PPT — Professional presentations with multiple style templates
• Doc / DOCX — Intelligent document generation and formatting
• Website — Rapid web page creation
• Data Analysis — Data analysis and visualization
• Image — AI image generation
• Storybook — Storybook style visuals creation
• SmartDraw — Diagram generation (professional / hand-drawn style)

• Sends task prompts and parameters to

  www.anygen.io

• Uploads user-provided reference files to

  www.anygen.io

  after obtaining consent
• Downloads generated files (slides, documents, diagrams) to

  ~/.openclaw/workspace/

• Renders diagram source files to PNG locally using Chromium (auto-installed on first run)
• Reads/writes API key config at

  ~/.config/anygen/config.json

• Upload files without informing the user and obtaining consent
• Send your API key to any endpoint other than

  www.anygen.io

• Modify system configuration beyond

  ~/.config/anygen/config.json

scripts/anygen.py

scripts/render-diagram.sh

scripts/diagram-to-image.ts

• Python3 and

  requests

  :

  pip3 install requests

• Node.js v18+ (for SmartDraw PNG rendering, auto-installed on first run)
• AnyGen API Key (

  sk-xxx

  ) — Get one → Setting → Integration
• Configure once:

  python3 scripts/anygen.py config set api_key "sk-xxx"

All

scripts/

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

sessions_spawn

status

poll

1. create

   → get

   task_id

   and

   task_url

   .
2. Tell user: (a) generation started, (b) the online link, (c) ~10–15 min, free to do other things.
3. Launch background monitor via

   sessions_spawn

   (Phase 4). Do NOT announce this to the user.
4. Continue the conversation — do NOT wait.
5. The background monitor handles sending preview/result and notifying the user directly, then replies

   ANNOUNCE_SKIP

   so the main session does NOT relay anything further.

• Technical identifiers:

  task_id

  ,

  file_token

  ,

  task_xxx

  ,

  tk_xxx

• API/system terms:

  API

  ,

  OpenAPI

  ,

  create

  ,

  poll

  ,

  status

  ,

  query

• Infrastructure terms:

  sub-agent

  ,

  subagent

  ,

  background process

  ,

  spawn

  ,

  sessions_spawn

• Script/code references:

  anygen.py

  ,

  scripts/

  , command-line syntax, JSON output

• "Your file has been uploaded" (NOT "file_token=tk_xxx received")
• "I'm generating your content now" (NOT "Task task_xxx created")
• "You can view your results here: [URL]" (NOT "Task URL: ...")
• "I'll let you know when it's ready" (NOT "Spawning a sub-agent to poll")

• You may mention AnyGen as the service when relevant.
• Ask questions in your own voice. Do NOT use a relaying tone like "AnyGen wants to know…".

prepare

1. Read the file yourself. Extract key information relevant to the task.
2. Reuse existing

   file_token

   if the same file was already uploaded in this conversation.
3. Get consent before uploading: "I'll upload your file to AnyGen for reference."
4. Upload to get a

   file_token

   .
5. Include extracted content in

   --message

   when calling

   prepare

   (the API does NOT read files internally).

python3 scripts/anygen.py upload --file ./reference.pdf

Present questions from `reply` naturally. Continue with user's answers:

```bash
python3 scripts/anygen.py prepare \
  --input ./conversation.json \
  --message "Focus on generative AI and enterprise adoption" \
  --save ./conversation.json

status="ready"

suggested_task_params

• status="ready"

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

  create

  directly.

• For

  smart_draw

  : describe the diagram type, components, and relationships. Do NOT paste raw file contents — files are processed server-side.
• For

  chat

  /

  data_analysis

  /

  website

  /

  storybook

  : include extracted file content in

  --message

  since the API does NOT read files.

Requires

sessions_spawn

. If unavailable, skip to Fallback below.

sessions_spawn

sessions_spawn(
    prompt=<subagent prompt below>,
    runTimeoutSeconds=1500  # REQUIRED: 25 minutes (1500s) to cover 20-min poll + buffer
)

timeout

maxDuration

{...}

You are a background monitor for an AnyGen content generation task.
You MUST strictly follow every instruction below. Do not skip, reorder, or improvise any step.

Task ID: {task_id}
Task URL: {task_url}
Operation: {operation}
Script: {script_path}
Render Script: {render_script_path}
Export Format: {export_format}
Thumbnail Output: {thumbnail_output_dir}
User Language: {user_language}

IMPORTANT: This monitoring task may take up to 20 minutes. Ensure your execution timeout is at least 25 minutes.

CRITICAL RULES:
- You MUST reply in {user_language}.
- After completing ALL steps (including sending messages to the user), your FINAL reply
  MUST be EXACTLY "ANNOUNCE_SKIP" — nothing else. This prevents the main session from
  sending duplicate messages.
- Do NOT say anything beyond what is specified below. No greetings, no extra commentary.
- NEVER include technical terms like "task_id", "file_token", "poll", "sub-agent",
  "API", "script", "workspace", "downloaded to", file paths, or status labels
  in any message to the user.

Your job depends on the operation type:

1. Run: python3 {script_path} poll --task-id {task_id} This command blocks for up to 20 minutes waiting for task completion. Do NOT pass --output — the file will only be downloaded when the user requests it.
2. On success: a. Download thumbnail: python3 {script_path} thumbnail --task-id {task_id} --output {thumbnail_output_dir} b. Send the thumbnail preview image to the user. Choose the correct method:
   • Feishu/Lark: Two-step process via OpenAPI — Step 1 (Upload image): POST https://open.feishu.cn/open-apis/im/v1/images curl -X POST 'https://open.feishu.cn/open-apis/im/v1/images'
     -H 'Authorization: Bearer <tenant_access_token>'
     -F 'image_type=message'
     -F 'image=@{thumbnail_output_dir}/thumbnail.png' This returns an image_key. Step 2 (Send image message): POST https://open.feishu.cn/open-apis/im/v1/messages?receive_id_type=chat_id Request body: { "receive_id": "<chat_id>", "msg_type": "image", "content": "{"image_key":"<image_key>"}" }
   • Other platforms: Send via message tool with filePath. c. Send a text message to the user (in {user_language}, natural tone): "Your content is ready! If you'd like me to send you the file, just let me know." d. Reply EXACTLY: ANNOUNCE_SKIP

1. Run: python3 {script_path} poll --task-id {task_id} --output ~/.openclaw/workspace/ This command blocks for up to 20 minutes waiting for task completion.
2. On success: a. Get the local file path from [RESULT] Local file: line. b. Render to PNG:
   • For drawio: bash {render_script_path} drawio <local_file> <local_file_without_ext>.png
   • For excalidraw: bash {render_script_path} excalidraw <local_file> <local_file_without_ext>.png c. Send the rendered PNG image to the user. Choose the correct method:
   • Feishu/Lark: Two-step process via OpenAPI — Step 1 (Upload image): POST https://open.feishu.cn/open-apis/im/v1/images curl -X POST 'https://open.feishu.cn/open-apis/im/v1/images'
     -H 'Authorization: Bearer <tenant_access_token>'
     -F 'image_type=message'
     -F 'image=@<local_file_without_ext>.png' This returns an image_key. Step 2 (Send image message): POST https://open.feishu.cn/open-apis/im/v1/messages?receive_id_type=chat_id Request body: { "receive_id": "<chat_id>", "msg_type": "image", "content": "{"image_key":"<image_key>"}" }
   • Other platforms: Send via message tool with filePath. d. Send a text message to the user (in {user_language}, natural tone): "Your diagram is ready! You can view and edit it online here: {task_url}" e. Reply EXACTLY: ANNOUNCE_SKIP f. If rendering fails: Send text: "The diagram has been generated but I couldn't render a preview. You can view and edit it here: {task_url}" Reply EXACTLY: ANNOUNCE_SKIP

1. Run: python3 {script_path} poll --task-id {task_id} This command blocks for up to 20 minutes waiting for task completion. No --output needed — results are viewed online.
2. On success: a. Send a text message to the user (in {user_language}, natural tone): "Your content is ready! You can view it here: {task_url}" b. Reply EXACTLY: ANNOUNCE_SKIP

• On failure: a. Send a text message to the user (in {user_language}): "Unfortunately the generation didn't complete successfully. You can check the details here: {task_url}" b. Reply EXACTLY: ANNOUNCE_SKIP
• On timeout (20 min): a. Send a text message to the user (in {user_language}): "The generation is taking a bit longer than expected. You can check the progress here: {task_url}" b. Reply EXACTLY: ANNOUNCE_SKIP

Do NOT wait for the background monitor. Do NOT tell the user you launched it.

**Handling the completion event.** The background monitor sends preview/result and notification to the user directly. It replies `ANNOUNCE_SKIP` as its final output, which means the main session should NOT relay or duplicate any message. If you receive a completion event with `ANNOUNCE_SKIP`, simply ignore it — the user has already been notified.

python3 {script_path} download --task-id {task_id} --output ~/.openclaw/workspace/

• Feishu/Lark: Two-step process via OpenAPI — Step 1 (Upload file):

  POST https://open.feishu.cn/open-apis/im/v1/files

  curl -X POST 'https://open.feishu.cn/open-apis/im/v1/files' \
    -H 'Authorization: Bearer <tenant_access_token>' \
    -F 'file_type=stream' \
    -F 'file=@~/.openclaw/workspace/<output_file>' \
    -F 'file_name=<output_file>'

  This returns a

  file_key

  . (Note: use

  file_type="ppt"

  for PPTX,

  file_type="stream"

  for DOCX.) Step 2 (Send file message):

  POST https://open.feishu.cn/open-apis/im/v1/messages?receive_id_type=chat_id

  json

  {
    "receive_id": "<chat_id>",
    "msg_type": "file",
    "content": "{\"file_key\":\"<file_key>\"}"
  }

• Other platforms: Send via message tool with filePath.

• Maximum execution time per task is 20 minutes (customizable via

  --max-time

  )
• Download link is valid for 24 hours
• Single attachment file should not exceed 10MB (after Base64 encoding)
• Polling interval is 3 seconds
• SmartDraw local rendering requires Chromium (auto-installed on first run)