cap_im_platform

What problem does it solve?

It solves the need to deliver the user’s requested extra content (a message, an image, or a local file) to the correct IM channel and target chat without disturbing the normal agent reply flow.

Core Features & Use Cases

• Channel-aware delivery: Routes outbound sends through the appropriate capability for Feishu, QQ, Telegram, or WeChat based on source_cap or an explicit user request.
• Correct payload typing: Sends text, images, or non-image files using the matching tool, including image-extension handling and “files vs images” separation.
• Local path resolution rules: Ensures path is a real local device path and avoids passing remote URLs directly, supporting common app storage patterns like <storage_root>/inbox.
• Chat target enforcement: Applies the right chat_id requirements, especially strict WeChat behavior that must always use explicit chat_id.

Quick Start

Use this skill when the user says they want to send an additional piece of content through their current IM channel, and provide the requested text, image, or local file path so the skill can call the correct platform send capability.