spawn-skill

Spawn disposable child agents in Docker for sandboxed experimentation.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/misunders2d/ori --skill spawn-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spawn-skill
Source: https://github.com/misunders2d/ori/tree/main/skills/spawn-skill
Command: npx skills add https://github.com/misunders2d/ori --skill spawn-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spawns disposable child agents in Docker to enable sandboxed experimentation and isolated testing without risking the main environment.

Core Features & Use Cases

  • Create per-session disposable agents that inherit the parent codebase but run in isolation.
  • Export DNA back to the parent for commit after successful validation of changes.
  • Prevent reboot and Git tooling inside the child to maintain safe sandbox constraints.

Quick Start

Spawn a disposable child container to test risky changes in isolation, then export the results back to the parent for integration.

Frequently Asked Questions about spawn-skill

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

FAQPage Schema
How do I run isolated tests for risky refactors in Docker without affecting my main environment?

You can spawn disposable child agents in Docker sandboxes to run isolated tests for risky refactors. Each child inherits your parent codebase but runs in a per-session sandbox directory, preventing changes from impacting the main environment until validated.

Can I transfer code changes from a Docker sandbox back to my parent project?

Yes, you can transfer validated changes from a Docker sandbox back to the parent project using the export_dna mechanism. This moves successful results out of the disposable child agent for final integration and commit.

What's the best way to create per-session sandboxes for feature experiments?

The best way to create per-session sandboxes for feature experiments is by spawning disposable child agents in Docker. This provides isolated testing environments using dedicated sandbox directories identified by a unique session ID.

Does spawning child agents in Docker prevent Git operations inside the sandbox?

Yes, spawning child agents in Docker maintains safe sandbox constraints by preventing reboot and Git tooling inside the child. This ensures the disposable agent cannot directly commit changes or modify the parent system.

What do I need to set up before spawning disposable Docker agents for isolated testing?

To spawn disposable Docker agents for isolated testing, you need a parent Docker image and per-session sandbox directories structured under data/sandbox/<session_id>/. These provide the base environment and isolated workspace for the child agent.