Onboard Messaging Channel

Use this skill to add a messaging channel end-to-end without leaking channel-specific logic into core NemoClaw code.

Intake

Gather inputs progressively. Do not ask the full intake checklist in one message. Ask one concise clarification at a time, choosing the earliest unresolved blocker:

1. If the channel name is missing, ask for the channel name.
2. If target agents are missing, ask whether the channel should support OpenClaw, Hermes, or both.
3. If upstream references are missing, ask for the official docs link and source-of-truth implementation link or path. Include Telegram as the format example: docs https://docs.openclaw.ai/channels/telegram, source https://github.com/openclaw/openclaw/tree/main/extensions/telegram.
4. After references are available, read them and the local messaging package before asking about credentials, plugin installs, reachability, or network policy.
5. Ask follow-up questions one by one only for details that remain ambiguous after source analysis.

Use this intake checklist internally while analyzing source: