init-first-agent

Provision a first NanoClaw agent for a direct message channel with delivery verification.

5|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/chiptoe-svg/nanoclaw_gccourse --skill init-first-agent-chiptoe-svg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: init-first-agent
Source: https://github.com/chiptoe-svg/nanoclaw_gccourse/tree/main/.claude/skills/init-first-agent
Command: npx skills add https://github.com/chiptoe-svg/nanoclaw_gccourse --skill init-first-agent-chiptoe-svg

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill eliminates the manual, error-prone process of configuring your first NanoClaw agent for a direct message channel, and removes the uncertainty of whether end-to-end message delivery is working properly.

Core Features & Use Cases

  • Guided Channel & Identity Setup: Walks you through selecting your active channel, collecting your platform user ID, display name, and desired agent persona name.
  • Cross-Channel Identity Resolution: Automatically handles identity lookup for both direct-addressable channels (Telegram, WhatsApp, etc.) and cold-DM channels (Discord, Slack, etc.) with optional pair-code support for Telegram.
  • Idempotent Agent Provisioning: Safely creates all required user records, agent groups, and messaging wiring, so you can rerun the skill at any time without duplicate entries or conflicts.
  • Built-in Delivery Verification: Sends a welcome DM from the new agent to confirm the full workflow works, with clear troubleshooting steps if the message doesn't arrive.
  • Use Case: For example, if you are an instructor deploying NanoClaw for your classroom for the first time, this Skill lets you quickly set up your personal assistant agent on your preferred messaging platform and confirm it can communicate with you before rolling it out to students.

Quick Start

Use the init-first-agent skill to configure your first NanoClaw direct message agent for your chosen connected channel and receive a welcome message to confirm end-to-end delivery is working correctly.

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 a DM agent for direct messaging channels without manual configuration errors?

To set up a DM agent without manual configuration errors, you need an automated provisioning process that handles user record creation, agent group wiring, and identity resolution. This ensures idempotent deployment, preventing duplicate entries when rerun, and verifies end-to-end message delivery successfully.

What is cross-channel identity resolution for cold-DM platforms like Discord and Slack?

Cross-channel identity resolution for cold-DM platforms like Discord and Slack is the automated process of mapping your platform user ID to your display name. It handles lookup differences between direct-addressable and cold-DM channels, ensuring accurate agent targeting and successful message delivery.

Can I provision a direct message agent for academic or personal NanoClaw deployments?

Yes, you can provision a direct message agent for academic or personal NanoClaw deployments. This setup process is specifically designed for instructors and individual operators to connect their first DM channel, resolve platform identity, and confirm the agent can send and receive messages successfully.

How do I verify welcome message delivery after agent setup?

To verify welcome message delivery after agent setup, the system automatically sends a test DM from the newly provisioned agent to your account. This confirms the full messaging workflow is operational and provides clear diagnostic troubleshooting steps if the message fails to arrive.

Why does my agent provisioning fail when I rerun the setup process?

Agent provisioning should not fail when rerun if the process uses idempotent provisioning logic. Idempotency safely creates all required user records, agent groups, and messaging wiring without generating duplicate entries or conflicts, allowing you to execute the setup workflow repeatedly without errors.