Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Orchestrates multi-agent task delegation and workflows with audit logging, checkpoint approvals, and agent learning for coordinated project execution.
Orchestrates multi-agent task delegation and workflows with audit logging, checkpoint approvals, and agent learning for coordinated project execution.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Multi-agent task delegation and process orchestration with audit logging and agent learning capabilities.
# Single task - auto-routed node scripts/colony.mjs dispatch "find top 5 time-series databases" # Multi-stage process node scripts/colony.mjs process validate-idea --context "AI meal planning for parents" node scripts/colony.mjs process-status # check progress node scripts/colony.mjs approve abc123 # continue past checkpoint # Check audit stats node scripts/colony.mjs audit # View agent memory node scripts/colony.mjs memory scout
AgentRoleSpecializationscuttleresearcherQuick searches, lookups, fact-findingscoutresearcherDeep market/competitor research, intelligenceforecastanalystData analysis, trends, projectionspincercoderWriting, debugging, refactoring codeshellopsGit, deployments, system tasksforgeproductPRDs, specs, roadmapsledgerfinancePricing, costs, business casesmusecreativeBrainstorming, naming, ideasscribewriterBlog posts, docs, long-form contentquillcopywriterLanding pages, sales copy, adsechosocialTweets, social posts, promotionsentryqaTesting, bug verification
node scripts/colony.mjs dispatch "research best practices for API rate limiting" Automatically detects the best agent based on task keywords.
node scripts/colony.mjs assign scout "find top 5 time-series databases" node scripts/colony.mjs assign pincer "refactor the auth module to use JWT" node scripts/colony.mjs assign shell "deploy the staging branch"
node scripts/colony.mjs status Shows all agents and their current tasks.
node scripts/colony.mjs results # Latest completed task node scripts/colony.mjs results abc123 # Specific task by ID
node scripts/colony.mjs history # Last 10 completed/failed node scripts/colony.mjs history --limit 20 # Custom limit
Processes are multi-stage workflows that chain agents together.
node scripts/colony.mjs processes
node scripts/colony.mjs process <process-name> --context "description" Examples: node scripts/colony.mjs process validate-idea --context "AI-powered meal planning for busy parents" node scripts/colony.mjs process content-pipeline --context "How to use vector databases for RAG" node scripts/colony.mjs process product-launch --context "Life Lunch ritual kit for parents" node scripts/colony.mjs process bug-triage --context "Login fails with OAuth on mobile"
node scripts/colony.mjs process-status # Show latest run node scripts/colony.mjs process-status abc123 # Specific run Shows: current stage, completed stages, checkpoints, output files.
node scripts/colony.mjs runs # All runs (active, paused, completed) node scripts/colony.mjs runs --limit 5 # Last 5
When a process hits a checkpoint, it pauses for human approval: node scripts/colony.mjs approve abc123 Also used to retry a failed stage.
node scripts/colony.mjs cancel abc123
Track agent performance, task statistics, and system health.
node scripts/colony.mjs audit Shows global stats, per-agent summary, and recent events.
node scripts/colony.mjs audit agent scout node scripts/colony.mjs audit agent pincer Shows detailed stats for a specific agent including: Total tasks, success rate Average duration Token usage Recent failures
node scripts/colony.mjs audit log # Last 20 events node scripts/colony.mjs audit log --limit 50 # More events
node scripts/colony.mjs audit slow # Top 10 slowest node scripts/colony.mjs audit slow --limit 20
node scripts/colony.mjs audit failures # Last 10 failures node scripts/colony.mjs audit failures --limit 20
Agents learn from experience and share knowledge.
Record feedback for completed tasks: node scripts/colony.mjs feedback abc123 "Great research, but needed more pricing data"
Each agent has a persistent memory file with lessons learned: # View an agent's memory node scripts/colony.mjs memory scout # Add a lesson node scripts/colony.mjs memory scout add "Always check publication dates on research sources" # Add to specific sections node scripts/colony.mjs memory scout add "Use bullet points for clarity" --pattern node scripts/colony.mjs memory scout add "Missed competitor X in analysis" --mistake node scripts/colony.mjs memory scout add "Prefers markdown tables over lists" --pref
Cross-agent insights and lessons: # View all shared learnings node scripts/colony.mjs learn # Add a learning node scripts/colony.mjs learn add "validate-idea works better with 3 competitors max" --category process node scripts/colony.mjs learn add "Always verify API rate limits early" --category technical --source run-abc123
Shared context all agents can access: # View global context node scripts/colony.mjs context # Set preferences node scripts/colony.mjs context set preferences.codeStyle "TypeScript, functional" node scripts/colony.mjs context set preferences.timezone "America/Chicago" # Add active facts (temporary context) node scripts/colony.mjs context add-fact "We're targeting enterprise customers" node scripts/colony.mjs context add-fact "Launch deadline is Q2 2024" # Add decisions node scripts/colony.mjs context add-decision "Use Postgres over MySQL" --project "life-lunch" # Add projects node scripts/colony.mjs context add-project "life-lunch"
Review recent activity and generate insights: node scripts/colony.mjs retro # Last 7 days node scripts/colony.mjs retro --days 14 # Last 14 days Shows: Task completion summary Per-agent stats Failure patterns Suggested learnings
Validate a business idea end-to-end Stages: brainstorm β research β analyze β spec β estimate Checkpoints: after analyze Output: business-case.md
End-to-end product launch Stages: research β spec β build β copy Checkpoints: after spec, after copy Output: market-brief.md, prd.md, code/, landing-copy.md
Research, write, publish, promote content Stages: research β draft β review β publish β promote Checkpoints: review (human reviews draft) Output: research.md, draft.md, social-posts.md
Reproduce, fix, deploy bug fixes Stages: reproduce β fix β test β deploy Checkpoints: none (fast path) Output: bug-report.md, fix-summary.md
Deep dive on a customer segment Stages: identify β pain-points β validate β synthesize Checkpoints: none Output: customer-profile.md, insights.md
Create a full landing page Stages: strategy β copy β review β build Checkpoints: after copy review Output: strategy.md, copy.md, landing.html, landing.css
Start - Process creates a run entry and spawns first stage agent Execute - Each stage runs with inputs from previous stages Checkpoint - If stage is a checkpoint, process pauses for approval Continue - After approval, next stage runs Complete - All stages done, outputs in colony/context/<run-id>/
{context} in task templates is replaced with your --context value Stage outputs are saved to colony/context/<run-id>/<output-file> Next stage reads inputs from previous stage's output files Agent memory and global context are injected into prompts Full task history in tasks.json
Stages that share the same parallel_group run concurrently: stages: - id: spec agent: forge inputs: [analysis.md] parallel_group: "final" # Stages with same group run together - id: estimate agent: ledger inputs: [analysis.md] parallel_group: "final" # Same group = parallel execution When the process reaches a parallel group: All consecutive stages with the same parallel_group are collected All stages spawn concurrently (using Promise.all()) Process waits for ALL parallel stages to complete If any stage fails, the entire group fails Checkpoints work per-group (pause after all parallel stages complete) Output shows parallel execution clearly: βββ Parallel Group: final (2 stages) βββ β Stage 4: spec (forge) β Stage 5: estimate (ledger) --- [PARALLEL] Stage 4/5: spec --- --- [PARALLEL] Stage 5/5: estimate --- βββ Parallel Group: final completed βββ When to use parallel groups: Stages that read the same inputs (no dependencies on each other) Build + copy tasks (both depend on spec, not on each other) Multiple analyses of the same data Independent research threads Processes with parallel stages: validate-idea: spec + estimate run in parallel product-launch: build + copy run in parallel
Colony can send notifications when processes hit checkpoints, complete, or fail. Notifications use openclaw cron wake to alert you. Configuration (colony/config.yaml): notifications: enabled: true # Master switch for all notifications on_checkpoint: true # Notify when process pauses at checkpoint on_complete: true # Notify when process finishes on_failure: true # Notify when process/stage fails Manage via CLI: # View current config node scripts/colony.mjs config # Disable all notifications node scripts/colony.mjs config set notifications.enabled false # Enable only failure notifications node scripts/colony.mjs config set notifications.on_checkpoint false node scripts/colony.mjs config set notifications.on_complete false node scripts/colony.mjs config set notifications.on_failure true Notification examples: π Colony checkpoint: Process "validate-idea" paused after stage "analyze". To continue: colony approve abc123 β Colony complete: Process "validate-idea" finished in 120s. Run ID: abc123 β Colony failed: Process "validate-idea" failed at stage "research". Error: Agent timed out. Run ID: abc123
Checkpoints pause the process for human review. Two ways to define: In process checkpoints array (after that stage completes) As a standalone stage with checkpoint: true (human-only review step)
skills/colony/ βββ SKILL.md # This file βββ package.json # Dependencies (js-yaml) βββ colony/ β βββ agents.yaml # Agent definitions β βββ processes.yaml # Process definitions β βββ config.yaml # Notification & behavior config β βββ tasks.json # Task queue and history β βββ runs.json # Process run tracking β βββ feedback.json # Task feedback storage β βββ learnings.yaml # Shared cross-agent learnings β βββ global-context.json # Shared context for all agents β βββ audit/ β β βββ log.jsonl # Append-only event log β β βββ global.json # Aggregate statistics β β βββ agents/ # Per-agent statistics β β βββ scout.json β β βββ pincer.json β β βββ ... β βββ memory/ # Per-agent persistent memory β β βββ scout.md β β βββ pincer.md β β βββ ... β βββ context/ # Per-task and per-run outputs β βββ <run-id>/ βββ scripts/ βββ colony.mjs # Main CLI βββ colony-worker.mjs # Background agent executor βββ agent-wrapper.mjs # Task lifecycle utilities βββ audit.mjs # Audit system functions βββ learning.mjs # Learning system functions
The audit log tracks these events: EventFieldstask_startedtaskId, agent, processRunId?, stage?task_completedtaskId, agent, durationMs, tokens, successtask_failedtaskId, agent, durationMs, errorcheckpoint_waitingrunId, stagecheckpoint_approvedrunId, stagecheckpoint_rejectedrunId, stage, reasonprocess_startedrunId, processId, contextprocess_completedrunId, processId, durationMsfeedback_receivedtaskId, agent, feedback
Edit colony/agents.yaml: agents: myagent: role: specialist description: > What this agent does... model: anthropic/claude-sonnet-4 triggers: - keyword1 - keyword2 After adding, create their memory file: touch colony/memory/myagent.md
Edit colony/processes.yaml: processes: my-process: description: "What this process does" triggers: [keyword1, keyword2] stages: - id: stage1 agent: scout task: "Do something with: {context}" outputs: [output1.md] - id: stage2 agent: pincer task: "Next step based on previous" inputs: [output1.md] outputs: [output2.md] checkpoints: [stage1] # Optional: pause after these stages
Works with OpenClaw's agent sessions. Dispatch/Assign (async): Tasks are spawned in the background and the CLI returns immediately. Use colony status to monitor progress and colony results <task-id> to view output. Process stages (blocking): Multi-stage processes run sequentially, waiting for each stage to complete before proceeding. This ensures proper data flow between stages and checkpoint handling. Each agent receives: Their role description Lessons from their memory file Active facts from global context Project/preference context
node scripts/colony.mjs process validate-idea \ --context "Subscription box for home coffee brewing experiments" Watch as it flows: brainstorm β research β analyze β (checkpoint) β spec β estimate
node scripts/colony.mjs process content-pipeline \ --context "Why RAG is eating traditional search" Stages: research β draft β (human review) β publish β promote
node scripts/colony.mjs dispatch "compare Pinecone vs Weaviate vs Milvus" Auto-routes to scout, returns comparison.
# After several tasks, check overall health node scripts/colony.mjs audit # Deep dive into a struggling agent node scripts/colony.mjs audit agent pincer node scripts/colony.mjs audit failures # Add learnings from issues node scripts/colony.mjs memory pincer add "Handle file not found errors gracefully" --mistake
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.