Teams: purpose and common use cases
Teams is represented as a plugin from openai/plugins. Its catalog record points to plugins/teams and is grouped under Communication; install and source links are kept separate so the directory does not imply capabilities that are not present upstream.
Where Teams fits in an agent workflow
Teams is a Codex plugin associated with communication workflows. For Teams, the plugin layer sits one level above individual skills: they can package capabilities, integrations, MCP connections or supporting resources into one installable unit. For discovery, Teams is most relevant to teams and communication. The Teams plugin page is useful when you are choosing an integration first and then deciding which bundled capability to use.
What to check before using Teams
Before enabling Teams, check the source-backed metadata below for authentication, version, license and included capabilities. This record is tied to plugins/teams; the Teams upstream manifest remains the authority for installation requirements and behavior. Artifiner uses the Teams page to make comparison easier, not to replace the vendor or repository documentation.