doey-add-team — equipo de múltiples agentes doey-add-team, community, equipo de múltiples agentes, ide skills, herramienta CLI, administración de equipos, agente de IA, doey-add-team AI agent skill, doey-add-team for Claude Code

v1.0.0

Acerca de este Skill

Ideal para agentes Taskmaster y Subtaskmaster que necesitan una gestión eficiente de equipos basados en tmux. La habilidad doey-add-team es una herramienta CLI para crear equipos de múltiples agentes basados en Tmux

Características

Creación de equipos de múltiples agentes basados en Tmux
Administración de herramientas CLI
Administración eficiente de equipos

# Temas principales

FRIKKern FRIKKern
[3]
[1]
Actualizado: 4/4/2026

Skill Overview

Start with fit, limitations, and setup before diving into the repository.

Ideal para agentes Taskmaster y Subtaskmaster que necesitan una gestión eficiente de equipos basados en tmux. La habilidad doey-add-team es una herramienta CLI para crear equipos de múltiples agentes basados en Tmux

¿Por qué usar esta habilidad?

Permite a los agentes generar equipos desde archivos.team.md, aprovechando tmux para la automatización y colaboración de flujos de trabajo, con soporte para definiciones de paneles personalizadas y roles de agente.

Mejor para

Ideal para agentes Taskmaster y Subtaskmaster que necesitan una gestión eficiente de equipos basados en tmux.

Casos de uso accionables for doey-add-team

Automatización de la configuración de equipo desde archivos.team.md
Automatización del flujo de trabajo con tmux y agentes personalizados
Mejora de la colaboración mediante una gestión eficiente de equipos

! Seguridad y limitaciones

  • Requiere entorno tmux
  • Limitado a agentes Taskmaster y Subtaskmaster
  • No hay mensaje de confirmación para la generación de equipos

About The Source

The section below is adapted from the upstream repository. Use it as supporting material alongside the fit, use-case, and installation summary on this page.

Demo Labs

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ y pasos de instalación

These questions and steps mirror the structured data on this page for better search understanding.

? Preguntas frecuentes

¿Qué es doey-add-team?

Ideal para agentes Taskmaster y Subtaskmaster que necesitan una gestión eficiente de equipos basados en tmux. La habilidad doey-add-team es una herramienta CLI para crear equipos de múltiples agentes basados en Tmux

¿Cómo instalo doey-add-team?

Ejecuta el comando: npx killer-skills add FRIKKern/doey/doey-add-team. Funciona con Cursor, Windsurf, VS Code, Claude Code y más de 19 IDE adicionales.

¿Cuáles son los casos de uso de doey-add-team?

Los casos de uso principales incluyen: Automatización de la configuración de equipo desde archivos.team.md, Automatización del flujo de trabajo con tmux y agentes personalizados, Mejora de la colaboración mediante una gestión eficiente de equipos.

¿Qué IDE son compatibles con doey-add-team?

Esta skill es compatible con Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Usa la CLI de Killer-Skills para una instalación unificada.

¿Tiene limitaciones doey-add-team?

Requiere entorno tmux. Limitado a agentes Taskmaster y Subtaskmaster. No hay mensaje de confirmación para la generación de equipos.

Cómo instalar este skill

  1. 1. Abre tu terminal

    Abre la terminal o línea de comandos en el directorio de tu proyecto.

  2. 2. Ejecuta el comando de instalación

    Ejecuta: npx killer-skills add FRIKKern/doey/doey-add-team. La CLI detectará tu IDE o agente automáticamente y configurará la skill.

  3. 3. Empieza a usar el skill

    El skill ya está activo. Tu agente de IA puede usar doey-add-team de inmediato en el proyecto actual.

! Source Notes

This page is still useful for installation and source reference. Before using it, compare the fit, limitations, and upstream repository notes above.

Upstream Repository Material

The section below is adapted from the upstream repository. Use it as supporting material alongside the fit, use-case, and installation summary on this page.

Upstream Source

doey-add-team

Install doey-add-team, an AI agent skill for AI agent workflows and automation. Explore features, use cases, limitations, and setup guidance.

SKILL.md
Readonly
Upstream Repository Material
The section below is adapted from the upstream repository. Use it as supporting material alongside the fit, use-case, and installation summary on this page.
Upstream Source

Context

  • Session config: !cat /tmp/doey/*/session.env 2>/dev/null | head -20 || true
  • Current windows: !tmux list-windows -F '#{window_index} #{window_name}' 2>/dev/null || true
  • Available team defs: !ls -1 .team.md *.team.md .doey/*.team.md ~/.config/doey/teams/*.team.md 2>/dev/null || echo "(none found in common locations)"

Prompt

Spawn a team from a .team.md file. No confirmation. Taskmaster/Subtaskmaster only.

.team.md Format

markdown
1--- 2name: team-name 3description: What this team does 4--- 5## Panes 6| Pane | Role | Agent | Name | Model | 7|------|------|-------|------|-------| 8| 0 | manager | doey-manager | Team Lead | opus | 9| 1 | reviewer | - | Reviewer | opus | 10 11## Workflows 12| Trigger | From | To | Subject | 13|---------|------|----|---------| 14| stop | reviewer | manager | review_complete |

Step 1: Load session, try CLI first

bash
1RUNTIME_DIR=$(tmux show-environment DOEY_RUNTIME 2>/dev/null | cut -d= -f2-) 2source "${RUNTIME_DIR}/session.env" 3TEAM_NAME="${1:?Usage: /doey-add-team <name>}" 4 5if command -v doey >/dev/null 2>&1 && doey add-team "$TEAM_NAME" 2>/dev/null; then 6 echo "Team spawned via doey CLI"; exit 0 7fi

Step 2: Find and parse .team.md

bash
1TEAM_DEF="" 2for _search_dir in "$PROJECT_DIR" "$PROJECT_DIR/.doey" "${HOME}/.config/doey/teams" "$(dirname "$(command -v doey 2>/dev/null || echo /dev/null)")/../../share/doey/teams"; do 3 for _candidate in "${_search_dir}/${TEAM_NAME}.team.md" "${_search_dir}/${TEAM_NAME}"; do 4 [ -f "$_candidate" ] && { TEAM_DEF="$_candidate"; break 2; } 5 done 6done 7[ -z "$TEAM_DEF" ] && { echo "ERROR: '${TEAM_NAME}' not found"; exit 1; }
bash
1TEAMDEF_FILE="${RUNTIME_DIR}/teamdef_${TEAM_NAME}.env" 2TEAM_DESC=$(sed -n '/^---$/,/^---$/{ /^description:/{ s/^description:[[:space:]]*//; p; }; }' "$TEAM_DEF") 3 4PANE_COUNT=0 5PANE_DEFS="" 6_in_panes=false 7while IFS= read -r line; do 8 case "$line" in 9 "## Panes"*) _in_panes=true; continue ;; 10 "## "*) _in_panes=false; continue ;; 11 esac 12 [ "$_in_panes" = "false" ] && continue 13 echo "$line" | grep -q '^|[[:space:]]*Pane' && continue 14 echo "$line" | grep -q '^|[[:space:]]*-' && continue 15 echo "$line" | grep -q '^|' || continue 16 _pane=$(echo "$line" | cut -d'|' -f2 | sed 's/^[[:space:]]*//;s/[[:space:]]*$//') 17 _role=$(echo "$line" | cut -d'|' -f3 | sed 's/^[[:space:]]*//;s/[[:space:]]*$//') 18 _agent=$(echo "$line" | cut -d'|' -f4 | sed 's/^[[:space:]]*//;s/[[:space:]]*$//') 19 _name=$(echo "$line" | cut -d'|' -f5 | sed 's/^[[:space:]]*//;s/[[:space:]]*$//') 20 _model=$(echo "$line" | cut -d'|' -f6 | sed 's/^[[:space:]]*//;s/[[:space:]]*$//') 21 [ -z "$_pane" ] && continue 22 [ "$_agent" = "-" ] && _agent="" 23 PANE_DEFS="${PANE_DEFS}${_pane}|${_role}|${_agent}|${_name}|${_model} 24" 25 PANE_COUNT=$(( PANE_COUNT + 1 )) 26done < "$TEAM_DEF" 27 28[ "$PANE_COUNT" -eq 0 ] && { echo "ERROR: No pane definitions found in $TEAM_DEF"; exit 1; } 29echo "Parsed ${PANE_COUNT} panes from team definition" 30 31# Parse workflows 32WORKFLOWS="" 33_in_workflows=false 34while IFS= read -r line; do 35 case "$line" in 36 "## Workflows"*) _in_workflows=true; continue ;; 37 "## "*) _in_workflows=false; continue ;; 38 esac 39 [ "$_in_workflows" = "false" ] && continue 40 echo "$line" | grep -q '^|[[:space:]]*Trigger' && continue 41 echo "$line" | grep -q '^|[[:space:]]*-' && continue 42 echo "$line" | grep -q '^|' || continue 43 _trigger=$(echo "$line" | cut -d'|' -f2 | sed 's/^[[:space:]]*//;s/[[:space:]]*$//') 44 _from=$(echo "$line" | cut -d'|' -f3 | sed 's/^[[:space:]]*//;s/[[:space:]]*$//') 45 _to=$(echo "$line" | cut -d'|' -f4 | sed 's/^[[:space:]]*//;s/[[:space:]]*$//') 46 _subject=$(echo "$line" | cut -d'|' -f5 | sed 's/^[[:space:]]*//;s/[[:space:]]*$//') 47 [ -z "$_trigger" ] && continue 48 WORKFLOWS="${WORKFLOWS}${_trigger}|${_from}|${_to}|${_subject} 49" 50done < "$TEAM_DEF" 51 52# Write teamdef env 53cat > "${TEAMDEF_FILE}.tmp" << TDEF_EOF 54TEAM_DEF_NAME=${TEAM_NAME} 55TEAM_DEF_DESC=${TEAM_DESC} 56TEAM_DEF_FILE=${TEAM_DEF} 57TEAM_DEF_PANE_COUNT=${PANE_COUNT} 58TEAM_DEF_PANES=$(echo "$PANE_DEFS" | head -c -1 | tr '\n' ';') 59TEAM_DEF_WORKFLOWS=$(echo "$WORKFLOWS" | head -c -1 | tr '\n' ';') 60TDEF_EOF 61mv "${TEAMDEF_FILE}.tmp" "$TEAMDEF_FILE" 62echo "Teamdef written to $TEAMDEF_FILE"

Step 3: Create tmux window and split panes

bash
1tmux new-window -t "$SESSION_NAME" -n "$TEAM_NAME" -c "$PROJECT_DIR" 2sleep 0.5 3NEW_WIN=$(tmux display-message -t "$SESSION_NAME" -p '#{window_index}') 4 5for _s in $(seq 1 $((PANE_COUNT - 1))); do 6 tmux split-window -t "${SESSION_NAME}:${NEW_WIN}" -c "$PROJECT_DIR" 7done 8tmux select-layout -t "${SESSION_NAME}:${NEW_WIN}" tiled 9sleep 0.5 10 11MANAGER_PANE_IDX="" 12WORKER_PANES_LIST="" 13while IFS='|' read -r _pane _role _agent _name _model; do 14 [ -z "$_pane" ] && continue 15 tmux select-pane -t "${SESSION_NAME}:${NEW_WIN}.${_pane}" -T "T${NEW_WIN} ${_name}" 16 case "$_role" in 17 manager) MANAGER_PANE_IDX="$_pane" ;; 18 *) [ -n "$WORKER_PANES_LIST" ] && WORKER_PANES_LIST="${WORKER_PANES_LIST},${_pane}" || WORKER_PANES_LIST="${_pane}" ;; 19 esac 20done << PANE_INPUT 21$(echo "$PANE_DEFS") 22PANE_INPUT 23WORKER_COUNT=$(echo "$WORKER_PANES_LIST" | tr ',' '\n' | grep -c .)

Step 4: Write team env, update TEAM_WINDOWS

bash
1TEAM_FILE="${RUNTIME_DIR}/team_${NEW_WIN}.env" 2cat > "${TEAM_FILE}.tmp" << TEAM_EOF 3SESSION_NAME=${SESSION_NAME} 4PROJECT_DIR=${PROJECT_DIR} 5PROJECT_NAME=${PROJECT_NAME} 6WINDOW_INDEX=${NEW_WIN} 7GRID=custom 8TOTAL_PANES=${PANE_COUNT} 9MANAGER_PANE=${MANAGER_PANE_IDX} 10WORKER_PANES=${WORKER_PANES_LIST} 11WORKER_COUNT=${WORKER_COUNT} 12WORKTREE_DIR= 13WORKTREE_BRANCH= 14TEAM_DEF=${TEAM_NAME} 15TEAM_NAME=${TEAM_NAME} 16TEAM_DESC=${TEAM_DESC} 17TEAM_EOF 18mv "${TEAM_FILE}.tmp" "$TEAM_FILE" 19 20CURRENT_WINDOWS=$(grep '^TEAM_WINDOWS=' "${RUNTIME_DIR}/session.env" 2>/dev/null | cut -d= -f2 | tr -d '"') 21[ -n "$CURRENT_WINDOWS" ] && NEW_WINDOWS="${CURRENT_WINDOWS},${NEW_WIN}" || NEW_WINDOWS="${NEW_WIN}" 22TMPENV=$(mktemp "${RUNTIME_DIR}/session.env.tmp_XXXXXX") 23if grep -q '^TEAM_WINDOWS=' "${RUNTIME_DIR}/session.env"; then 24 sed "s/^TEAM_WINDOWS=.*/TEAM_WINDOWS=${NEW_WINDOWS}/" "${RUNTIME_DIR}/session.env" > "$TMPENV" 25else 26 cat "${RUNTIME_DIR}/session.env" > "$TMPENV" 27 echo "TEAM_WINDOWS=${NEW_WINDOWS}" >> "$TMPENV" 28fi 29mv "$TMPENV" "${RUNTIME_DIR}/session.env"

Step 5: Launch Claude instances (3s stagger)

bash
1while IFS='|' read -r _pane _role _agent _name _model; do 2 [ -z "$_pane" ] && continue 3 _model_flag="" 4 [ -n "$_model" ] && _model_flag="--model $_model" 5 _agent_flag="" 6 [ -n "$_agent" ] && _agent_flag="--agent \"$_agent\"" 7 _cmd="claude --dangerously-skip-permissions ${_model_flag} --name \"T${NEW_WIN} ${_name}\" ${_agent_flag}" 8 tmux send-keys -t "${SESSION_NAME}:${NEW_WIN}.${_pane}" "$_cmd" Enter 9 sleep 3 10done << LAUNCH_INPUT 11$(echo "$PANE_DEFS") 12LAUNCH_INPUT 13echo "All ${PANE_COUNT} Claude instances launched" 14 15bash -c " 16 eval \"\$(sed -n '/^_env_val()/,/^}/p' '${PROJECT_DIR}/shell/doey.sh')\" 17 eval \"\$(sed -n '/^_layout_checksum()/,/^}/p' '${PROJECT_DIR}/shell/doey.sh')\" 18 eval \"\$(sed -n '/^rebalance_grid_layout()/,/^}/p' '${PROJECT_DIR}/shell/doey.sh')\" 19 rebalance_grid_layout '${SESSION_NAME}' '${NEW_WIN}' '${RUNTIME_DIR}' 20"

Step 6: Brief the manager with team context

bash
1if [ -n "$MANAGER_PANE_IDX" ]; then 2 sleep 8 3 MGR_PANE="${SESSION_NAME}:${NEW_WIN}.${MANAGER_PANE_IDX}" 4 BRIEFING=$(mktemp "${RUNTIME_DIR}/task_XXXXXX.txt") 5 cat > "$BRIEFING" << BRIEF_EOF 6You are leading team "${TEAM_NAME}": ${TEAM_DESC} 7 8Your panes (from ${TEAM_DEF}): 9$(echo "$PANE_DEFS" | while IFS='|' read -r _p _r _a _n _m; do [ -n "$_p" ] && echo "- Pane $_p: $_n (role: $_r, agent: ${_a:-none}, model: $_m)"; done) 10 11Workflows: 12$(echo "$WORKFLOWS" | while IFS='|' read -r _t _f _to _s; do [ -n "$_t" ] && echo "- On $_t from $_f -> notify $_to (subject: $_s)"; done) 13 14Coordinate your team. Dispatch initial tasks to workers based on the team definition. 15BRIEF_EOF 16 17 tmux copy-mode -q -t "$MGR_PANE" 2>/dev/null 18 tmux send-keys -t "$MGR_PANE" Escape 19 tmux load-buffer "$BRIEFING" && tmux paste-buffer -t "$MGR_PANE" 20 sleep 1 21 tmux send-keys -t "$MGR_PANE" Escape 22 tmux send-keys -t "$MGR_PANE" Enter 23 rm "$BRIEFING" 24 echo "Manager briefed" 25fi

Step 7: Verify boot and report

bash
1sleep 5 2NOT_READY=0; DOWN_PANES="" 3while IFS='|' read -r _pane _role _agent _name _model; do 4 [ -z "$_pane" ] && continue 5 CHILD_PID=$(pgrep -P "$(tmux display-message -t "${SESSION_NAME}:${NEW_WIN}.${_pane}" -p '#{pane_pid}')" 2>/dev/null) 6 OUTPUT=$(tmux capture-pane -t "${SESSION_NAME}:${NEW_WIN}.${_pane}" -p 2>/dev/null) 7 if [ -z "$CHILD_PID" ] || ! echo "$OUTPUT" | grep -q "bypass permissions"; then 8 NOT_READY=$((NOT_READY + 1)); DOWN_PANES="$DOWN_PANES ${NEW_WIN}.$_pane" 9 fi 10done << VERIFY_INPUT 11$(echo "$PANE_DEFS") 12VERIFY_INPUT 13if [ "$NOT_READY" -eq 0 ]; then echo "All panes booted"; else echo "WARNING: ${NOT_READY} not ready:${DOWN_PANES}"; fi

Output: team name, window, layout, boot status. Teardown: /doey-kill-window ${NEW_WIN}. Bash 3.2. 3s stagger. Search: root → .doey/~/.config/doey/teams/ → share. Missing ## Workflows = skip. Agent - = no flag.

Habilidades relacionadas

Looking for an alternative to doey-add-team or another community skill for your workflow? Explore these related open-source skills.

Ver todo

openclaw-release-maintainer

Logo of openclaw
openclaw

Resumen localizado: 🦞 # OpenClaw Release Maintainer Use this skill for release and publish-time workflow. It covers ai, assistant, crustacean workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

333.8k
0
Inteligencia Artificial

widget-generator

Logo of f
f

Resumen localizado: Generate customizable widget plugins for the prompts.chat feed system # Widget Generator Skill This skill guides creation of widget plugins for prompts.chat. It covers ai, artificial-intelligence, awesome-list workflows. This AI agent skill supports Claude Code, Cursor, and

149.6k
0
Inteligencia Artificial

flags

Logo of vercel
vercel

Resumen localizado: The React Framework # Feature Flags Use this skill when adding or changing framework feature flags in Next.js internals. It covers blog, browser, compiler workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

138.4k
0
Navegador

pr-review

Logo of pytorch
pytorch

Resumen localizado: Usage Modes No Argument If the user invokes /pr-review with no arguments, do not perform a review. It covers autograd, deep-learning, gpu workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

98.6k
0
Desarrollador