About this skill

Problem It Addresses

In WeChat integration, group sending, entry push, and auto-reply are often implemented as separate scripts or endpoints. Each caller must handle authentication, message context, failure retries, and response parsing. This skill consolidates the actions under one calling contract, making them easier to integrate into an engineering pipeline.

How It Works

Action type: set action_type to group_send, entry_push, or msg_callback, and pass action-specific fields through params.
Messaging channel: Kafka settings such as bootstrap_servers and topics like wx_group_send_topic, wx_entry_notice_topic, and wx_auto_reply_topic determine where messages are written.
Auth and model: skillhub_token handles authentication, while openai.api_key, model, and temperature shape auto-reply or generated response behavior.
Response shape: it returns code, msg, and data; code=0 indicates success, and non-zero values indicate failure, which simplifies branching and logging.

Boundaries and Caveats

This skill fits backend workflows that need WeChat message actions, especially when Kafka, OpenAI, or similar model services are already part of the stack. The provided materials do not specify WeChat account authorization scope, rate limits, compliance requirements, or retry policy. Before production use, verify the expected params, topic permissions, token management, and environment configuration. It should not be treated as a full WeChat Open Platform SDK.

Screenshots

Use Cases

When backend integrates WeChat group sending, trigger group_send with target parameters.
When support systems receive user messages, call msg_callback to generate auto-replies.
When entry-notice services need to push review results with entry_push business parameters.
When Kafka consumers process wx_auto_reply_topic messages and run reply logic.

Best For

Backend engineers integrating WeChat notifications who need a unified API for group send and entry push.
Support-system developers who want to connect message callbacks to auto-reply workflows.
Business-platform integrators who need to route actions by action_type.
Kafka pipeline maintainers who need to map message topics to response codes.