🎁 Get the FREE AI Skills Starter Guide β€” Subscribe β†’
BytesAgainBytesAgain
BytesAgain β€Ί Skills β€Ί Lightweight Team Orchestration
πŸ¦€ ClawHub

Lightweight Team Orchestration

by @openlark

Facilitates simple multi-agent team collaboration with defined roles, task distribution, and versioned artifact management via a streamlined folder structure.

Versionv1.0.0
Downloads631
#clawhub
TERMINAL
clawhub install lightweight-team-orchestration

πŸ“– About This Skill

name: lightweight-team-orchestration description: Lightweight multi-agent team orchestration. Output structure simplified to two folders: agents/ and projects/.

Lightweight Team Orchestration

A lightweight multi-agent team collaboration skill with a simplified output structure focused on core deliverables.

Use Cases

  • Creating simple teams with 2+ agents
  • Agent role definition and task distribution
  • Agent output artifact management (with versioning)
  • Lightweight collaboration workflows (no complex workflow engine required)

    • Quick Start

    Output Structure

    [TEAM_NAME]/
β”œβ”€β”€ agents/                   # Agent role definitions
β”‚   β”œβ”€β”€ orchestrator/         # Orchestrator
β”‚   β”‚   └── SOUL.md           # Role definition
β”‚   β”œβ”€β”€ builder/              # Executor
β”‚   β”‚   └── SOUL.md
β”‚   └── reviewer/             # Reviewer (optional)
β”‚       └── SOUL.md
└── projects/                 # Output artifacts (with versioning)
    β”œβ”€β”€ v1.0.0/               # Version directory
    β”‚   β”œβ”€β”€ builder.md        # Builder output
    β”‚   └── reviewer.md       # Reviewer output
    └── v1.1.0/               # Next version

    Workflow

    1. Create Agent Roles β†’ Create SOUL.md for each agent under agents/ 2. Distribute Tasks β†’ Launch agents using sessions_spawn 3. Collect Artifacts β†’ Store artifacts in projects/v{version}/ 4. Version Management β†’ Create a new version directory for each delivery

    Agent Role Definitions

    agents/orchestrator/SOUL.md

    # Orchestrator
    Responsibilities
    

  • Task distribution and progress tracking
    • 

  • Coordination between agents
    • 

  • Artifact version management
    • Behaviors
    

  • Use high-reasoning model
    • 

  • Keep task status updated
    •

    agents/builder/SOUL.md

    # Executor
    Responsibilities
    

  • Execute specific tasks
    • 

  • Produce deliverables
    • Behaviors
    

  • Deliver according to specifications
    • 

  • Annotate version number
    •

    agents/reviewer/SOUL.md (optional)

    # Reviewer
    Responsibilities
    

  • Verify output quality
    • 

  • Propose improvement suggestions
    •

    Task Distribution

    Launch agents using sessions_spawn:

    Task: [Task description]
Output: projects/v{version}/{agent}.md
Verify: [Verification method]

    Version Management

  • Initial version: v1.0.0
  • Each iteration: Increment version number
  • Preserve history: All versions retained in projects/

    • When to Use

  • Simple 2-3 person teams
  • No complex workflow engine required
  • Focus on artifact delivery over process

    • When Not to Use

  • Complex multi-stage workflows
  • Real-time status tracking β†’ Use task boards
  • Large-scale agent coordination

    • ⚑ When to Use

    TriggerAction
    - No complex workflow engine required
    - Focus on artifact delivery over process

    πŸ’‘ Examples

    Output Structure

    [TEAM_NAME]/
β”œβ”€β”€ agents/                   # Agent role definitions
β”‚   β”œβ”€β”€ orchestrator/         # Orchestrator
β”‚   β”‚   └── SOUL.md           # Role definition
β”‚   β”œβ”€β”€ builder/              # Executor
β”‚   β”‚   └── SOUL.md
β”‚   └── reviewer/             # Reviewer (optional)
β”‚       └── SOUL.md
└── projects/                 # Output artifacts (with versioning)
    β”œβ”€β”€ v1.0.0/               # Version directory
    β”‚   β”œβ”€β”€ builder.md        # Builder output
    β”‚   └── reviewer.md       # Reviewer output
    └── v1.1.0/               # Next version

    Workflow

    1. Create Agent Roles β†’ Create SOUL.md for each agent under agents/ 2. Distribute Tasks β†’ Launch agents using sessions_spawn 3. Collect Artifacts β†’ Store artifacts in projects/v{version}/ 4. Version Management β†’ Create a new version directory for each delivery