self-customize

Automate NanoClaw environment customization with admin-approved workspace and package changes.

5|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/thmtz/nanoclaw-fleet --skill self-customize-thmtz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: self-customize
Source: https://github.com/thmtz/nanoclaw-fleet/tree/main/container/skills/self-customize
Command: npx skills add https://github.com/thmtz/nanoclaw-fleet --skill self-customize-thmtz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The self-customize skill enables users to modify their agent environment and capabilities by coordinating direct workspace edits, system package changes, MCP server wiring, or code changes through a dedicated builder agent, while keeping a clear boundary between runtime workspace edits and container-level changes.

Core Features & Use Cases

  • Delegated code changes: Use create_agent to spin up a Builder agent to edit source code, Dockerfiles, or CLAUDE.md without directly editing the running agent.
  • Managed tool integration: Install system or npm packages via admin-approved workflows and automatically restart containers as needed.
  • MCP server wiring: Add and configure MCP servers with controlled approval and seamless runtime integration.
  • Safe workflow boundaries: Changes are reviewed in a builder context and reflected on the next container start for persistence.
  • Use Case: A developer wants to add a new capability to their agent by editing source files within /workspace/agent and wiring up a new tool, then tests in a sandbox before going live.

Quick Start

Instruct the builder to apply a specific change by describing files and acceptance criteria, then review the builder's summary after it reports back.

Frequently Asked Questions about self-customize

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely customize my agent environment and install new packages?

Agent self-customization delegates code edits and tool integrations to a builder agent, separating runtime workspace edits from container-level changes. This keeps a safe boundary so modifications are reviewed in a builder context before going live.

How do I wire up an MCP server to my workspace agent?

MCP server wiring is managed through admin-approved workflows that configure servers and integrate them at runtime. The builder agent applies the configuration, which becomes persistent upon the next container restart.

Can I edit source code and Dockerfiles without breaking my running agent?

Yes, you delegate code changes to a builder agent that edits source files and Dockerfiles without touching the running agent. Changes are tested in a builder context and applied on the next container restart.

Do I need admin approval to install system packages in my agent container?

Yes, installing system or npm packages requires admin approval. This managed workflow ensures safe integration and automatically restarts the container so non-trivial changes take effect.

Why are my agent workspace changes not persisting across container restarts?

Changes persist when applied through the builder agent and reflected on the next container start. Runtime edits that bypass this controlled boundary are not saved, so approved changes are required for persistence.