nemoclaw-contributor-onboard-messaging-channel

Guides contributors through adding messaging channels to NemoClaw's manifest-first architecture.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/Army161/NemoClaw --skill nemoclaw-contributor-onboard-messaging-channel-army161
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nemoclaw-contributor-onboard-messaging-channel
Source: https://github.com/Army161/NemoClaw/tree/main/.agents/skills/nemoclaw-contributor-onboard-messaging-channel
Command: npx skills add https://github.com/Army161/NemoClaw --skill nemoclaw-contributor-onboard-messaging-channel-army161

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Adding a new messaging channel to NemoClaw requires coordinating manifests, template resolvers, hooks, policy presets, agent packages, docs, and tests across many files, and mistakes leak channel-specific logic into core code. ## Core Features & Use Cases - Progressive Intake: Asks one clarification at a time for channel name, target agents (OpenClaw, Hermes, or both), upstream docs, and source-of-truth implementation links. - Manifest-First Implementation: Walks through creating channel manifests, template resolvers, hooks, built-in registrations, and network policy presets under src/lib/messaging/channels/. - Quality Gates and Verification: Enforces rules like mocking external APIs in tests, keeping secrets out of persisted state, and running targeted Vitest invocations. - Use Case: A contributor wants to onboard a Telegram-style channel for OpenClaw; the skill guides them from upstream source analysis through manifest creation, policy preset, docs updates, and targeted test runs. ## Quick Start Ask the agent to onboard a new messaging channel for OpenClaw using the official channel docs and upstream source repository links.

Frequently Asked Questions about nemoclaw-contributor-onboard-messaging-channel

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new messaging channel to NemoClaw?

Start with a manifest at src/lib/messaging/channels/<channel>/manifest.ts defining auth, inputs, credentials, policyPresets, render, runtime, agentPackages, state, and hooks. Then register it in built-ins.ts, add a policy preset, update docs, and run targeted Vitest tests.

How do I onboard a messaging channel for OpenClaw or Hermes?

Declare supported agents only in the channel manifest's supportedAgents field, never in agent manifests. Keep Hermes unsupported when only OpenClaw source support exists, and add agentPackages metadata when the channel needs an external agent plugin.

When should I add a template resolver or hooks for a channel?

Add a template resolver only for derived render values like allowlist normalization or proxy URLs. Add hooks only for enrollment, external reachability checks, QR capture, conflict checks, or health probes that cannot be static manifest data.

What tests should I run after adding a messaging channel?

Run a targeted npx vitest invocation covering the channel directory, manifests.test.ts, metadata.test.ts, manifest-compiler.test.ts, and messaging-build-applier tests. Mock external APIs and use a skip env var for live reachability hooks with fake credentials.

Can channel manifests store user credentials or tokens?

No, only non-secret state may be persisted. Plans may contain placeholders, availability flags, and hashes, but never raw tokens, keeping credentials out of stored channel state.