Add Channel Connect Button
novuhq/novu
Build a new channel Connect button (e.g. An agent skill from novuhq/novu.
Introduce yourself to a newly connected channel. An agent skill from nanocoai/nanoclaw.
MITAuto-check passed
Install Welcome
$ npx skills add nanocoai/nanoclaw --skill welcome -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nanocoai/nanoclaw welcome --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/nanocoai/nanoclaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/container/skills/welcome .claude/skills/welcome && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "welcome" agent skill from https://github.com/nanocoai/nanoclaw/tree/main/container/skills/welcome into .claude/skills/welcome/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "welcome", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/nanocoai/nanoclaw/tree/main/container/skills/welcomeType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add nanocoai/nanoclaw --skill welcome -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nanocoai/nanoclaw welcome --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nanocoai/nanoclaw.git skills-src && mkdir -p .agents/skills && cp -r skills-src/container/skills/welcome .agents/skills/welcome && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "welcome" agent skill from https://github.com/nanocoai/nanoclaw/tree/main/container/skills/welcome into .agents/skills/welcome/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "welcome", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nanocoai/nanoclaw --skill welcome -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nanocoai/nanoclaw welcome --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nanocoai/nanoclaw.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/container/skills/welcome .cursor/skills/welcome && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "welcome" agent skill from https://github.com/nanocoai/nanoclaw/tree/main/container/skills/welcome into .cursor/skills/welcome/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "welcome", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/nanocoai/nanoclaw.git --path container/skills/welcome--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add nanocoai/nanoclaw --skill welcome -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nanocoai/nanoclaw welcome --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nanocoai/nanoclaw.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/container/skills/welcome .gemini/skills/welcome && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "welcome" agent skill from https://github.com/nanocoai/nanoclaw/tree/main/container/skills/welcome into .gemini/skills/welcome/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "welcome", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install nanocoai/nanoclaw welcomeInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add nanocoai/nanoclaw --skill welcome -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/nanocoai/nanoclaw.git skills-src && mkdir -p .github/skills && cp -r skills-src/container/skills/welcome .github/skills/welcome && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "welcome" agent skill from https://github.com/nanocoai/nanoclaw/tree/main/container/skills/welcome into .github/skills/welcome/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "welcome", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nanocoai/nanoclaw --skill welcome -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install nanocoai/nanoclaw welcome --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nanocoai/nanoclaw.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/container/skills/welcome .opencode/skills/welcome && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "welcome" agent skill from https://github.com/nanocoai/nanoclaw/tree/main/container/skills/welcome into .opencode/skills/welcome/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "welcome", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
welcome- GitHub stars
- 31k
- Used in
- 1 other repo
- Token cost
- ~1.5k tokens
- SKILL.md length
- 886 words
- Files
- 1
- Skills in repo
- 59
- Repo updated
- First seen
- Licence
- MIT
At a glance
Introduce yourself to a newly connected channel. An agent skill from nanocoai/nanoclaw.
- Works in 8 steps: Memory & Context Over Time → Spawning Persistent Agents (create_agent) → Scheduled & Background Tasks → …
- SKILL.md covers Channel addenda, What to do, Capabilities to reveal (in… and Trust & Control — always…, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Welcome is an agent skill from nanocoai/nanoclaw. Introduce yourself to a newly connected channel. Triggered automatically when a channel is first wired. Send a friendly greeting and brief overview of what you can do.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: A lightweight alternative to OpenClaw that runs in containers for security. Connects to WhatsApp, Telegram, Slack, Discord, Gmail and other messaging apps,, has memory, scheduled…. The licence is MIT.
Example prompts
- “/welcome”
Workflow steps
8 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 66f0823. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Welcome loads about 1.5k tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 886 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from nanocoai/nanoclaw at commit 66f0823, republished under its MIT licence (© nanocoai). 886 words, ~1,471 tokens.
Download SKILL.mdSave it as
.claude/skills/welcome/SKILL.md (or your agent's skills folder).- name
- welcome
- description
- Introduce yourself to a newly connected channel. Triggered automatically when a channel is first wired. Send a friendly greeting and brief overview of what you can do.
/welcome — Channel Onboarding (Updated)
You've just been connected to a new user. This your time to shine and make a strong first impression. Introduce yourself and guide the user through what you can do. you got this!
Channel addenda
The instruction that triggered this welcome may name a channel addendum file
(e.g. /app/skills/welcome/addenda/slack.md). If it does, read that file first
and follow it — it adjusts this welcome for the channel you are on (it may
replace a section below or add steps). If no addendum is named, run this skill
exactly as written.
What to do
- Send a short, warm greeting
- State your name (from your system prompt / CLAUDE.md)
- Signal that you're capable of a lot — but don't list everything upfront. Be intriguing, not encyclopedic
- Ask: would they like to explore what you can do, or jump straight into something?
If they want to explore: drip-feed one capability at a time. Briefly explain it, offer to demo a compelling example or let them try it. Never dump a full list.
If they want to jump in: just go.
Capabilities to reveal (in order)
Reveal these one at a time, in this sequence. Each should be 2–4 sentences max.
1. Memory & Context Over Time
You remember things across conversations — projects, preferences, people, decisions. Users don't have to re-explain context every session. The more they work with you, the more situationally aware you become.
2. Spawning Persistent Agents (create_agent)
You can spin up other named agents — a Researcher, a Builder, a Calendar agent — each with their own memory, workspace, and personality. They're addressable destinations: you delegate, they work, they report back. These aren't one-shot tasks; they accumulate context across sessions.
3. Scheduled & Background Tasks
You can run tasks on a schedule — daily briefings, monitors that alert only when something matters, recurring reminders. For bigger jobs, you can spin up an agent that works in the background while the conversation continues.
4. Research & Web Browsing
You can browse the web like a person — read articles, pull live data, summarize reports, compare products, answer questions that aren't in your training data. Ask me "what's the latest on X" or "find the best Y for Z" and I'll actually look it up. Very powerful when combined with scheduled tasks.
5. Code & Building Things
You can write, debug, and deploy full applications — scripts, APIs, frontend sites. You can spin up a dev server, test in a real browser, and deploy to production (e.g. Vercel). Concept to live URL.
6. Interactive UI
You can send structured cards and multiple-choice buttons directly into the chat — not just plain text. Useful for decisions, presenting options, or surfacing results cleanly.
7. Files & Artifacts
You can produce real deliverables — reports, PDFs, charts, generated images — and send them as downloadable files in chat, not just pasted text.
8. Self-Customization
You can add new tools and MCP servers to yourself if a capability isn't built in. You can extend your own toolkit when the task requires it.
Trust & Control — always include these
After the capabilities tour (or woven in naturally), cover these two points. Frame them positively — users stay in control.
Show full SKILL.md (364 more words)Show less
Approvals
Sensitive actions — installing packages, adding MCP servers — require the user's explicit approval before you proceed. They'll get a prompt; nothing happens automatically. Their credential gateway may also require human approval before releasing a credential.
Access Control
The user owns who can talk to you. Adding you to a new group or sharing a bot link with someone triggers an approval request on their end. Nobody interacts with you without their say-so.
How to interact — always mention this
There are no special commands. Users just talk naturally. If they want something done, they say so. That's it.
Shape memory to the user's world (agent-internal, not part of the tour)
From the first conversation onward, pay attention to the parts of the user's world that will recur: personal life, business operations, legal work, research, or something else. Don't interview them; infer it from what they ask and share.
Let those domains drive your memory types. What are the handful of kinds of things this user will keep coming back to? A business assistant might land on customers, deals, and competitors; legal work on clients and matters. Derive the vocabulary from your conversations, and let it evolve with your understanding of the user.
Record who the user is and the context you infer as Core Memory lines in
memory/index.md from the first conversation, and refine them as the
recurring domains become clear. Behavioral role and persona instructions
belong in instructions.prepend.md.
Wrapping up
After the tour, finish with an open invitation. Ask if they want help with something specific. Tell them they can share any generally what they're working on and any challenges they have currently and you can suggest ways you could help.
Tone
Warm, confident, inviting. Make the user feel like they just unlocked something powerful. Match the channel vibe: casual on consumer chat apps, slightly more professional on workplace platforms.
Important
- Scan your available MCP tools and skills before starting — know what you have, but keep it in your back pocket
- Never overwhelm with a full capability list. Discovery should feel like unwrapping, not reading a manual
- Confirmations and corrections from the user during onboarding are feedback — save them to memory for future sessions
© nanocoai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in container/skills/welcome of nanocoai/nanoclaw.
Open the folder on GitHubat commit 66f0823
Used in 1 other repository
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in nanocoai/nanoclaw, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Welcome next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Welcome this skillnanocoai/nanoclaw | 31k | 1 repos | ~1.5k | Automated safety check: Pass | MIT | |
| Add Channel Connect Buttonnovuhq/novu | 40k | — | ~1.6k | Automated safety check: Pass | Custom licence | |
| ConnectComposioHQ/awesome-claude-skills | 77k | 3 repos | ~987 | Automated safety check: Pass | None | |
| Configure Channelopenclaw/openclaw | 392k | — | ~946 | Automated safety check: Pass | MIT | |
| Node Connectopenclaw/openclaw | 392k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Connections Optimizeraffaan-m/ECC | 275k | 2 repos | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
Connect
ComposioHQ/awesome-claude-skills
Connect Claude to any app. An agent skill from ComposioHQ/awesome-claude-skills.
Configure Channel
openclaw/openclaw
Configure and prove a chat channel with non-interactive one-liners; secrets only as SecretRefs.
Node Connect
openclaw/openclaw
Diagnose OpenClaw Control UI browser and native Android, iOS, or macOS node connection failures across route, auth, pairing, QR/setup-code, and reconnect states.
Connections Optimizer
affaan-m/ECC
Reorganize the user's X and LinkedIn network with review-first pruning, add/follow recommendations, and channel-specific warm outreach drafted in the user's real voice.
Figma Code Connect Components
nexu-io/open-design
Connect Figma design components to code components using Code Connect so design-system updates flow into the codebase automatically.
More from nanocoai/nanoclaw
All 59 skills in this repoIron Proxy Gateway for NanoClaw
nanocoai/nanoclaw
Installs or refreshes Iron Proxy and its Iron Control web console for NanoClaw, with a local Docker setup, database, credentials and a human approval bridge.
Agent Browser
nanocoai/nanoclaw
Drives a web browser from the shell with the agent-browser CLI: open pages, read an element snapshot, click and fill by reference, grab text and screenshots.
NanoClaw OneCLI Gateway Installer
nanocoai/nanoclaw
Installs or refreshes OneCLI as the gateway provider for NanoClaw, copying the adapter files, registering the provider and running the setup script.
OpenClaw to NanoClaw Migration
nanocoai/nanoclaw
Guides a conversational migration from an OpenClaw install to NanoClaw v2, carrying over identity, channel credentials, scheduled tasks and workspace files.
Add A Second Dial Phone Number
nanocoai/nanoclaw
Wires up an additional phone number onto an already-installed Dial channel, so one NanoClaw install answers SMS and AI voice calls on more than one line.
NanoClaw LLM Wiki Setup
nanocoai/nanoclaw
Adds a persistent wiki knowledge base to a NanoClaw group following Karpathy's LLM Wiki pattern, with folders, a tailored container skill and a CLAUDE.md section.
Questions about Welcome
What does Welcome do?
Introduce yourself to a newly connected channel. An agent skill from nanocoai/nanoclaw. Welcome is an agent skill from nanocoai/nanoclaw. Introduce yourself to a newly connected channel.
How do I install Welcome in Claude Code?
Run `npx skills add nanocoai/nanoclaw --skill welcome -a claude-code`. Or copy the skill folder (container/skills/welcome in nanocoai/nanoclaw) into .claude/skills/welcome in your project. Claude Code loads it when a task matches its description.
How do I install Welcome in Codex?
Run `npx skills add nanocoai/nanoclaw --skill welcome -a codex`. Or copy the skill folder (container/skills/welcome in nanocoai/nanoclaw) into .agents/skills/welcome in your project. Codex loads it when a task matches its description.
Can I use Welcome in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nanocoai/nanoclaw --skill welcome -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/welcome, .gemini/skills/welcome, .github/skills/welcome and .opencode/skills/welcome in your project.
What does Welcome need to run?
SKILL.md names no scripts, command-line tools or credentials: Welcome is instructions for the agent only.
Does Welcome access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Welcome safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Welcome use?
Welcome is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Welcome use?
About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Welcome?
Skills that share tags, products or a category with Welcome: Add Channel Connect Button (novuhq/novu, 40k stars), Connect (ComposioHQ/awesome-claude-skills, 77k stars), Configure Channel (openclaw/openclaw, 392k stars) and Node Connect (openclaw/openclaw, 392k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Welcome?
nanocoai (a GitHub organization) maintains it in nanocoai/nanoclaw, which has 30,897 GitHub stars. The repository holds 59 skills in this directory. The repository was last updated on October 6, 2026.
Source: nanocoai/nanoclaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.