Agent skill

Customize NanoClaw

Interactive helper for changing a NanoClaw install: it asks what you want, points to a dedicated skill when one exists, then edits the right layer and says how to verify.

MITAuto-check: notesAgent Workflows

Install Customize NanoClaw

skills CLI

$ npx skills add nanocoai/nanoclaw --skill customize -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install nanocoai/nanoclaw customize --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/nanocoai/nanoclaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/customize .claude/skills/customize && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "customize" agent skill from https://github.com/nanocoai/nanoclaw/tree/main/.claude/skills/customize into .claude/skills/customize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customize", 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

$skill-installer install https://github.com/nanocoai/nanoclaw/tree/main/.claude/skills/customize

Type 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.

skills CLI

$ npx skills add nanocoai/nanoclaw --skill customize -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install nanocoai/nanoclaw customize --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nanocoai/nanoclaw.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/customize .agents/skills/customize && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "customize" agent skill from https://github.com/nanocoai/nanoclaw/tree/main/.claude/skills/customize into .agents/skills/customize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customize", 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.

skills CLI

$ npx skills add nanocoai/nanoclaw --skill customize -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install nanocoai/nanoclaw customize --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nanocoai/nanoclaw.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/customize .cursor/skills/customize && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "customize" agent skill from https://github.com/nanocoai/nanoclaw/tree/main/.claude/skills/customize into .cursor/skills/customize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customize", 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

$ gemini skills install https://github.com/nanocoai/nanoclaw.git --path .claude/skills/customize

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add nanocoai/nanoclaw --skill customize -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install nanocoai/nanoclaw customize --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nanocoai/nanoclaw.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/customize .gemini/skills/customize && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "customize" agent skill from https://github.com/nanocoai/nanoclaw/tree/main/.claude/skills/customize into .gemini/skills/customize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customize", 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.

GitHub CLI

$ gh skill install nanocoai/nanoclaw customize

Installs 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).

skills CLI

$ npx skills add nanocoai/nanoclaw --skill customize -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/nanocoai/nanoclaw.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/customize .github/skills/customize && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "customize" agent skill from https://github.com/nanocoai/nanoclaw/tree/main/.claude/skills/customize into .github/skills/customize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customize", 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.

skills CLI

$ npx skills add nanocoai/nanoclaw --skill customize -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install nanocoai/nanoclaw customize --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nanocoai/nanoclaw.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/customize .opencode/skills/customize && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "customize" agent skill from https://github.com/nanocoai/nanoclaw/tree/main/.claude/skills/customize into .opencode/skills/customize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customize", 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: customize
GitHub stars: 31k
Token cost: ~1.7k tokens
SKILL.md length: 790 words
Files: 1
Skills in repo: 59
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Interactive helper for changing a NanoClaw install: it asks what you want, points to a dedicated skill when one exists, then edits the right layer and says how to verify.

Works in 5 steps: Understand the request — Ask clarifying… → Prefer a dedicated skill — If a skill… → Plan the changes — Identify the v2… → …
Adding a new messaging channel or changing how the agent is triggered
SKILL.md covers Workflow, Entity Model, Key Files and Common Customization Patterns, plus 2 more sections
Calls pnpm

What it does

Questions come first, then a check for a dedicated skill that already covers the request, such as the add-channel skills for Telegram, Slack, Discord, WhatsApp, Signal or iMessage, manage-channels for wiring, manage-mounts for directory access, and skills for alternative agent providers or MCP tools. Only when none fits does the agent plan and make the change itself and describe how to test it.

Every change is framed in terms of the v2 entity model: users, messaging groups, agent groups and sessions, joined by wirings that carry trigger rules. The ncl admin CLI inspects and edits that model, and a table of key files names the entry point, router, delivery loop, session manager, container runner, channel adapters, config and central database.

When your agent uses it

Adding a new messaging channel or changing how the agent is triggered
Modifying how inbound messages are routed to agents
Not sure which NanoClaw skill or file covers a requested change

Example prompts

“Add Telegram as a channel and make the agent answer only when its name is mentioned.”
“Change how NanoClaw routes messages from my Slack workspace to the support agent.”

Requirements

A NanoClaw checkout

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

Understand the request — Ask clarifying questions.
Prefer a dedicated skill — If a skill covers the request, invoke it instead of editing core by hand
Plan the changes — Identify the v2 surface the change belongs to (entity model in the central DB, per-agent-group container config…
Implement — Make the change on the right surface.
Test guidance — Tell the user how to verify.

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
Shell commands in SKILL.md call:
- pnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.
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

Customize NanoClaw loads about 1.7k tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 790 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~75
When it runs · the whole SKILL.md, loaded when a task matches: ~1.7k

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NoteMentions a .env fileSKILL.md:37

istant name, paths, timeouts) read from `.env` |

NoteMentions a .env fileSKILL.md:98
```
2. Update paths in `.env` / config.
```

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). 790 words, ~1,675 tokens.

Download SKILL.mdSave it as .claude/skills/customize/SKILL.md (or your agent's skills folder).

name: customize
description: Add new capabilities or modify NanoClaw behavior. Use when user wants to add channels (Telegram, Slack, email input), change triggers, add integrations, modify the router, or make any other customizations. This is an interactive skill that asks questions to understand what the user wants.

NanoClaw Customization

This skill helps users add capabilities or modify behavior. Use AskUserQuestion to understand what they want before making changes.

Workflow

Understand the request — Ask clarifying questions.
Prefer a dedicated skill — If a skill covers the request, invoke it instead of editing core by hand:
- Channels: /add-telegram, /add-slack, /add-discord, /add-whatsapp, /add-signal, /add-imessage, and the rest of the /add-<channel> family.
- Wiring channels to agents and isolation levels: /manage-channels.
- Container directory access: /manage-mounts.
- Agent providers (non-default): /add-opencode, /add-codex, /add-ollama-provider.
- MCP tools: /add-ollama-tool, /add-atomic-chat-tool.
Plan the changes — Identify the v2 surface the change belongs to (entity model in the central DB, per-agent-group container config, per-group CLAUDE.md, or core code).
Implement — Make the change on the right surface.
Test guidance — Tell the user how to verify.

Entity Model

Customizations route through the v2 entity model: users → messaging groups → agent groups → sessions. A messaging group is one chat/channel on one platform; an agent group holds the workspace, personality, and container config; a wiring links a messaging group to an agent group with a session mode and trigger rules. Inspect and edit all of this with the ncl admin CLI. See docs/isolation-model.md for the three isolation levels.

Key Files

File	Purpose
`src/index.ts`	Entry point: init DB, migrations, channel adapters, delivery polls, sweep, shutdown
`src/router.ts`	Inbound routing: messaging group → agent group → session → `inbound.db` → wake
`src/delivery.ts`	Polls `outbound.db`, delivers via adapter, handles system actions
`src/session-manager.ts`	Resolves sessions; opens `inbound.db` / `outbound.db`; heartbeat path
`src/container-runner.ts`	Spawns per-agent-group containers with session DB + outbox mounts, OneCLI `ensureAgent`
`src/channels/`	Channel adapter infra (registry, Chat SDK bridge); specific adapters install from the `channels` branch
`src/config.ts`	Process-level config (assistant name, paths, timeouts) read from `.env`
`data/v2.db`	Central DB: users, roles, agent_groups, messaging_groups, wirings, container_configs
`data/v2-sessions/<session>/`	Per-session `inbound.db` (host→container) + `outbound.db` (container→host)
`groups/<folder>/CLAUDE.md`	Per-agent-group memory/persona and instructions

For ad-hoc DB queries, use pnpm exec tsx scripts/q.ts <db> "<sql>".

Common Customization Patterns

Adding a New Input Channel (e.g., Telegram, Slack, Email)

Questions to ask:

Which channel? (Telegram, Slack, Discord, WhatsApp, Signal, email, etc.)
Should this channel reach an existing agent group or a new one?
What isolation level — share an agent group with other channels, or keep it separate?
Same trigger rules as other channels on that agent group, or different?

Implementation:

Run the matching install skill (/add-telegram, /add-slack, …). It fetches the adapter from the channels branch, wires the registration import, installs the pinned package, and builds.
Run /manage-channels (or use ncl messaging-groups + ncl wirings) to create the messaging group, choose the isolation level, and wire it to an agent group with a session mode and trigger rules.

Show full SKILL.md (362 more words)Show less

Adding a New MCP Integration

Questions to ask:

What service? (Calendar, Notion, database, etc.)
What operations are needed? (read, write, both)
Which agent group should have access?

Implementation:

If a dedicated /add-<service>-tool skill exists, run it — it wires the MCP server and routes credentials through OneCLI so no raw keys reach the container.
Otherwise wire the MCP server into the agent group's container config with either --command <cmd> [--args <json-array>] [--env <json-object>] for stdio or --url <url> for Streamable HTTP (HTTPS, or plain HTTP for localhost / host.docker.internal): ncl groups config add-mcp-server --id <group-id> --name <name> .... Then run ncl groups restart --id <group-id> to take effect. From inside a container the agent uses the add_mcp_server self-mod tool, which requires one admin approval.

Changing Assistant Behavior

Questions to ask:

What aspect? (persona, response style, instructions)
Apply to one agent group or several?

Implementation:

Persona, instructions, and personality live per agent group in groups/<folder>/CLAUDE.md — edit that file for the target group.
Container runtime behavior (provider, model, packages, MCP servers) lives in the container_configs table: ncl groups config get/update --id <group-id>.

Adding New Commands

Questions to ask:

What should the command do?
Which agent group(s)?
Does it need new MCP tools?

Implementation:

The agent interprets requests naturally — add instructions to the agent group's groups/<folder>/CLAUDE.md.
For routing or trigger changes (which messages wake which agent group), update the wiring's trigger rules: ncl wirings update --id <wiring-id> ....

Changing Deployment

Questions to ask:

Target platform? (Linux server, different Mac)
Service manager? (launchd, systemd)

Implementation:

Create the appropriate service files.
Update paths in .env / config.
Provide setup instructions.

After Changes

Always tell the user.

Run from your NanoClaw project root:

bash

# Rebuild and restart
pnpm run build
source setup/lib/install-slug.sh
# macOS:
launchctl unload ~/Library/LaunchAgents/$(launchd_label).plist
launchctl load ~/Library/LaunchAgents/$(launchd_label).plist
# Linux:
# systemctl --user restart $(systemd_unit)

Example Interaction

User: "Add Telegram as an input channel"

Run /add-telegram to install the adapter, wire its registration, and build.
Ask: "Should Telegram reach an existing agent group, or a new one?"
Ask: "Share an agent group with your other channels, or keep Telegram separate?"
Run /manage-channels (or ncl messaging-groups create + ncl wirings create) to create the messaging group and wire it to the chosen agent group with a session mode and trigger rules.
Tell the user how to authenticate and test.

Files

Just SKILL.md in .claude/skills/customize of nanocoai/nanoclaw.

Open the folder on GitHubat commit 66f0823

Compare with similar skills

Customize NanoClaw 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.

Customize NanoClaw compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Customize NanoClaw this skillnanocoai/nanoclaw	31k	—	~1.7k	Automated safety check: Notes	MIT	yesterday
Chat SDKdatabuddy-analytics/Databuddy	1.2k	—	~2.6k	Automated safety check: Pass	AGPL-3.0	today
Traul Message Searchdandaka/traul	113	—	~3.9k	Automated safety check: Notes	AGPL-3.0	5 mo ago
Message Push0xranx/golembot	323	—	~984	Automated safety check: Pass	MIT	8 days ago
Im Adapter0xranx/golembot	323	—	~1.4k	Automated safety check: Pass	MIT	8 days ago
Ak Dev New Messaging Integrationyaalalabs/agent-kernel	191	—	~4.2k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Chat SDK
databuddy-analytics/Databuddy
Build multi-platform chat bots with Chat SDK (chat npm package).
1.2k GitHub stars~2.6k tokensUpdated today
Agent WorkflowsAuto-check passed
Traul Message Search
dandaka/traul
Drives the traul CLI to sync, search and monitor messages from Slack, Telegram, Discord, Linear, Gmail, WhatsApp, Claude Code sessions and Markdown files.
113 GitHub stars~3.9k tokensUpdated 5 mo ago
Productivity & AutomationAuto-check: notes
Message Push
0xranx/golembot
Send proactive messages to IM groups or individual users via the gateway Send API.
323 GitHub stars~984 tokensUpdated 8 days ago
Productivity & AutomationAuto-check passed
Im Adapter
0xranx/golembot
Format responses for instant messaging platforms such as Lark, DingTalk, WeCom, Slack, and Telegram.
323 GitHub stars~1.4k tokensUpdated 8 days ago
Productivity & AutomationAuto-check passed
Ak Dev New Messaging Integration
yaalalabs/agent-kernel
Step-by-step guide for adding a new messaging platform integration to Agent Kernel.
191 GitHub stars~4.2k tokensUpdated today
Productivity & AutomationAuto-check passed
Skill Publish Notify
ZJU-REAL/Easel
发布通知推送：内容发布成功/失败后，把结果推送到飞书/钉钉/企业微信群机器人、 Telegram、Slack 或任意 webhook。当用户说"发布通知""发到飞书群""通知钉钉""推送到企微" "发布成功提醒""webhook 通知""发布完通知我""群机器人"时使用。纯脚本无第三方依赖。
3.2k GitHub stars~467 tokensUpdated 2 days ago
Backend & APIsAuto-check: notes

Questions about Customize NanoClaw

What does Customize NanoClaw do?

Interactive helper for changing a NanoClaw install: it asks what you want, points to a dedicated skill when one exists, then edits the right layer and says how to verify. Questions come first, then a check for a dedicated skill that already covers the request, such as the add-channel skills for Telegram, Slack, Discord, WhatsApp, Signal or iMessage, manage-channels for wiring, manage-mounts for directory access, and skills for alternative agent providers or MCP tools. Only when none fits does the agent plan and make the change itself and describe how to test it.

When should I use Customize NanoClaw?

Customize NanoClaw fits situations like: adding a new messaging channel or changing how the agent is triggered; modifying how inbound messages are routed to agents; not sure which NanoClaw skill or file covers a requested change.

How do I install Customize NanoClaw in Claude Code?

Run `npx skills add nanocoai/nanoclaw --skill customize -a claude-code`. Or copy the skill folder (.claude/skills/customize in nanocoai/nanoclaw) into .claude/skills/customize in your project. Claude Code loads it when a task matches its description.

How do I install Customize NanoClaw in Codex?

Run `npx skills add nanocoai/nanoclaw --skill customize -a codex`. Or copy the skill folder (.claude/skills/customize in nanocoai/nanoclaw) into .agents/skills/customize in your project. Codex loads it when a task matches its description.

Can I use Customize NanoClaw 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 customize -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/customize, .gemini/skills/customize, .github/skills/customize and .opencode/skills/customize in your project.

What does Customize NanoClaw need to run?

Going by SKILL.md and its folder, Customize NanoClaw needs the command-line tools its instructions call (pnpm). Our summary lists: A NanoClaw checkout.

Does Customize NanoClaw 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 Customize NanoClaw safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Customize NanoClaw use?

Customize NanoClaw 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 Customize NanoClaw use?

About 1.7k tokens (SKILL.md is roughly 6.7k 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 Customize NanoClaw?

Skills that share tags, products or a category with Customize NanoClaw: Chat SDK (databuddy-analytics/Databuddy, 1.2k stars), Traul Message Search (dandaka/traul, 113 stars), Message Push (0xranx/golembot, 323 stars) and Im Adapter (0xranx/golembot, 323 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Customize NanoClaw?

nanocoai (a GitHub organization) maintains it in nanocoai/nanoclaw, which has 30,883 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.

Install Customize NanoClaw

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

NanoClaw Customization

Workflow

Entity Model

Key Files

Common Customization Patterns

Adding a New Input Channel (e.g., Telegram, Slack, Email)

Adding a New MCP Integration

Changing Assistant Behavior

Adding New Commands

Changing Deployment

After Changes

Example Interaction

Files

Compare with similar skills

Similar skills

More from nanocoai/nanoclaw

Related

Questions about Customize NanoClaw