About this skill

What It Solves

When agents handle DingTalk meetings, the hard part is not merely reading a calendar. It is completing multi-step actions reliably: inferring titles, times, participants, and rooms; resolving userId values; checking room availability; and confirming whether deletion affects the organizer or only one participant. This skill narrows those tasks to the official DingTalk Calendar MCP and enforces a predictable workflow for defaults, confirmation, and failure handling.

How It Works

Event management: create, update, and delete events; respond to invitations; list recent events and inspect details.
Participants and rooms: resolve participants by name or phone number, add or remove attendees, query available meeting rooms, and book rooms to events.
Key steps: verify the dingtalk-calendar MCP is available; show a complete confirmation summary before write operations; fill defaults for time, timezone, and duration; cache participant userId values in references/contacts.cache to reduce repeated lookups.

Boundaries

It only covers DingTalk calendar and meeting rooms, not Feishu, Google Calendar, Outlook, DingTalk IM, or document workflows. Adding other attendees may require the dingtalk-contacts MCP. MCP URLs contain personal API keys and should not be committed to version control. Write operations such as deleting events, booking rooms, or changing ACLs require confirmation.

Screenshots

Use Cases

Before a team meeting, create a DingTalk event and resolve attendee `userId` values by name via the contacts MCP.
When review timing is unclear, query attendee busy status and suggest available meeting times.
Book a meeting room for a retro by checking available rooms and attaching one to an existing event.
Before deleting a mistaken event, confirm event details, participants, and the deletion scope.

Best For

Engineering managers planning releases: sync review and integration windows to DingTalk Calendar and resolve attendees.
Product managers running cross-team meetings: create events, check busy status, and book meeting rooms.
Office administrators managing calendar sharing: list calendar books and add or remove ACL entries.
Agent developers integrating MCP: wrap DingTalk calendar operations into confirmable, recoverable workflows.