oneworks-channellisted

# oneworks-channel Use this skill when the current task is running from a OneWorks channel session and the channel chat should receive a deliberate message. `oneworks channel` is a shell CLI for the agent. It is not a command users send inside WeChat, Lark, or another chat platform. In channel sessions, assume `oneworks channel` is available from the injected environment. Do not run `which oneworks`, `oneworks --help`, or `oneworks channel --help` just to check availability; use the examples below directly unless a command fails or the user explicitly asks you to inspect CLI help. ## When To Send - In group chats, runtime progress is intentionally not auto-forwarded. Send only when the user asked for a group-visible result, a concise status, or a useful artifact. - In WeChat private chats, a compatibility auto-delivery path may still exist for the first assistant reply and final stop reply. Prefer deliberate external replies through `oneworks channel`, then keep Chat History / stop text as a short internal summary to avoid duplicate messages. - In casual channel chat, custom emoji can be part of the bot's voice. For lightweight agreement, teasing, awkward silence, topic closure, quick encouragement, or a reaction to another sticker, consider sending a known custom emoji instead of making every reply text-heavy. - Build a small stable set of signature emoji for the bot. Prefer high-confidence, reusable emoji with clear labels/tags over random one-off choices, so repeated