nanocoai/nanoclaw / .claude/skills/update-skills
update-skills
VerifiedRefresh installed NanoClaw channel and provider payloads (channels from their registry branch, providers from their skill payload) with fork-safe remote resolution and a blocking structured result. Use after updating NanoClaw or whenever installed channel/provider code may be stale.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.4 KB |
SKILL.md
View on GitHub---
name: update-skills
description: Refresh installed NanoClaw channel and provider payloads (channels from their registry branch, providers from their skill payload) with fork-safe remote resolution and a blocking structured result. Use after updating NanoClaw or whenever installed channel/provider code may be stale.
---
# 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:
```bash
git status --porcelain
```
If 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`:
```bash
pnpm exec tsx scripts/update-skills.ts --skills all
# Example subset: --skills slack,opencode
```
The helper detects installed skills from the real channel/provider barrels.
A channels-branch companion with no barrel import, such as
`slack-agent-flow`, is found through a line only it appends.
Provider skills refresh from their own `payload/` in this checkout and need
no remote; a provider first installed from the old `providers` branch is
rewritten from the payload the same way. For channel skills it resolves the
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.
`NANOCLAW_REGISTRY_REMOTE=<name>` 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.
- Continue only when `success` is `true` and every status is `refreshed`.
- A missing skill, missing structured apply contract, unresolved input, agent
fallback, fetch error, or dependency error is blocking.
- 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:
```bash
pnpm run build
pnpm test
```
If files under `container/agent-runner/src/` changed, also run:
```bash
pnpm exec tsc -p container/agent-runner/tsconfig.json --noEmit
```
If anything under `container/` changed, update the install's agent image using
the source mode already selected in `.env`:
```bash
if grep -q '^NANOCLAW_HARDENED_IMAGE=true$' .env 2>/dev/null; then
./container/build.sh pull
else
./container/build.sh
fi
```
Any 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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |