agent-spawner

Name: agent-spawner
Availability: InStock
Author: austineral

Clone the current OpenClaw agent configuration and provision a Docker-based instance.

Updated Feb 19, 2026

Search Tags:#automation #onboarding #docker #deploy #openclaw #agent-spawner #config-carryover

Ready to run

npx skills add https://github.com/AustinEral/agent-spawner --skill agent-spawner

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: agent-spawner
Source: https://github.com/AustinEral/agent-spawner/tree/main
Command: npx skills add https://github.com/AustinEral/agent-spawner --skill agent-spawner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spawn a new OpenClaw agent through conversation. Uses official Docker setup and non-interactive onboarding, carries over API keys, tools, plugins, and skills from the current agent. User answers 2-3 questions.

Core Features & Use Cases

Read current agent's config (API keys, model, tools, plugins, and skills) from the existing installation.
Carry over provider, API keys, model, tools, plugins, and non-bundled skills to the new agent.
Guide user through deployment choices (where to deploy, naming, special constraints) and perform non-interactive onboarding.
Deploy using the official OpenClaw Docker setup and patch the new agent with the current configuration, then provide a URL and token.

Quick Start

Tell me where to deploy, name the new agent, and note any special constraints to begin provisioning.

Frequently Asked Questions about agent-spawner

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

FAQPage Schema

How do I deploy a new OpenClaw agent using Docker?▼

OpenClaw agent deployment with Docker is automated by cloning the workspace, reading current configuration, and provisioning a containerized instance. You answer 2-3 questions about deployment location and constraints, and it patches the new agent with your existing API keys, tools, and skills.

Can I carry over my API keys and plugins when spawning another agent?▼

Yes, you can carry over API keys and plugins. The skill reads provider details, API keys, models, tools, plugins, and non-bundled skills from your current agent and patches them directly onto the newly deployed instance during the onboarding process.

What deployment options are supported for provisioning an OpenClaw instance?▼

Supported deployment options for provisioning an OpenClaw instance include local Docker, remote SSH, and bare metal. You select your preferred environment during the guided conversation, and the skill configures the official Docker setup accordingly.

Does the agent-spawner require interactive configuration for onboarding?▼

Onboarding is non-interactive except for 2-3 initial questions. The skill automatically extracts provider and API key details, models, and tools from your current installation to patch the config on the running instance without further manual input.

What's the best way to automate OpenClaw agent creation with existing tools?▼

Automating OpenClaw agent creation is best handled by extracting current workspace configurations and deploying via official Docker setup. This skill provisions the instance, carries over non-bundled skills, and patches the running config to deliver a functional agent URL and token.

Are there limitations when cloning workspace configurations to a remote SSH deployment?▼

Limitations depend on your remote SSH environment's compatibility with the official OpenClaw Docker setup. The skill patches the config on the running instance, but you must ensure your remote target supports Docker provisioning and network accessibility for the delivered URL.