Venture Spawner

Instant agent hiring. Takes job postings from the orchestrator and fills them with properly configured sub-agents. Handles context passing, timeout enforceme...

This skill appears to implement an agent-spawning orchestration flow but contains several items that could expose secrets or sensitive files if not constrained. Before installing, confirm: (1) where JOB_BOARD.md and referenced files live and who can write them; (2) that the platform enforces strict allowlists/deny-lists so spawned tasks cannot receive .env contents, private keys, or personal files unless explicitly authorized; (3) whether 'Include SSH commands for droplet' implies access to SSH private keys — if so, deny or centralize SSH access rather than embedding keys in tasks; (4) how access to other skills' files and OpenClaw docs is controlled; and (5) add explicit sanitization rules in the orchestrator (strip credentials, redact secrets, require user confirmation before spawning buckets that reference named personal files). If you proceed, limit which buckets can spawn agents, require explicit approval for any job that references SSH or named personal data, and monitor spawned-agent activity and logs for unexpected outbound connections or file accesses.

Type: OpenClaw Skill Name: venture-spawner Version: 1.0.0 The 'venture-spawner' skill is a robust orchestration tool designed to manage sub-agent lifecycles based on a job board (JOB_BOARD.md). It implements several safety and operational best practices, such as a strict concurrency limit (max 3 agents), dependency resolution logic, and explicit instructions in SKILL.md to avoid modifying .env files with real credentials. While it handles high-privilege tasks like spawning agents and passing SSH context for infrastructure management, these actions are well-documented and aligned with the stated purpose of automated project management without any signs of malicious intent or data exfiltration.