dingtalk-contacts

Query DingTalk contacts for users, departments, and organization structure.

6|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/Acosmi/CrabClaw --skill dingtalk-contacts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dingtalk-contacts
Source: https://github.com/Acosmi/CrabClaw/tree/main/docs/skills/tools/dingtalk/contacts
Command: npx skills add https://github.com/Acosmi/CrabClaw --skill dingtalk-contacts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

DingTalk contact information is often scattered across apps and corporate portals. This skill provides a unified way to query users, departments, and the organizational structure directly from your workflow.

Core Features & Use Cases

  • User and Department Retrieval: fetches user details and department info (via get_user, get_department).
  • Department Membership: list members of a given department.
  • Search Capability: find users by name or keyword.
  • Use Case: HR quickly locates a colleague's contact details and department path.

Quick Start

Query DingTalk Contacts to fetch a user by ID, or list department members by dept_id.

Frequently Asked Questions about dingtalk-contacts

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

FAQPage Schema
How do I query DingTalk contacts to retrieve colleague details and department hierarchies?

Query DingTalk contacts by using actions like get_user and get_department to fetch user details and organization structure. You can also list department_users or search_user by keyword to quickly locate colleague information within a corporate environment.

Can I list all members of a specific department in DingTalk?

Yes, you can list department members in DingTalk by using the list_department_users action with a specific dept_id. This retrieves the team roster for a given department, providing quick access to all colleagues within that organizational unit.

What is the best way to search for a user in a DingTalk organization directory?

The best way to search for a user in a DingTalk organization directory is the search_user action, which finds users by name or keyword. This provides a unified query method to retrieve contact details scattered across corporate portals.

Does the DingTalk contacts lookup skill require specific IDs to fetch user information?

Yes, fetching specific user information requires a user ID for the get_user action and a dept_id for the get_department action. The skill includes input validation and safe defaults to ensure accurate retrieval of DingTalk contact details.

What actions are supported for retrieving DingTalk organization structure and contact details?

Supported actions for retrieving DingTalk organization structure include get_user, get_department, list_department_users, and search_user. These actions fetch colleague contact details, department paths, and team rosters directly through the DingTalk API.

Why use a dedicated skill for DingTalk contact lookup instead of manual searches?

Use a dedicated skill for DingTalk contact lookup because corporate contact information is often scattered across apps and portals. This skill provides a unified query method with input validation to directly retrieve users, departments, and organizational structure from your workflow.