Access DingTalk documents and knowledge spaces through the DingTalk document MCP. Use this skill whenever the user selects a DingTalk knowledge space, folder, or document.
Scanned 8/31/2026
Install to Claude Code
Skills Directorynpx -y skills add wecode-ai/Wegent --skill dingtalk-docs --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Dingtalk Docs?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/wecode-ai-dingtalk-docs)More formats (shields.io, HTML) on the badges page.
---
description: "Access DingTalk documents and knowledge spaces through the DingTalk document MCP. Use this skill whenever the user selects a DingTalk knowledge space, folder, or document."
displayName: "钉钉文档"
version: "1.0.0"
author: "Wegent Team"
tags: ["knowledge", "dingtalk", "document"]
bindShells:
- Chat
- Agno
- ClaudeCode
mcpServers:
dingtalk_docs:
type: streamable-http
url: "${{task_data.user_mcps.dingtalk.services.docs.credentials.url}}"
---
# DingTalk Documents
Use the DingTalk document MCP directly. Resource IDs in `<selected_knowledge_sources>` are DingTalk-native IDs.
- For a knowledge space, call `list_nodes` with its workspace ID and traverse the returned hierarchy.
- For a folder, call `list_nodes` with the selected folder ID and continue through descendants when needed.
- For a document, call `get_document_content` with the selected node ID to read its Markdown body.
- `search_documents` does not guarantee workspace or folder scoping. Do not use an unscoped search when the user selected a narrower range; traverse the hierarchy or read the exact document instead.
- The MCP exposes both read and write capabilities. A selected source is a routing hint, not write authorization; DingTalk remains the authority for permissions.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
