How do I install the Dingtalk Browser Export skill?

Run npx skillmds@latest add stardustai/dingtalk-browser-export in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Dingtalk Browser Export safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Dingtalk Browser Export?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Dingtalk Browser Export free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Dingtalk Browser Export?

stardustai (@stardustai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Dingtalk Browser Export by stardustai

Name: Dingtalk Browser Export
Author: stardustai

Dingtalk Browser Export

Export the currently open DingTalk/Alidocs document from a logged-in Chrome session without relying on the browser save dialog. Use this whenever the user asks to export, download, save, or back up the current DingTalk document to Word (.docx), PDF, or Markdown, especially when Chrome download popups would block automation.

stardustai 71e6af1 3 files · 16.0 KB Updated Sep 17, 2026

File contents

DingTalk Browser Export

Use this skill when the user wants the current DingTalk document from their real Chrome session exported to a local file without getting blocked by the browser's save dialog.

This skill is for the browser-export path, not the OpenAPI path:

Prefer this skill when the user is already logged into DingTalk in Chrome.
Prefer this skill when the user explicitly wants the same export result as DingTalk's web UI.
Do not use this skill for editing document content.

Prerequisites

OpenClaw Chrome extension is installed and connected.
openclaw CLI is available locally.
Chrome already has the target DingTalk document open and visible.
The active relay profile may be chrome-relay or another extension-backed profile; do not assume it is named chrome.

Workflow

Confirm the active Chrome tab is a DingTalk/Alidocs document.
Run the bundled script:

python3 /Users/derek/.agents/skills/dingtalk-browser-export/scripts/export_current_dingtalk.py

If you need to force a specific profile:

python3 /Users/derek/.agents/skills/dingtalk-browser-export/scripts/export_current_dingtalk.py --browser-profile chrome-relay

By default the script exports .docx to /Users/derek/output/doc.
Report the saved file path back to the user.

Format options

Use --format when needed:

python3 /Users/derek/.agents/skills/dingtalk-browser-export/scripts/export_current_dingtalk.py --format pdf
python3 /Users/derek/.agents/skills/dingtalk-browser-export/scripts/export_current_dingtalk.py --format md

Supported values:

docx
pdf
md

Operational notes

The script does not wait for Chrome's save dialog.
It triggers DingTalk's own export job in the page, captures the export result URL, and downloads the generated file directly to a fixed local path.
If the toolbar DOM shifts, rerun once after re-focusing the desired Chrome tab. The script already re-reads the current active tab every run and probes multiple header buttons before failing.

Output

Always return:

the document title
the export format
the saved local path

If export fails, say whether it failed at:

finding the active DingTalk tab
opening the export menu
waiting for the export job result
downloading the generated file

---name: dingtalk-browser-exportdescription: Export the currently open DingTalk/Alidocs document from a logged-in Chrome session without relying on the browser save dialog. Use this whenever the user asks to export, download, save, or back up the current DingTalk document to Word (.docx), PDF, or Markdown, especially when Chrome download popups would block automation.---# DingTalk Browser ExportUse this skill when the user wants the current DingTalk document from their real Chrome session exported to a local file without getting blocked by the browser's save dialog.This skill is for the browser-export path, not the OpenAPI path:- Prefer this skill when the user is already logged into DingTalk in Chrome.- Prefer this skill when the user explicitly wants the same export result as DingTalk's web UI.- Do not use this skill for editing document content.## Prerequisites- OpenClaw Chrome extension is installed and connected.- `openclaw` CLI is available locally.- Chrome already has the target DingTalk document open and visible.- The active relay profile may be `chrome-relay` or another extension-backed profile; do not assume it is named `chrome`.## Workflow1. Confirm the active Chrome tab is a DingTalk/Alidocs document.2. Run the bundled script:```bashpython3 /Users/derek/.agents/skills/dingtalk-browser-export/scripts/export_current_dingtalk.py```If you need to force a specific profile:```bashpython3 /Users/derek/.agents/skills/dingtalk-browser-export/scripts/export_current_dingtalk.py --browser-profile chrome-relay```3. By default the script exports `.docx` to `/Users/derek/output/doc`.4. Report the saved file path back to the user.## Format optionsUse `--format` when needed:```bashpython3 /Users/derek/.agents/skills/dingtalk-browser-export/scripts/export_current_dingtalk.py --format pdfpython3 /Users/derek/.agents/skills/dingtalk-browser-export/scripts/export_current_dingtalk.py --format md```Supported values:- `docx`- `pdf`- `md`## Operational notes- The script does not wait for Chrome's save dialog.- It triggers DingTalk's own export job in the page, captures the export result URL, and downloads the generated file directly to a fixed local path.- If the toolbar DOM shifts, rerun once after re-focusing the desired Chrome tab. The script already re-reads the current active tab every run and probes multiple header buttons before failing.## OutputAlways return:- the document title- the export format- the saved local pathIf export fails, say whether it failed at:- finding the active DingTalk tab- opening the export menu- waiting for the export job result- downloading the generated file

Frequently asked questions