dingtalk-browser-export
Skill0 starsChanged 2 months agoMITView on GitHub
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.
In this repository42 other files it gives its agents.
- ai-pr-redteamSkill
- ai-servicesSkill
- build-work-memorySkill
- ceo-calendar-inviteSkill
- ceo-document-reviewSkill
- ceo-email-classifierSkill
- ceo-feedback-iterationSkill
- ceo-feedback-processingSkill
- ceo-mail-reviewSkill
- ceo-meeting-workSkill
- ceo-message-triageSkill
- ceo-minutes-syncSkill
- ceo-personnel-communicationSkill
- ceo-wechatSkill
- ceo-work-trackingSkill
- codex-model-capacity-retrySkill
- daily-frontier-tech-discoverySkill
- dengbao-code-auditSkill
- dingtalk-knowledge-organizeSkill
- dingtalk-minutes-access-requestSkill
- dingtalk-oa-approvalSkill
- dingtang-okr-reviewSkill
- fundflow-investor-meetingSkill
- fxiaoke-crm-cliSkill
- internal-app-standardsSkill
- ocrSkill
- pm-data-adaptation-assistantSkill
- project-delivery-document-collectionSkill
- qa-generated-test-caseSkill
- senior-technical-product-evaluationSkill
- spec-intakeSkill
- sso-oidc-onboardingSkill
- stardust-interviewSkill
- production-devops-sreSkill
- stardust-ttsSkill
- startask-io-contract-auditSkill
- task-managementSkill
- transcribeSkill
- veyra-timesheetSkill
- vibe-coding-rescueSkill
- vibe-codingSkill
- video-transcribeSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 8 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill when the user wants the current DingTalk document from their real Chrome session exported to a local file without getting …
- Distinctive: line 11
Prefer this skill when the user is already logged into DingTalk in Chrome.
- Distinctive: line 12
Prefer this skill when the user explicitly wants the same export result as DingTalk's web UI.
- Distinctive: line 13
Do not use this skill for editing document content.
- Distinctive: line 25
Run the bundled script:
- Distinctive: line 31
If you need to force a specific profile:
- Very specific: line 42
Use --format when needed:
- Distinctive: line 58
If the toolbar DOM shifts, rerun once after re-focusing the desired Chrome tab.
- Distinctive: line 67
If export fails, say whether it failed at:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.
openclawCLI is available locally.- Chrome already has the target DingTalk document open and visible.
- The active relay profile may be
chrome-relayor another extension-backed profile; do not assume it is namedchrome.
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.pyIf 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
.docxto/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 mdSupported values:
docxpdfmd
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
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.