agent-team-shared

Coordinate daemonless state management for agent-team CLI workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Shared runtime procedures enable daemonless state management, standardized flags, JSON input/output, and consistent shell usage for the agent-team CLI.

Core Features & Use Cases

  • Shared runtime for daemonless coordination between orchestrators and workers.
  • Global flags and JSON I/O standardization for predictable workflows.
  • State directory rules and error handling to maintain reliable project state and recoverability.

Quick Start

Initialize the shared runtime in your project by running agent-team init and load this skill before issuing command-specific agent-team operations.

Frequently Asked Questions about agent-team-shared

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

FAQPage Schema
How do I coordinate multiple orchestrators and workers without a daemon?

Daemonless coordination is achieved by applying shared runtime procedures for state management, enabling orchestrators and workers to sync through CLI commands and JSON I/O without background processes.

How do I initialize daemonless state management for an agent-team workflow?

Initialize daemonless state management by running the agent-team init command to set up the shared runtime and state directories before issuing any task, run, or inbox operations.

What is the best way to standardize CLI flags and JSON input/output for agent workflows?

Standardizing CLI flags and JSON input/output is handled by a shared runtime that enforces strict flag parsing and predictable JSON formatting across all agent-team commands.

Does daemonless agent-team orchestration support strict flag parsing and error handling?

Yes, daemonless orchestration supports strict flag parsing and robust error handling through shared runtime procedures that validate inputs and maintain reliable project state.

Why do I need state directory rules for daemonless workflow orchestration?

State directory rules are required to maintain reliable project state and recoverability, ensuring orchestrators and workers can safely read and write JSON data without daemon locks.

Can I use agent-team commands like sync and inbox for daemonless state management?

Yes, you can use agent-team commands like sync checks and inbox for daemonless state management to coordinate task execution and message passing between multiple orchestrators and workers.