dingtalk-messaging

Format DingTalk messages across text, markdown, and ActionCard with mentions.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/adongguo/openclaw-dingtalk --skill dingtalk-messaging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dingtalk-messaging
Source: https://github.com/adongguo/openclaw-dingtalk/tree/main/skills/dingtalk-messaging
Command: npx skills add https://github.com/adongguo/openclaw-dingtalk --skill dingtalk-messaging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Formatting and rendering DingTalk messages correctly across text, markdown, and ActionCard to ensure professional appearance, reliable presentation, and proper use of mentions and content chunking.

Core Features & Use Cases

  • Message type overview: text, markdown, actionCard, and link formats with auto-render guidance.
  • Render mode guidance: auto, raw, or card, plus rules for when to switch rendering based on content.
  • Markdown rules and @mention guidance, including supported constructs and limitations.
  • Long-form messaging practices: chunking, headers, and concise content for mobile readability.
  • Real-world use: bot replies and team updates that require consistent formatting and clear visual structure.

Quick Start

Provide a sample DingTalk message demonstrating proper formatting for text and markdown, with appropriate @mentions and an ActionCard example.

Frequently Asked Questions about dingtalk-messaging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I format DingTalk messages for consistent rendering across text and markdown?

To format DingTalk messages, apply specific rules for text, markdown, and ActionCard types, ensuring consistent presentation. Proper formatting guarantees reliable rendering and professional appearance across bot replies and team communications.

What markdown constructs are supported for DingTalk bot responses?

DingTalk markdown supports specific constructs with known limitations for bot responses. Following the provided markdown rules and anti-pattern avoidance ensures your messages render reliably without formatting errors on mobile or desktop clients.

How do I handle long-form DingTalk messages for mobile readability?

Handle long-form DingTalk messages by applying content chunking, using headers, and keeping content concise. This practice ensures mobile readability and prevents rendering issues when sending extensive team updates or knowledge base entries.

When should I use ActionCard versus raw text in DingTalk?

Use ActionCard versus raw text based on render mode guidance, switching formats according to content needs. Auto, raw, and card modes dictate when to apply specific formatting to maintain clear visual structure.

Does DingTalk messaging support @mentions within markdown content?

DingTalk messaging supports @mentions within markdown content by following specific guidance for proper use. Correctly formatting mentions ensures notifications trigger reliably while maintaining the intended markdown rendering structure.

What are common rendering limitations when formatting DingTalk messages?

Common DingTalk rendering limitations involve unsupported markdown constructs and anti-patterns that break visual structure. Specifying requirements around supported render modes and containment bounds helps avoid these formatting pitfalls.