Team Packager
Export your agent team configuration as shareable YAML packages. Import team templates from others to instantly set up your Dev Flow environment.
When to Use
- •Sharing your agent team setup with others
- •Backing up your agent configuration
- •Setting up a new machine with your existing config
- •Importing a team template from the marketplace
- •Creating team templates for different project types
Input Handling
For Export:
- •
team_name: Optional custom name (defaults to workspace name) - •
agents: Optional list of specific agents to include (defaults to all) - •
output_path: Optional save location (defaults to current directory)
For Import:
- •
package_path: Path to devflow-team.yaml file - •
workspace: Optional target workspace (defaults to current) - •
rename_prefix: Optional prefix for agent IDs to avoid conflicts
Instructions
Export Flow
- •
Read current configuration
- •Parse
~/.openclaw/openclaw.jsonfor agent definitions - •Read workspace files (AGENTS.md, SOUL.md, IDENTITY.md, etc.)
- •Collect agent identities and models
- •Parse
- •
Generate package
- •Create YAML with all agent configs
- •Include workspace file templates
- •List required skills
- •Add metadata (version, created, author)
- •
Output package file
- •Save to
devflow-team.yaml - •Provide summary of what's included
- •Save to
Import Flow
- •
Validate package
- •Check YAML syntax
- •Verify required fields
- •Check for agent ID conflicts
- •
Create agents
- •Run
openclaw agents addfor each agent - •Set identities with
openclaw agents set-identity - •Copy workspace files
- •Run
- •
Configure skills
- •Verify required skills are available
- •Warn about missing skills
- •
Verify setup
- •List created agents
- •Show any warnings or manual steps needed
Required Output Sections
Export Output
markdown
## Team Package Created
**Package:** devflow-team.yaml
**Team Name:** {{team_name}}
**Agents:** {{agent_count}}
### Included Agents
| ID | Role | Model |
|----|------|-------|
{{#each agents}}
| {{id}} | {{role}} | {{model}} |
{{/each}}
### Workspace Files Included
- AGENTS.md
- SOUL.md
- IDENTITY.md
- USER.md (template)
### Required Skills
{{#each skills}}
- {{name}}
{{/each}}
### How to Use This Package
1. Copy `devflow-team.yaml` to target machine
2. Run: `team-packager import devflow-team.yaml`
3. Restart gateway: `openclaw gateway run --force`
Package saved to: {{output_path}}
Import Output
markdown
## Team Imported Successfully
**Package:** {{package_name}}
**Agents Created:** {{agent_count}}
**Workspace:** {{workspace_path}}
### Agents Created
| ID | Identity | Status |
|----|----------|--------|
{{#each agents}}
| {{id}} | {{identity.emoji}} {{identity.name}} | ✅ Created |
{{/each}}
### Next Steps
1. Restart gateway: `openclaw gateway run --force`
2. Verify agents: `openclaw agents list`
3. Run onboarding: "get started with dev flow"
### Notes
{{#if warnings}}
**Warnings:**
{{#each warnings}}
- {{this}}
{{/each}}
{{/if}}
Package Format (devflow-team.yaml)
yaml
# Dev Flow Team Package
version: "1.0"
metadata:
name: "SaaS Development Team"
description: "Full-stack team for SaaS application development"
author: "chad420"
created: "2026-02-06T00:00:00Z"
devflow_version: "1.0.0"
# Agent definitions
agents:
- id: main
role: orchestrator
model: anthropic/claude-opus-4-6
identity:
name: "Siberius"
emoji: "wolf"
subagents:
- codex
- night-shift
- id: backend
role: backend-engineer
model: anthropic/claude-opus-4-6
identity:
name: "Backend Engineer"
emoji: "wrench"
workspace: shared
- id: frontend
role: frontend-engineer
model: anthropic/claude-opus-4-6
identity:
name: "Frontend Engineer"
emoji: "art"
workspace: shared
- id: qa
role: qa-engineer
model: anthropic/claude-opus-4-6
identity:
name: "QA Engineer"
emoji: "test_tube"
workspace: shared
# Required skills for this team
skills_required:
- launch-planner
- test-engineer
- code-reviewer
- prodops-optimizer
- saas-deployment-ops
# Workspace file templates
workspace_files:
AGENTS.md: |
# Agent Workspace
This workspace is shared by the development team.
## Team Members
- Backend Engineer: APIs, databases, services
- Frontend Engineer: UI, components, styling
- QA Engineer: Testing, quality assurance
SOUL.md: |
# Team Soul
We build quality software together.
Each agent has their specialty, but we collaborate.
IDENTITY.md: |
# Team Identity
name: "Dev Team"
emoji: "rocket"
# Optional: Cron jobs to include
cron_jobs: []
# Optional: Channel bindings
channel_bindings: []
Guardrails
- •Never export secrets or API keys
- •Sanitize file paths (use relative paths)
- •Warn before overwriting existing agents
- •Validate YAML syntax before import
- •Check for circular dependencies in subagents
- •Respect user's existing agent configurations
Commands
/export-team
code
/export-team [team-name] /export-team "My SaaS Team" /export-team --agents backend,frontend,qa
/import-team
code
/import-team devflow-team.yaml /import-team ./templates/saas-team.yaml /import-team --prefix project1- devflow-team.yaml
Pre-Built Templates
SaaS Development Team
yaml
agents: [main, backend, frontend, infra, qa] skills: [launch-planner, test-engineer, saas-deployment-ops]
Mobile App Team
yaml
agents: [main, mobile-ios, mobile-android, qa] skills: [design-guide, test-engineer]
API/Backend Team
yaml
agents: [main, api-engineer, db-engineer] skills: [api-devex-architect, security-threat-modeler]
Solo Developer
yaml
agents: [main, codex] skills: [launch-planner, test-engineer, prodops-optimizer]
Trigger Patterns
javascript
if (/(export team|import team|package team|share team|team template|\/export-team|\/import-team|share my setup|backup agents)/i.test(objective)) {
// Run team-packager
}
Integration
Dependencies: None Triggers: devflow-onboarding (after import)
Version History
- •v1.0.0: Initial release with export/import