agent-team-run-close

Close agent-team workflow runs after all tasks reach terminal states.

2|Updated May 10, 2026
One-click install
npx skills add https://github.com/tae2089/agent-team --skill agent-team-run-close
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-team-run-close
Source: https://github.com/tae2089/agent-team/tree/main/skills/agent-team-run-close
Command: npx skills add https://github.com/tae2089/agent-team --skill agent-team-run-close

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Close a workflow run after all tasks reach a terminal state (done, failed, or cancelled).

Core Features & Use Cases

  • Ensure a run is closed only when every associated task has reached a terminal state (done, failed, or cancelled).
  • Provide clear error messages for invalid states, missing runs, or non-open runs.
  • Integrate with agent-team lifecycle to record closure in events and persist final status.

Quick Start

Close a workflow run by specifying the RUN_ID once all tasks reach a terminal state.

Frequently Asked Questions about agent-team-run-close

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

FAQPage Schema
How do I close a workflow run only after all tasks reach a terminal state?

The run_not_ready error occurs during workflow run closure when one or more associated tasks have not yet reached a terminal state. You must wait until all tasks are done, failed, or cancelled before attempting to close the run.

What is the invalid_run_state error when managing agent-team workflows?

The invalid_run_state error is returned when attempting to close a workflow run that is not currently open. The closure logic requires the target run to exist in an open state before it can process the final termination and persist the status.

Can I close an agent-team run if some tasks are still active?

You cannot close an agent-team run if tasks are still active. The system validates all required inputs and checks that every task has terminated (done, failed, or cancelled) to prevent premature closure and ensure workflow integrity.

How does the run closure process persist the final workflow status?

The run closure process integrates with the agent-team lifecycle to record the closure in events and persist the final status. This guarantees the workflow state is accurately saved after all tasks reach their terminal states.

What happens if I specify a RUN_ID that does not exist?

If you specify a non-existent RUN_ID, the system returns a not_found error code. This precise error validation prevents accidental closure of incorrect workflows and ensures only existing runs are targeted.