skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
catlog22/claude-code-workflow48 installs

team-executor

Lightweight session execution skill. Resumes existing team-coordinate sessions for pure execution via team-worker agents. No analysis, no role generation -- only loads and executes. Session path required. Triggers on "Team Executor".

How do I install this agent skill?

npx skills add https://github.com/catlog22/claude-code-workflow --skill team-executor
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill is a session executor that orchestrates multi-agent workflows by loading state and instructions from a local directory. Its primary security consideration is indirect prompt injection, as it dynamically loads and processes natural language instructions for subagents from files that could be tampered with or reside in untrusted locations.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

  • Runlayerpass

    3/4 files flagged

What does this agent skill do?

Team Executor

Lightweight session execution skill: load session -> reconcile state -> spawn team-worker agents -> execute -> deliver. No analysis, no role generation -- only executes existing team-coordinate sessions.

Architecture

+---------------------------------------------------+
|  Skill(skill="team-executor")                      |
|  args="--session=<path>" [REQUIRED]                |
+-------------------+-------------------------------+
                    | Session Validation
         +---- --session valid? ----+
         | NO                       | YES
         v                          v
    Error immediately          Orchestration Mode
    (no session)               -> executor
                                    |
                    +-------+-------+-------+
                    v       v       v       v
                 [team-worker agents loaded from session role-specs]

Session Validation (BEFORE routing)

CRITICAL: Session validation MUST occur before any execution.

Parse Arguments

Extract from $ARGUMENTS:

  • --session=<path>: Path to team-coordinate session folder (REQUIRED)

Validation Steps

  1. Check --session provided:

    • If missing -> ERROR: "Session required. Usage: --session=<path-to-TC-folder>"
  2. Validate session structure (see specs/session-schema.md):

    • Directory exists at path
    • team-session.json exists and valid JSON
    • task-analysis.json exists and valid JSON
    • role-specs/ directory has at least one .md file
    • Each role in team-session.json#roles has corresponding .md file in role-specs/
  3. Validation failure:

    • Report specific missing component
    • Suggest re-running team-coordinate or checking path

Role Router

This skill is executor-only. Workers do NOT invoke this skill -- they are spawned as team-worker agents directly.

Dispatch Logic

ScenarioAction
No --sessionERROR immediately
--session invalidERROR with specific reason
Valid sessionOrchestration Mode -> executor

Orchestration Mode

Invocation: Skill(skill="team-executor", args="--session=<session-folder>")

Lifecycle:

Validate session
  -> executor Phase 0: Reconcile state (reset interrupted, detect orphans)
  -> executor Phase 1: Spawn first batch team-worker agents (background) -> STOP
  -> Worker executes -> SendMessage callback -> executor advances next step
  -> Loop until pipeline complete -> Phase 2 report + completion action

User Commands (wake paused executor):

CommandAction
check / statusOutput execution status graph, no advancement
resume / continueCheck worker states, advance next step

Role Registry

RoleFileType
executorroles/executor/role.mdbuilt-in orchestrator
(dynamic)<session>/role-specs/<role-name>.mdloaded from session

Executor Spawn Template

v2 Worker Spawn (all roles)

When executor spawns workers, use team-worker agent with role-spec path:

Agent({
  subagent_type: "team-worker",
  description: "Spawn <role> worker",
  team_name: <team-name>,
  name: "<role>",
  run_in_background: true,
  prompt: `## Role Assignment
role: <role>
role_spec: <session-folder>/role-specs/<role>.md
session: <session-folder>
session_id: <session-id>
team_name: <team-name>
requirement: <task-description>
inner_loop: <true|false>

## Progress Milestones
session_id: <session-id>
Report progress via team_msg at natural phase boundaries (context loaded -> core work done -> verification).
Report blockers immediately via team_msg type="blocker".
Report completion via team_msg type="task_complete" after final SendMessage.

Read role_spec file to load Phase 2-4 domain instructions.`
})

Completion Action

When pipeline completes (all tasks done), executor presents an interactive choice:

AskUserQuestion({
  questions: [{
    question: "Team pipeline complete. What would you like to do?",
    header: "Completion",
    multiSelect: false,
    options: [
      { label: "Archive & Clean (Recommended)", description: "Archive session, clean up team" },
      { label: "Keep Active", description: "Keep session for follow-up work" },
      { label: "Export Results", description: "Export deliverables to target directory, then clean" }
    ]
  }]
})

Action Handlers

ChoiceSteps
Archive & CleanUpdate session status="completed" -> TeamDelete -> output final summary with artifact paths
Keep ActiveUpdate session status="paused" -> output: "Resume with: Skill(skill='team-executor', args='--session=<path>')"
Export ResultsAskUserQuestion(target path) -> copy artifacts to target -> Archive & Clean

Integration with team-coordinate

ScenarioSkill
New task, no sessionteam-coordinate
Existing session, resume executionteam-executor
Session needs new rolesteam-coordinate (with resume)
Pure execution, no analysisteam-executor

Error Handling

ScenarioResolution
No --session providedERROR immediately with usage message
Session directory not foundERROR with path, suggest checking path
team-session.json missingERROR, session incomplete, suggest re-run team-coordinate
task-analysis.json missingERROR, session incomplete, suggest re-run team-coordinate
No role-specs in sessionERROR, session incomplete, suggest re-run team-coordinate
Role-spec file not foundERROR with expected path
capability_gap reportedWarn only, cannot generate new role-specs
Fast-advance spawns wrong taskExecutor reconciles on next callback
Completion action failsDefault to Keep Active, log warning

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/catlog22/claude-code-workflow/team-executor">View team-executor on skillZs</a>