claude-team

Validate team configs and resume Claude Code orchestrator sessions.

3|1|Updated Dec 3, 2025
One-click install
npx skills add https://github.com/nsheaps/ai-mktpl --skill claude-team
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-team
Source: https://github.com/nsheaps/ai-mktpl/tree/main/plugins/claude-team/skills/claude-team
Command: npx skills add https://github.com/nsheaps/ai-mktpl --skill claude-team

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents silent failures, misrouted messages, and session-reconnection pitfalls that break multi-agent Claude Code workflows by documenting validation steps, reconnection procedures, and coordination best practices.

Core Features & Use Cases

  • Silent-failure detection: How to verify teammates and avoid SendMessage to nonexistent recipients and accidental empty teams.
  • Session reconnection: Exact steps to resume orchestrator sessions by reading team config, matching leadSessionId, team and agent names, and validating TaskList.
  • Coordination & cost control: Guidelines to avoid expensive broadcasts, reduce context bloat, and enforce file placement conventions for shared artifacts.
  • Use Case: Reconnect a crashed orchestrator, recover task lists, and re-establish peer messaging without losing history.

Quick Start

Reconnect a crashed Claude Code team by reading ~/.claude/teams/{team-name}/config.json, copy the exact team and lead names, resume the leadSessionId with the --resume and --team-name flags, and verify TaskList shows existing tasks.

Frequently Asked Questions about claude-team

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

FAQPage Schema
How do I reconnect a crashed Claude Code orchestrator session?

To reconnect a crashed Claude Code orchestrator, read the team config at ~/.claude/teams/{team-name}/config.json, match the exact leadSessionId and team names, then resume using the --resume and --team-name flags to recover task lists and messaging history.

Why do silent failures happen in multi-agent Claude Code teams?

Silent failures in multi-agent Claude Code teams happen when messages route to nonexistent recipients or empty teams, causing coordination to break without errors. Verifying teammates exist before sending messages prevents these misrouted communications.

What's the best way to reduce context bloat in Claude Code agent teams?

To reduce context bloat in Claude Code agent teams, avoid expensive broadcasts, enforce shared filesystem placement conventions for artifacts, and use targeted SendMessage operations instead of broad team-wide notifications.

How do I verify TaskList shows existing tasks after a session recovery?

After resuming the leadSessionId with the --resume and --team-name flags, verify TaskList shows existing tasks by validating the recovered orchestrator session against the team config and confirming task entries match the pre-crash state.

Does Claude Code team orchestration require matching exact team and agent names?

Yes, Claude Code team orchestration requires matching exact team and agent names from the config file for resume operations. Mismatched names prevent valid session reconnection and leave shared artifacts and messaging unrecovered.

When should I not use broadcast messaging in multi-agent Claude Code workflows?

You should not use broadcast messaging in multi-agent Claude Code workflows when targeted SendMessage delivery suffices, as broadcasts increase context bloat and costs without improving coordination among verified teammates.