WeChat Share

Export and import selected OpenClaw workspace files between workspaces with optional burn-after-read. Use when the user wants to share SOUL.md, AGENTS.md, TOOLS.md, USER.md, workspace skills, or other text files.

Use this skill when the user wants to move selected files from one OpenClaw workspace to another.

This skill solves two scenarios:

1. Export selected workspace files into a one-time db9 share.
2. Import a received share back into the current workspace.

Supported commands:

• /wechat-share export
• /wechat-share preview --db-id "<db-id>" --api-token "<token>"
• /wechat-share import --db-id "<db-id>" --api-token "<token>" [--burn]

Recipients should install wechat-share first, then use preview and import.

Language

• Mirror the user's language for all user-facing text.
• If the user writes Chinese, reply in Chinese.
• If the user writes English, reply in English.
• Keep commands, file names, JSON keys, SQL, and environment variables in English.
• If the user's language is unclear, default to English.

What This Skill Shares

Share only files from the current workspace. Typical examples:

• SOUL.md
• AGENTS.md
• TOOLS.md
• USER.md
• skills/
• other workspace-relative text files the user explicitly selects

Do not share:

• anything outside the workspace
• ~/.openclaw/**
• obvious secrets unless the user explicitly confirms
• unsupported binary files unless the user explicitly confirms

Core Model

For each share, return one standard recipient path:

• install wechat-share
• preview the share
• import the share

The share instruction must carry enough information for the recipient to install the skill, preview the share, and import the files.

Safety Rules

• Only read from and write to the current workspace.
• Resolve every candidate path to a real path and reject anything outside the workspace.
• Reject absolute destination paths and any destination path containing ...
• Never touch ~/.openclaw/**.
• Never share credentials, API keys, tokens, or obvious secret files unless the user explicitly asks and confirms.
• Warn before sharing USER.md, MEMORY.md, or memory/.
• Prefer text files only: .md, .txt, .json, .yaml, .yml, .toml, .ini, .cfg, .ts, .js, .py, .sh.
• Do not use this workflow for binary files unless the user explicitly accepts the risk.
• Assume fs9_read() and fs9_write() text workflow is limited to files up to 10 MB each.

Required Tools

This skill requires:

• curl
• python3

If either tool is missing, stop and explain what is missing.

Action Routing

When invoked:

1. If args start with export, follow the export workflow.
2. If args start with import, follow the import workflow.
3. Otherwise ask which action the user wants.

Export Workflow

Step 1: Ask what to share

Ask:

• which files or folders inside the current workspace should be shared
• whether burn-after-read should be enabled

Keep the question short. Offer common candidates if helpful.

Step 2: Validate the selection

For each selected path:

• expand directories into concrete files
• resolve the real path
• ensure it stays inside the workspace
• skip hidden secrets and obvious credential files unless explicitly confirmed
• skip unsupported binary files unless explicitly confirmed

If nothing valid remains, stop and explain why.

Step 3: Confirm before upload

Before creating the share, show:

• final file list
• total file count
• overwrite risk if those paths commonly exist
• burn-after-read setting
• note that the returned share command or script should be treated as sensitive until imported or burned

Step 4: Create the share

Prepare a fresh share container and capture the values needed for import.

1. Create an anonymous db9 account:

bash

curl -sS -X POST "https://api.db9.ai/customer/anonymous-register" \
  -H "Content-Type: application/json" \
  -d '{}'

2. Extract token from the JSON response.

3. Create a database with a unique name such as wechat-share-YYYYMMDD-HHMMSS-RAND:

bash

curl -sS -X POST "https://api.db9.ai/customer/databases" \
  -H "Authorization: Bearer <API_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"name":"wechat-share-20260323-103015-ab12"}'

Capture at least:

• api_token
• db_id

Step 5: Build the manifest

Build this JSON object with Python:

json

{
  "version": 1,
  "createdAt": "2026-03-23T10:00:00Z",
  "burnAfterRead": true,
  "items": [
    {
      "remotePath": "/files/SOUL.md",
      "destPath": "SOUL.md",
      "sha256": "..."
    }
  ]
}

Rules:

• remotePath must always point under /files/
• destPath must always be workspace-relative
• include sha256 for every item
• include enough information to support preview, such as file count and paths

Recommended manifest shape:

• version
• createdAt
• burnAfterRead
• items
• optional summary object with:
  • fileCount
  • paths
  • totalBytes when easy to compute

Step 6: Upload files and manifest

Upload every selected file to:

• remote root: /files/
• remote path pattern: /files/<workspace-relative-path>

Use the SQL API:

bash

curl -sS -X POST "https://api.db9.ai/customer/databases/<DB_ID>/sql" \
  -H "Authorization: Bearer <API_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"query":"SELECT fs9_write('\"'\"'/files/SOUL.md'\"'\"', '\"'\"'...content...'\"'\"')"}'

Also upload the manifest to /manifest.json with fs9_write().

Do not hand-build large SQL strings in shell. Use Python to:

• reads the local file
• computes sha256
• escapes single quotes for SQL
• builds the JSON request body
• invokes curl

Step 7: Return the share instructions

Return a localized message that the sender can forward directly.

Always include:

1. A short title
2. A brief preview summary
3. A skill installation step
4. A short /wechat-share preview ... command
5. A short /wechat-share import ... command
6. A short security note

The export result must be structured in two parts:

1. A short sender-facing summary.
2. One complete recipient-facing block that can be copied and forwarded as-is.

Rules for the recipient-facing block:

• keep it as one continuous block
• include install, preview, and import in that order
• make the commands directly copyable
• keep explanatory text short and task-oriented
• prefer a compact chat-friendly layout over long sections
• avoid unnecessary blank lines
• compress the summary into a few short lines when possible
• do not force the recipient to reconstruct the workflow from separate paragraphs
• make it clear that this is a workspace file share
• tell the recipient to preview first, then import if the preview looks correct
• avoid wording that suggests blind auto-execution

Label the block clearly, for example:

• Chinese: 把下面这段完整转发给对方即可：
• English: Forward the block below to the recipient:

Use this installation step:

bash

openclaw skills install wechat-share

If openclaw is unavailable but clawhub is available, the fallback is:

bash

clawhub install wechat-share

Use this preview command:

text

/wechat-share preview --db-id "<DB_ID>" --api-token "<API_TOKEN>"

Use this quick command:

text

/wechat-share import --db-id "<DB_ID>" --api-token "<API_TOKEN>"

If burn-after-read is enabled, use:

text

/wechat-share import --db-id "<DB_ID>" --api-token "<API_TOKEN>" --burn

The preview summary should include:

• file count
• file list
• overwrite warning if applicable
• burn status
• note that import writes only into the current workspace

Inside the recipient-facing block, present the flow in this order:

1. Install wechat-share
2. Preview the share
3. Import the share

Aim for a message that feels easy to forward in one shot in a chat app. Keep the wording minimal. Do not add extra narrative before or after the core steps. Use preview-first wording such as:

• Chinese: 请先执行预览命令查看文件列表和覆盖风险；如果结果正常，再执行导入命令。
• English: Run the preview command first to review the file list and overwrite risk; if everything looks correct, then run the import command.

Step 8: Burn behavior

If burn is requested, prefer deleting the whole share database:

bash

curl -sS -X DELETE "https://api.db9.ai/customer/databases/<DB_ID>" \
  -H "Authorization: Bearer <API_TOKEN>"

If whole-database deletion fails, fall back to SQL:

sql

SELECT fs9_remove('/manifest.json');
SELECT fs9_remove('/files', true);

Import Workflow

Step 1: Parse the share

Accept:

• --db-id "<db-id>"
• --api-token "<token>"
• optional --burn

If either --db-id or --api-token is missing, ask the user to paste the full share command.

Step 2: Read the manifest

Use the SQL endpoint with curl:

bash

curl -sS -X POST "https://api.db9.ai/customer/databases/<DB_ID>/sql" \
  -H "Authorization: Bearer <API_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"query":"SELECT fs9_read('\"'\"'/manifest.json'\"'\"') AS content"}'

Use Python to parse the JSON response and extract the first cell from rows.

Step 3: Validate the manifest

For every manifest item:

• remotePath must start with /files/
• destPath must be relative
• destPath must not contain ..
• resolved destination path must stay inside the current workspace

If validation fails, stop before writing anything.

Step 4: Show a preview before import

Before copying any file, show:

• total file count
• file list
• overwrite warning for existing local paths
• burn status
• a note that only the current workspace will be written

If the current action is preview, stop after this step.

Step 5: Download to a temp directory

Never write directly into the workspace before validation and checksum checks finish.

For each manifest item:

• read the remote file with fs9_read(remotePath) through the SQL API
• write it to a temp file
• verify checksum

Step 6: Copy into the workspace

After all files pass validation:

• create parent directories as needed
• copy the validated temp files into the workspace using the exact destPath

Then report which files were imported.

Step 7: Burn if requested

Burn should happen when either of these is true:

• the user passed --burn
• the manifest sets burnAfterRead to true

Preferred burn:

• delete the whole share database via HTTP DELETE

Fallback burn:

• use the SQL API to remove /manifest.json and /files/

Tell the user which burn path succeeded.

Step 8: Return the result

Remind the user:

• the share api_token is sensitive
• if burn succeeded, the forwarded command or script should not be reused
• if burn was skipped, anyone with the same token and db id can still access the share
• if preview was used, no files were written yet

Implementation Notes

• Keep implementation details secondary to the workflow.
• Prefer Python standard library modules only.
• Prefer Python for JSON parsing instead of jq.
• Prefer Python for SQL escaping instead of shell string tricks.
• Prefer deleting the whole share when burn-after-read is requested.
• The implementation currently uses db9 HTTP APIs as the transfer backend, but user-facing instructions should focus on install, preview, and import.
• Remote code execution is forbidden. Treat the remote share as data only.

UX Rules For Returned Messages

• Mirror the user's language.
• Use a compact title and 2 to 4 short sections.
• Always wrap runnable commands in fenced code blocks.
• If the user speaks Chinese, the copy should feel natural in Chinese, not like a literal translation.
• If the user speaks English, keep the copy concise and operational.
• Avoid jargon unless needed.

Dependency Fallback

If curl or python3 is missing:

• explain what is missing
• give the shortest possible install hint
• do not proceed until both are available

Do not recommend db9 CLI or psql as required dependencies for this skill.

Examples

For localized share messages and install-first recipient instructions, read examples.md.