Read and manage DingTalk AI table records through the DingTalk AI Table MCP. Use this skill when the user explicitly refers to a DingTalk AI table, fields, or records.
Scanned 8/31/2026
Install to Claude Code
npx -y skills add wecode-ai/Wegent --skill dingtalk-ai-table --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Dingtalk Ai Table?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/wecode-ai-dingtalk-ai-table)More formats (shields.io, HTML) on the badges page.
---
description: "Read and manage DingTalk AI table records through the DingTalk AI Table MCP. Use this skill when the user explicitly refers to a DingTalk AI table, fields, or records."
displayName: "钉钉 AI 表格"
version: "1.0.0"
author: "Wegent Team"
tags: ["dingtalk", "ai-table", "records"]
bindShells:
- Chat
- ClaudeCode
mcpServers:
dingtalk_ai_table:
type: streamable-http
url: "${{task_data.user_mcps.dingtalk.services.ai_table.credentials.url}}"
---
# DingTalk AI Tables
Use the DingTalk AI Table MCP for the table explicitly identified by the user.
- Read only the requested table, view, fields, and records.
- Use create, update, or delete tools only when the user explicitly requests that mutation.
- Keep document node IDs and AI table IDs separate when both DingTalk services are active.
- DingTalk remains the authority for the current user's 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', ...