update-skills skill
Refresh installed NanoClaw channel and provider payloads from their registry branches with fork-safe remote resolution and a blocking structured result. Use after updating NanoClaw or whenever installed channel/provider code may be stale.
Is the update-skills skill safe?
Clean: nothing in its files matched our rules. We read 1 file in the folder on 2026-09-28.
No findings.
Install the update-skills skill
A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description.
git clone --depth 1 https://github.com/nanocoai/nanoclaw.git /tmp/nanoclaw mkdir -p ~/.claude/skills cp -r /tmp/nanoclaw/.claude/skills/update-skills ~/.claude/skills/update-skills
In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub
The instructions your agent would load
SKILL.md as published, without the frontmatter. Read it on GitHub
Update installed skills
Refresh the code carried by installed channel and provider skills. This does not re-run credential setup, change .env, alter wiring, or restart services.
Run from the NanoClaw project root. Use ordinary conversation for any choice; do not depend on a provider-specific question or skill-invocation tool.
1. Preflight and selection
Require a clean working tree:
git status --porcelainIf it is dirty, stop. Never mix a refresh with unrelated changes.
The default is every installed channel/provider. If the user asked for a subset, pass its comma-separated names. Otherwise use all:
pnpm exec tsx scripts/update-skills.ts --skills all
# Example subset: --skills slack,opencodeThe helper detects installed skills from the real channel/provider barrels. It resolves each registry branch by checking configured remotes, so a fork whose origin is the user's repo and whose official source is upstream works without special handling. NANOCLAWREGISTRYREMOTE= is an explicit override and is validated before use.
2. Treat the JSON result as a gate
The command prints nanoclaw-skill-refresh/v1-shaped JSON fields with one result per selected skill and exits nonzero unless every selected skill was fully refreshed.
fallback, fetch error, or dependency error is blocking.
- Continue only when success is true and every status is refreshed.
- A missing skill, missing structured apply contract, unresolved input, agent
- Never record a failed skill and continue toward an upgrade completion stamp.
- Preserve the full report in the update summary.
The refresh engine overwrites skill-owned registry files and advances exact dependency/CLI-manifest pins. It skips prompts, operator walkthroughs, .env writes, wiring, restarts, and ordinary build/test directives.
3. Validate the composed checkout
After a successful refresh:
pnpm run build
pnpm testIf files under container/agent-runner/src/ changed, also run:
pnpm exec tsc -p container/agent-runner/tsconfig.json --noEmitIf anything under container/ changed, update the install's agent image using the source mode already selected in .env:
if grep -q '^NANOCLAW_HARDENED_IMAGE=true$' .env 2>/dev/null; then
./container/build.sh pull
else
./container/build.sh
fiAny validation or image failure is blocking. Do not restart or report success.
4. Report
Show the selected skills, the registry remote used for each branch, changed files, validation results, and any blocking error. If this was a standalone refresh and the service was running, restart it through the service mode that actually owns this install and verify data/ncl.sock plus bin/ncl groups list. When called inside /update-nanoclaw, leave restart and health checking to that transaction.
More skills from nanocoai/nanoclaw
- Aadd-anydocAdd local office-document-to-Markdown conversion to NanoClaw agent containers with the pinned Firecrawl AnyDoc CLI. Use when agents need to read attached Word, PowerPoint, Excel, OpenDocument, RTF, EPUB, CSV, or text-based PDF files without uploading them to a hosted parser.
- Aadd-atomic-chat-toolAdd Atomic Chat MCP server so the container agent can call local models served by the Atomic Chat desktop app via its OpenAI-compatible API.
- Fadd-clidashAdd clidash — a zero-dependency, read-only web dashboard that derives its tabs and tables at runtime from any CLI that lists resources as JSON. Ships pre-wired for NanoClaw's ncl CLI (agent groups, sessions, channels, users, roles), plus message-activity charts, a log tail, and a read-only file viewer for group skills/CLAUDE.md/profiles.
- Aadd-codexUse Codex (OpenAI's codex app-server) as a full agent provider — planning, tool orchestration, MCP tools, server-side history, session resume — alongside or instead of Claude. ChatGPT subscription or OpenAI API key, vault-only via the selected gateway. Per-group via `ncl groups config update --provider codex`. Distinct from using OpenAI as an MCP tool (where Claude remains the planner).
- Aadd-dashboardAdd a monitoring dashboard to NanoClaw. Installs @nanoco/nanoclaw-dashboard and a pusher that sends periodic JSON snapshots.
- Aadd-deltachatAdd DeltaChat channel integration via @deltachat/stdio-rpc-server. Native adapter — no Chat SDK bridge. Email-based messaging with end-to-end encryption.
- Cadd-dialAdd Dial channel integration — a real phone number for SMS and AI voice calls via the Dial platform (getdial.ai). Native adapter — no Chat SDK bridge.
- Aadd-dial-numberAdd another phone number to an existing Dial channel — a second (or third) public line for the agent, so one NanoClaw install answers SMS and AI voice calls on multiple numbers. Use when Dial is already installed and the operator wants an additional number (e.g. a personal line plus a support line). Requires the Dial channel to already be installed (see /add-dial).
- Aadd-dial-toolGive chosen NanoClaw agents a real phone number as a container tool — the `dial` CLI baked into the agent image plus OneCLI credential injection for api.getdial.ai, scoped per agent, so the agents you pick can send SMS, place AI voice calls, and receive verification codes from inside the sandbox. Independent of the Dial channel; idempotent; re-run to change which agents may use it. Use when the user wants agents to text, call, or run `dial …` from a chat, without wiring Dial as a messaging channel.
- Aadd-discordAdd Discord bot channel integration via Chat SDK.
- Aadd-emacsAdd Emacs as a channel. Opens an interactive chat buffer and org-mode integration so you can talk to NanoClaw from within Emacs (Doom, Spacemacs, or vanilla). Local HTTP bridge — no bot token or external service needed.
- Aadd-gchatAdd Google Chat channel integration via Chat SDK.