nanoclaw-fleet: Skill for Claude Code

.claude/skills/migrate-from-openclaw/SKILL.md

migrate-from-openclaw is a skill for Claude Code from thmtz/nanoclaw-fleet. It costs 68 tokens per session (6,923 once invoked), scanned A, a copy of migrate-from-openclaw, MIT.

A guided migration skill for moving an existing OpenClaw installation to NanoClaw. It reviews OpenClaw identity, channel credentials, scheduled tasks, and other configuration before deciding what to transfer.

In plain words
What is it for?
Inspecting an OpenClaw installation, discussing migration choices, masking credentials while reviewing them, and recording migration progress.
Why use it?
It reduces the risk of silently copying unsuitable data or losing important settings during the move.

Skill for Claude Code

Written for Claude Code: ${CLAUDE_SKILL_DIR} variable. Also seen: mentions CLAUDE.md; mentions subagents; names the AskUserQuestion tool.

This is thmtz/nanoclaw-fleet's own configuration. It tells Claude Code how to work on nanoclaw-fleet itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything nanoclaw-fleet configures →

Reuse

Borrowing it

Nothing to install: this file belongs to thmtz/nanoclaw-fleet. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/thmtz/nanoclaw-fleet/main/.claude/skills/migrate-from-openclaw/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/thmtz/nanoclaw-fleet

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for migrate-from-openclaw

README.md
[![agentmods](https://agentmods.dev/badge/skills/thmtz/nanoclaw-fleet/migrate-from-openclaw/github.svg)](https://agentmods.dev/skills/thmtz/nanoclaw-fleet/migrate-from-openclaw)
Your own site
<a href="https://agentmods.dev/skills/thmtz/nanoclaw-fleet/migrate-from-openclaw"><img src="https://agentmods.dev/badge/skills/thmtz/nanoclaw-fleet/migrate-from-openclaw/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for migrate-from-openclaw

Your own site · 80×15
<a href="https://agentmods.dev/skills/thmtz/nanoclaw-fleet/migrate-from-openclaw"><img src="https://agentmods.dev/badge/skills/thmtz/nanoclaw-fleet/migrate-from-openclaw.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,923 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00068 $0.06923
Opus 5 $0.00034 $0.03461
Sonnet 5 $0.00014 $0.01385
Haiku 4.5 $0.00007 $0.00692

Measured 10d ago against content hash fbb8f8b7f28f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

migrate-from-openclaw scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/discover-openclaw.ts, scripts/extract-channel-credentials.ts), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- For simple webhook notifications: a task script with `curl` often suffices
Origin

This is a copy

100% identical to migrate-from-openclaw — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/skills/migrate-from-openclaw/SKILL.md · 448 lines

How it starts

The opening of the file, as written. The whole thing — 448 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Migrate from OpenClaw

Guide the user through migrating their OpenClaw installation to NanoClaw. This is a conversation, not a batch job. Read OpenClaw state, discuss it with the user, make judgment calls together about what to bring over and how.

Principle: Never silently copy data. Read it, explain it, discuss where it belongs in NanoClaw's architecture, show proposed changes before applying. Credentials must be masked when displayed (first 4 + ... + last 4 characters). Make judgment calls about what's core vs. reference material.

UX: Use AskUserQuestion for multiple-choice only. Use plain text for free-form input. Don't dump raw data — summarize and explain conversationally.

Migration State File

Create migration-state.md in the project root at the start of Phase 0. Update it after each phase completes. This file is the single source of truth for the migration — if context is compacted or lost, re-read it to recover all decisions and progress.

Before starting any phase, re-read migration-state.md to ensure you have current state.

Sections to maintain (add data as each phase completes):

  • Progress — checkbox list of phases (Phase 0–7)
  • Discovery — STATE_DIR, IDENTITY_NAME, channels, groups (with JID mappings), workspace files, cron job count, MCP servers
  • Decisions — assistant_name, group_model (shared/separate/main-only), main_group (folder + jid)
  • Registered Groups — table: folder, jid, channel, is_main
  • Settings Migrated — timezone, anthropic_credential (masked), sender_allowlist (created/skipped)
  • Identity & Memory — paths of files created, which CLAUDE.md was edited
  • Channel Credentials — table: channel, status, env_var
  • Scheduled Tasks — table: original_id, name, migrated/deferred
  • Deferred / Not Applicable — unsupported channels, discussed customizations, OpenClaw-only features

Keep it factual and terse — this is for machine recovery after compaction, not human reading. Delete the file at the end of Phase 7 (or offer to keep it as a record).

Read the full file on GitHub · 448 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 448 lines · 68 tokens per session scan A fbb8f8b7f28f

Subscribe to this mod's changes

migrate-from-openclaw is a skill published in the GitHub repository thmtz/nanoclaw-fleet (5 stars, last pushed 4mo ago), licensed MIT. It adds 68 tokens to every session and 6,923 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to migrate-from-openclaw, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens