Spawner for Openclaw

Spawner is a high-performance orchestration skill that automates the hiring, configuration, and monitoring of AI sub-agents to execute complex job board tasks.

dodge1218
v1.0.0
Mar 31, 2026
0
709
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install venture-spawner

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install venture-spawner using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is Spawner?

Spawner acts as the critical bridge between high-level project scoping and tactical execution within the Openclaw Skills ecosystem. It monitors a central JOB_BOARD.md file, automatically hiring the most appropriate sub-agents based on specific task buckets such as BUILD, OUTREACH, or STRATEGY. By managing the full lifecycle of these agents, it ensures that technical goals are met without manual intervention.

This skill is designed for developers and automation architects who need to scale their AI workflows. It solves the complexity of manual agent configuration by automatically injecting necessary context, enforcing strict timeouts, and managing git-based completion tracking. Spawner ensures that every sub-agent operates within a controlled environment, adhering to project-specific SOPs and security constraints.

Spawner Use Cases

  • Automatically spawning developer agents to fix bugs or build features based on project issues.
  • Orchestrating parallel outreach campaigns or sales research with dedicated sub-agents.
  • Automating system maintenance and skill testing across multiple workspaces.
  • Managing complex multi-step dependencies where one agent's output is required for the next task.
  • Enforcing resource limits and concurrency caps in high-volume AI automation environments.

How Spawner Works

  1. Spawner reads the workspace/JOB_BOARD.md file to identify pending job postings and their technical requirements.
  2. It verifies the current active sub-agent count to ensure it stays within the strict concurrency limit of 3 active agents.
  3. The skill checks for task dependencies, queuing jobs until their prerequisites are marked as completed.
  4. It selects a configuration template based on the job bucket (e.g., BUILD, SALES) and injects relevant context files and acceptance criteria.
  5. Sub-agents are spawned via session commands with specific labels, timeouts, and task descriptions.
  6. Spawner monitors for completion events, validates artifacts (like git commits or file outputs), and updates the job status on the board.

Spawner Setup

To activate Spawner within your Openclaw Skills environment, ensure your orchestrator is configured to write to the JOB_BOARD.md file. You can also trigger it manually via the CLI:

# Direct manual spawn for a specific task
openclaw run spawner "spawn an agent to do [task description]"

# List active sub-agents to check capacity
openclaw subagents list

Spawner Data Schema & Taxonomy

Spawner manages a structured workflow through the JOB_BOARD.md file and session metadata. The data taxonomy includes:

Field Description
Bucket Functional category (BUILD, OUTREACH, STRATEGY, etc.)
Status Lifecycle state: Pending (⏳), In Progress (🔄), Done (✅), or Failed (❌)
Context Injected file references and SOPs (limited to 2K tokens)
Artifacts Links to generated files, commit hashes, or URLs
Metadata Session keys, timeouts, and dependency mapping

Spawner Advanced Features

  • Smart Concurrency Management: Automatically queues jobs when the maximum limit of 3 sub-agents is reached.
  • Context Injection Logic: Curates relevant project memory and SOPs to ensure sub-agents have high situational awareness without token waste.
  • Automated Failure Recovery: Implements retry logic for timeouts and escalates critical system failures to the primary operator.
  • Dependency Resolution: Sophisticated wave-based execution that waits for prerequisite tasks to finalize before spawning downstream agents.
  • Integrated Git Workflows: Mandates build passes and descriptive git commits as part of the sub-agent acceptance criteria.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*