nano---Openclaw: Skill for Claude Code

.claude/skills/setup/SKILL.md

setup is a skill for Claude Code from ShinyStar307/nano---Openclaw. It costs 53 tokens per session (2,927 once invoked), scanned A, original, MIT.

A setup skill for NanoClaw, guiding the first-time installation and configuration of its dependencies, messaging channels, and background services.

In plain words
What is it for?
It is for installing NanoClaw, authenticating messaging channels, registering the main channel, configuring the project, and starting its services.
Why use it?
It helps get NanoClaw running and handles missing dependencies or service problems during setup.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: names the AskUserQuestion tool; mentions Claude Code.

This is ShinyStar307/nano---Openclaw's own configuration. It tells Claude Code how to work on nano---Openclaw 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 nano---Openclaw configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ShinyStar307/nano---Openclaw. 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/ShinyStar307/nano---Openclaw/main/.claude/skills/setup/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/ShinyStar307/nano---Openclaw

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 setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/shinystar307/nano---openclaw/setup/github.svg)](https://agentmods.dev/skills/shinystar307/nano---openclaw/setup)
Your own site
<a href="https://agentmods.dev/skills/shinystar307/nano---openclaw/setup"><img src="https://agentmods.dev/badge/skills/shinystar307/nano---openclaw/setup/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 setup

Your own site · 80×15
<a href="https://agentmods.dev/skills/shinystar307/nano---openclaw/setup"><img src="https://agentmods.dev/badge/skills/shinystar307/nano---openclaw/setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,927 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. ✓ AI security review opus-4-8 · 7 Sept 2026 📄 Read the review
Origin original No closer match found 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.00053 $0.02927
Opus 5.5 $0.00021 $0.01171
Sonnet 5.5 $0.00011 $0.00585
Haiku 4.5 $0.00005 $0.00293

Measured 1mo ago against content hash ea0ea971c6bf, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

setup 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 1mo ago.

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.

- Linux: `curl -fsSL https://deb.nodesource.com/setup_22.x | sudo -E bash - && sudo apt-get install -y nodejs`, or nvm
.claude/skills/setup/SKILL.md · 224 lines

How it starts

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

NanoClaw Setup

Run setup steps automatically. Only pause when user action is required (channel authentication, configuration choices). Setup uses bash setup.sh for bootstrap, then npx tsx setup/index.ts --step <name> for all other steps. Steps emit structured status blocks to stdout. Verbose logs go to logs/setup.log.

Principle: When something is broken or missing, fix it. Don't tell the user to go fix it themselves unless it genuinely requires their manual action (e.g. authenticating a channel, pasting a secret token). If a dependency is missing, install it. If a service won't start, diagnose and repair. Ask the user for permission when needed, then do the work.

UX Note: Use AskUserQuestion for all user-facing questions.

0. Git & Fork Setup

Check the git remote configuration to ensure the user has a fork and upstream is configured.

Run:

  • git remote -v

Case A — origin points to qwibitai/nanoclaw (user cloned directly):

The user cloned instead of forking. AskUserQuestion: "You cloned NanoClaw directly. We recommend forking so you can push your customizations. Would you like to set up a fork?"

  • Fork now (recommended) — walk them through it
  • Continue without fork — they'll only have local changes

If fork: instruct the user to fork qwibitai/nanoclaw on GitHub (they need to do this in their browser), then ask them for their GitHub username. Run:

git remote rename origin upstream
git remote add origin https://github.com/<their-username>/nanoclaw.git
git push --force origin main

Verify with git remote -v.

If continue without fork: add upstream so they can still pull updates:

git remote add upstream https://github.com/qwibitai/nanoclaw.git

Case B — origin points to user's fork, no upstream remote:

Add upstream:

git remote add upstream https://github.com/qwibitai/nanoclaw.git

Case C — both origin (user's fork) and upstream (qwibitai) exist:

Already configured. Continue.

Verify: git remote -v should show origin → user's repo, upstream → qwibitai/nanoclaw.git.

Read the full file on GitHub · 224 lines

Files

What ships with it

1 file 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. 1mo ago First seen · 224 lines · 53 tokens per session scan F ea0ea971c6bf

Subscribe to this mod's changes

setup is a skill published in the GitHub repository ShinyStar307/nano---Openclaw (5 stars, last pushed 7mo ago), licensed MIT. It adds 53 tokens to every session and 2,927 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

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

systematic-debugging

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

obra/superpowers · 21 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

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…

vercel/next.js · 123 tokens