using-legacy-claude-team

Manage legacy Claude Team creation, registry recovery, and teardown via TeamCreate.

73|7|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/spacedock-dev/spacedock --skill using-legacy-claude-team
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-legacy-claude-team
Source: https://github.com/spacedock-dev/spacedock/tree/main/skills/using-legacy-claude-team
Command: npx skills add https://github.com/spacedock-dev/spacedock --skill using-legacy-claude-team

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a back-channel for legacy Claude Team interactions via TeamCreate, enabling team creation, registry recovery, and teardown procedures.

Core Features & Use Cases

  • Legacy Team Management: Supports the creation and deletion of legacy Claude Teams.
  • Registry Desync Recovery: Offers a recovery process for team registry desynchronization.
  • Terminal Teardown: Provides a bounded procedure for team teardown.
  • Use Case: When using a runtime that still exposes TeamCreate, this Skill facilitates team-based communication and coordination between agents.

Quick Start

Load the using-legacy-claude-team skill and run the necessary commands to create a team, manage it, and eventually teardown the team.

Frequently Asked Questions about using-legacy-claude-team

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

FAQPage Schema
How do I create and delete legacy Claude Team back-channels for agent communication?

Legacy Claude Team back-channels are created and deleted using TeamCreate and TeamDelete commands, enabling structured agent communication and coordination within compatible Claude Code runtimes.

What is registry desync recovery in legacy Claude Team management?

Registry desync recovery is a built-in procedure that resolves team registry synchronization failures, restoring consistent state across agent communication channels when legacy Claude Team tracking becomes misaligned.

Does legacy Claude Team management require a specific Claude Code runtime?

Yes, managing legacy Claude Teams requires a Claude Code runtime that explicitly exposes the TeamCreate interface, as the Skill depends on that runtime capability for team initialization and teardown.

How do I perform a terminal teardown of a legacy Claude Team?

Terminal teardown is executed through a bounded procedure using TeamDelete, ensuring all active legacy Claude Team back-channels are safely closed and registry entries are cleanly removed.

Why does my Claude Team registry become desynchronized during agent communication?

Registry desynchronization occurs when team state tracking fails to update correctly across agent interactions, requiring the Skill's dedicated recovery procedure to restore proper registry alignment.

Can I use SendMessage for inter-agent communication within a legacy Claude Team?

Yes, SendMessage is supported for inter-agent communication, allowing messages to be routed through the established legacy Claude Team back-channel after team creation via TeamCreate.