openteams

Define multi-agent team structures via YAML templates with role inheritance and loadouts.

Updated Feb 7, 2026
One-click install
npx skills add https://github.com/alexngai/openteams --skill openteams
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openteams
Source: https://github.com/alexngai/openteams/tree/main
Command: npx skills add https://github.com/alexngai/openteams --skill openteams

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires commander, js-yaml, and includes scripts (resource) components.

What problem does it solve?

OpenTeams solves the fragmentation in multi-agent systems by providing a unified definition layer for team structures, ensuring that roles, communication topologies, and agent capabilities are consistent across different runtime environments.

Core Features & Use Cases

  • YAML Team Templates: Declare roles, spawn rules, and communication channels in a single, portable format.
  • Role Inheritance: Compose agent capabilities using a robust inheritance system with cycle detection.
  • Loadouts: Bundle skills, MCP servers, and permissions into reusable units that can be bound to any role.
  • Use Case: A development team can define a standard "Security Auditor" loadout and apply it to multiple roles across different team templates, ensuring consistent security enforcement without duplicating configuration.

Quick Start

Use the openteams cli to validate the team template located in the current directory.

Frequently Asked Questions about openteams

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define multi-agent team structures using YAML templates?

Role inheritance composes agent capabilities through a robust system with cycle detection, allowing you to build specialized roles from base definitions. Loadouts bundle skills, MCP servers, and permissions into reusable units that bind to any role.

How do I validate a multi-agent team configuration before deployment?

You validate multi-agent team configurations by running the openteams CLI against the YAML template in your current directory. This checks the structure of roles, communication topologies, and loadouts to ensure consistency before execution.

Can I reuse agent permissions and MCP servers across different roles?

Yes, loadouts bundle skills, MCP servers, and permissions into reusable units that can be bound to any role. A standard loadout, such as a Security Auditor, can be applied across multiple team templates to ensure consistent enforcement without duplicating configuration.

What is the best way to standardize agent communication topologies across different runtimes?

The best way to standardize agent communication topologies is using a unified YAML definition layer that decouples team structure from execution. This ensures roles, spawn rules, and communication channels remain consistent across different runtime environments.

Does this approach support generating agent prompts and skill documentation for the Multi-Agent Protocol?

Yes, the system facilitates the generation of agent prompts, skill documentation, and content-addressed bundles specifically for the Multi-Agent Protocol. This ensures teams are consistently configured and ready for orchestrated execution.