init-first-agent

Set up a NanoClaw DM agent by wiring channel, operator identity, and messaging group.

5|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/thmtz/nanoclaw-fleet --skill init-first-agent-thmtz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: init-first-agent
Source: https://github.com/thmtz/nanoclaw-fleet/tree/main/.claude/skills/init-first-agent
Command: npx skills add https://github.com/thmtz/nanoclaw-fleet --skill init-first-agent-thmtz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Guides operators through standing up the first NanoClaw DM agent for a channel, resolving the operator's identity, wiring the DM messaging group to the new agent, and triggering a welcome DM via the normal delivery path.

Core Features & Use Cases

  • Channel identity resolution and credential verification to determine the correct hosting channel.
  • Agent wiring and provisioning to create an agent-group, messaging group linkage, and deployment of a welcome flow.
  • End-to-end verification by sending a welcome DM to confirm the setup and readiness of the agent.

Quick Start

Stand up the DM first-agent flow by providing CHANNEL, USER_HANDLE, PLATFORM_ID, DISPLAY_NAME, and AGENT_NAME to initialize and awaken the agent, then verify the welcome message arrives.

Frequently Asked Questions about init-first-agent

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

FAQPage Schema
How do I set up the first NanoClaw DM agent for a new channel?

Setting up a NanoClaw DM agent involves resolving channel credentials, wiring the messaging group to a new agent, and synchronously waking the agent via the service CLI to trigger and verify a welcome DM.

What is NanoClaw DM agent onboarding and how does channel configuration work?

NanoClaw DM agent onboarding ties a specific channel, operator identity, and messaging group to a new agent, applying channel configuration checks and identity resolution to establish a ready-to-use DM welcome flow.

Can I rerun the DM agent setup script if the welcome message delivery fails?

Yes, the NanoClaw agent setup supports idempotent reruns, allowing you to safely re-execute the channel configuration and agent wiring scripts to verify end-to-end welcome DM delivery without duplication.

What inputs do I need to initialize a NanoClaw DM welcome flow?

You need the channel name, user handle, platform ID, display name, and agent name to initialize the NanoClaw DM agent and awaken it for end-to-end welcome message verification.

Does the NanoClaw agent setup verify end-to-end message delivery automatically?

Yes, the setup verifies end-to-end delivery by synchronously waking the agent via the service CLI and sending a welcome DM through the normal delivery path to confirm the agent is ready.

Why does my NanoClaw DM agent setup require identity resolution before wiring the messaging group?

Identity resolution is required to determine the correct hosting channel and verify operator credentials before linking the messaging group, ensuring the DM agent is securely provisioned and deployed.