Agent skill · DevOps & Cloud

agent-factory

Bootstrap new 33GOD ecosystem agents with standardized configuration. Use when creating new agents, spawning workers, deploying Yi nodes, or when the user says "spin up an agent", "create a new agent", "deploy a new worker", or needs a new agent for a specific pipeline role. Handles workspace creation, config injection, skill installation, provider mirroring, channel binding, and 33GOD ecosystem onboarding (GOD Docs, Plane, Bloodbank, memory).

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill agent-factory-delorenj-00-ceiling --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 5 KB
Bundled scripts: none
Path: skills/agent/agent-factory-delorenj-00-ceiling/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Agent Factory Standardized bootstrap for 33GOD ecosystem agents. Every agent ships ready to: - Consume and produce Bloodbank events - Read/write GOD Docs - Track work on Plane boards - Communicate with Cack (boss) and peer agents - Use long-term vector memory - Authenticate against all configured providers ## Quick Start When the user requests a new agent, gather these parameters: | Parameter | Required | Description | |-----------|----------|-------------| | `id` | ✅ | Agent ID (lowercase, no spaces, e.g. `scout`) | | `name` | ✅ | Display name (e.g. `Scout`) | | `role` | ✅ | One of: `manager`, `exec`, `ic`, `contractor` (see Yi Node Flavors) | | `purpose` | ✅ | One-line mission statement | | `personality` | ❌ | Vibe/tone (defaults to "competent, concise, team-player") | | `channel` | ❌ | `telegram` (needs bot token) or `none` (sub-agent only) | | `telegram_bot_token` | ❌ | If channel=telegram, the BotFather token | | `telegram_account_id` | ❌ | Account ID for multi-bot setup (defaults to agent id) | | `model` | ❌ | Model override (defaults to ecosystem default) | | `skills` | ❌ | Additional skills beyond the base set | ## Bootstrap Procedure ### 1. Create Workspace ```bash bash

What's inside
Steps it walks through
  1. Quick Start
  2. Bootstrap Procedure
  3. 1. Create Workspace
  4. 2. Update Gateway Config
  5. 3. Restart Gateway
  6. 4. Send Onboarding Briefing
  7. Yi Node Flavors (Role Types)
  8. Base Skills (auto-installed via symlink)
  9. Template Files
  10. Provider Auth
  11. Conventions
Ships with 1 file
  • metadata.json
Commands it runs
bash /home/delorenj/.openclaw/skills/agent-factory/scripts/bootstrap.sh \
More from claude-skill-registry
All skills →
About this skill
What does the agent-factory skill do?

Bootstrap new 33GOD ecosystem agents with standardized configuration. Use when creating new agents, spawning workers, deploying Yi nodes, or when the user says "spin up an agent", "create a new agent", "deploy a new worker", or needs a new agent for a specific pipeline role. Handles workspace creation, config injection, skill installation, provider mirroring, channel binding, and 33GOD ecosystem onboarding (GOD Docs, Plane, Bloodbank, memory).

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill agent-factory-delorenj-00-ceiling --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going