Skip to content

From the author

Codex-only team orchestration: run a named team of cooperating Codex workers with durable, script-managed state. MUST USE when the user asks Codex to create, run, coordinate, inspect, archive, or delete a team of agents/threads/sessions, or to work on something as a team in parallel. FIRST inspects the active tool surface (checking tool_search for deferred tools) and tells the user the route: native MultiAgentV2 agents (flat spawn_agent with task_name) when available, Codex App threads as the fallback, or a plain-subagent split when neither set exists. The main session is always the leader; members are defined by a concrete part, ownership area, or perspective - never a vague job role; a bundled cross-platform script writes the .omo/teams state plus an auto-generated member field manual. Use a team when the work is not perfectly isolated but parallelizing helps; use plain subagents when scope is perfectly isolated or the goal is ambiguous. Triggers: team mode, teammode, make a team, run as a team, team of age

Install

npx skills add code-yeongyu/oh-my-openagent --skill teammode -a claude-code

Installs to .claude/skills/teammode/ · Each command fetches the skill straight from GitHub with the open skills CLI.

No download: this skill’s licence (Custom or unclear) does not let us redistribute its files. The install commands fetch them from GitHub instead.

Want your agent to suggest skills while you type? See how to use skills from your IDE.

Safety checks on SKILL.md

  • Ships scripts we have not reviewedLow

Why 84

Security85
Provenance95
Maintenance100
Licence45
Adoption75

aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.

Similar skills

From the same category, best-trusted first. This skill is not indexed for matching yet, so these are its neighbours by category.

Ratings & reviews

—

no reviews

Tried this skill? Rate it to help others. Sign in

    Discussion

    Join the discussion. Sign in