dingtalk_channel_connect

Automate DingTalk channel integration into MateClaw via visible-browser workflows.

839|277|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/matevip/mateclaw --skill dingtalk-channel-connect-matevip
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dingtalk_channel_connect
Source: https://github.com/matevip/mateclaw/tree/main/mateclaw-server/src/main/resources/skills/dingtalk_channel_connect
Command: npx skills add https://github.com/matevip/mateclaw --skill dingtalk-channel-connect-matevip

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires browser_use, execute_shell_command, read_file.

What problem does it solve?

Automates the DingTalk channel integration for MateClaw using a visible browser, pausing when a login page appears and resuming after the user signs in.

Core Features & Use Cases

  • Automates the end-to-end setup of a DingTalk channel: app creation in the developer backend, binding to MateClaw, and configuration with bot capability.
  • Handles login prompts by pausing automation and awaiting user login, then continuing once the user confirms.
  • Enforces publishing steps after configuration changes to ensure new versions take effect, and provides guidance for retrieving Client ID and Client Secret.
  • Supports configuration of icons and preview images according to the required image specs, and guides the user through the binding workflow in MateClaw.

Quick Start

Launch the DingTalk channel connect flow using this skill and follow the on-screen prompts to complete the app creation, bot setup, credential capture, and binding steps in the visible browser.

Frequently Asked Questions about dingtalk_channel_connect

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

FAQPage Schema
How do I automate DingTalk channel integration with a visible browser?

Automating DingTalk channel integration involves guiding a visible-browser workflow to handle app creation, bot capability setup, and credentials binding. The automation pauses for login prompts and resumes after user authentication to complete the configuration.

Can I bind DingTalk credentials without manual login?

Binding DingTalk credentials requires manual login intervention. The visible-browser automation pauses when a login page appears, awaits user authentication, and resumes the binding workflow only after the user confirms the login is complete.

What steps are needed to configure a DingTalk bot for channel publishing?

Configuring a DingTalk bot requires app creation in the developer backend, enabling bot capabilities, uploading icons, and capturing Client ID and Secret. The workflow enforces version publishing steps after configuration changes to ensure updates take effect.

Does DingTalk channel automation support icon and preview image configuration?

DingTalk channel automation supports configuring icons and preview images according to required image specifications. The visible-browser workflow guides users through uploading these assets during the app creation and bot setup process.

How do I retrieve DingTalk Client ID and Client Secret for channel binding?

Retrieving DingTalk Client ID and Client Secret is part of the automated workflow. The visible-browser automation guides you through the developer backend to capture these credentials and then binds them to complete the channel integration.

Why does DingTalk channel binding require enforcing publishing steps?

Enforcing publishing steps after configuration changes ensures new versions take effect in the DingTalk developer backend. The automation mandates this step to guarantee that bot capability updates and binding configurations are successfully applied.