// QQ C2C channel skill. Use when Bub is handling a QQ conversation. Return your normal text reply directly and let the QQ channel deliver it through standard Bub outbound routing.
Create or update a Bub plugin in any local path. Use when the task is to scaffold a Python package that exposes a [project.entry-points.bub] entry, implement Bub hooks or tools, and make the plugin take effect by installing it or adding it as a dependency in the Bub runtime project. When working inside bub-contrib, also follow its package and workspace conventions.
Export, filter, scan, and review shareable tape datasets produced by `tape-dataset-opendal`. Use when Codex needs to prepare Bub-generated tape data for public sharing, Hugging Face upload, external research handoff, or any review-sensitive export that must run CEL filtering, TruffleHog secret scanning on the staged artifact, and a final conservative LLM audit.
WeCom channel skill. Return normal replies directly. For proactive sends such as scheduled jobs, use the packaged wecom_send.py script.
Use this skill to respond to messages from feishu channel.
DingTalk channel skill. When $dingtalk appears in message context, return your response as text and the framework will deliver it. For programmatic sends (e.g. progress updates), use dingtalk_send.
| name | |
| description | QQ C2C channel skill. Use when Bub is handling a QQ conversation. Return your normal text reply directly and let the QQ channel deliver it through standard Bub outbound routing. |
| metadata | {"channel":"qq"} |
Use this skill when the current conversation is on QQ.
QQChannel.send.qq_send.py for normal replies.msg_seq; QQ reply sequencing is managed inside the plugin.sender_id or message_id, do not invent protocol fields or shell commands.Current QQ inbound message JSON typically includes:
message: normalized text contentmessage_id: QQ inbound message id for passive replysender_id: QQ user openiddateattachmentsmsg_seq handling in the answer.