im-channels

Parse <im> blocks from WeChat, WeCom, DingTalk, and Lark messages.

5.0k|548|Updated May 14, 2025
One-click install
npx skills add https://github.com/dtyq/magic --skill im-channels
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: im-channels
Source: https://github.com/dtyq/magic/tree/main/backend/super-magic/agents/skills/im-channels
Command: npx skills add https://github.com/dtyq/magic --skill im-channels

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Integrate and interpret messages from IM channels (WeChat, WeCom, DingTalk, Lark) by understanding how <im> blocks convey source context.

Core Features & Use Cases

  • Understand incoming <im> blocks and extract their source, media attachments, and provenance.
  • Guide to connecting IM bots across WeChat, WeCom, DingTalk, and Lark with platform-specific references.
  • Ensure responses respect channel formatting and context, while isolating any metadata from the user-visible content.
  • Use Case: When a user sends a message with an <im> block, the agent processes it using the correct channel context and returns a coherent reply.

Quick Start

Connect an IM bot for your chosen platform (WeChat, WeCom, DingTalk, or Lark) using the reference steps and then test by sending a message containing an <im> block to verify correct handling.

Frequently Asked Questions about im-channels

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

FAQPage Schema
How do I connect an IM bot to process incoming WeChat or DingTalk messages?

To connect an IM bot, follow platform-specific reference steps for WeChat, WeCom, DingTalk, or Lark to collect credentials, establish the connection, and verify handling by sending a test message with an <im> block.

What is an <im> block and how does it convey message source context?

An <im> block is a metadata structure that conveys source context, carrying platform provenance and media attachments from IM channels like WeChat and Lark, enabling the agent to process messages with correct channel context.

Can I use this to extract media attachments from WeCom and Lark messages?

Yes, you can extract media attachments from WeCom and Lark messages by understanding incoming <im> blocks, which carry source context and media attachments from supported IM platforms for coherent processing.

How do I ensure responses respect channel formatting when isolating IM metadata?

To ensure responses respect channel formatting while isolating metadata, process <im> blocks to separate user-visible content from platform-specific metadata, returning coherent replies that match the originating IM channel context.

What are the limitations when handling IM channels across multiple platforms?

Limitations include enforcing safe handling and platform-specific steps as described in references, requiring credential collection and status checks for each supported IM platform to maintain correct source context processing.

Does im-channels work with WeChat, WeCom, DingTalk, and Lark simultaneously?

Yes, im-channels supports WeChat, WeCom, DingTalk, and Lark, integrating messages by understanding <im> blocks to extract source context and media attachments across these supported IM platforms.