team

Manage AgentTeamLand team installation, updates, removal, and listing in .claude directories.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/agentteamland/team-manager --skill team-agentteamland
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team
Source: https://github.com/agentteamland/team-manager/tree/main/skill
Command: npx skills add https://github.com/agentteamland/team-manager --skill team-agentteamland

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams of agents, skills, and rules in AgentTeamLand are hard to install, keep consistent, and version per-project; this Skill centralizes installing, updating, removing, and listing teams so each project has an explicit, reproducible set of agents and tools without polluting global state.

Core Features & Use Cases

  • Registry and URL installs: resolve short names via the AgentTeamLand registry or accept direct git URLs and owner/name shorthand.
  • Inheritance with overrides and excludes: recursively apply extends chains, allow children to override parent items by name, and drop unwanted inherited items via excludes.
  • Robust safety and validation: circular dependency detection with explicit chain errors, schema validation of team.json, version constraint checking, and atomic top-of-stack symlink materialization into the project's .claude directory.
  • Use case: set up a project-specific developer environment by installing a software-project-team that inherits a core baseline while overriding one agent and excluding an unwanted parent agent.

Quick Start

Run /team install <team-name> to install a team into the current project's .claude directory.

Frequently Asked Questions about team

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

FAQPage Schema
How do I install agent teams into a project's .claude directory?

To install agent teams into a project's .claude directory, run the /team install command with a team name, which resolves registry names or git URLs and atomically materializes symlinks. This ensures a reproducible project-specific environment without polluting global state.

How does inheritance work when managing project-level agent teams?

Inheritance for project-level agent teams works by recursively applying extends chains, allowing children to override parent items by name, and dropping unwanted inherited items via excludes. Circular dependencies are detected using a visited map to prevent infinite loops.

Can I install agent teams directly from a git URL instead of a registry?

Yes, you can install agent teams directly from git URLs or owner/name shorthand instead of resolving short names via the registry. The system enforces registry fetch with timeout and schema validation to ensure robust safety during installation.

What is the best way to keep agent teams consistent and versioned per project?

The best way to keep agent teams consistent and versioned per project is using a centralized management skill that handles installation, updates, and removal. It honors version constraints, installs transitive dependencies to a cache, and creates explicit per-project symlinks.

How are circular dependencies detected when resolving team extends chains?

Circular dependencies in team extends chains are detected using an explicit visited map that tracks the resolution path. If a cycle is found, the system throws a chain error to prevent infinite recursion and ensure robust safety during installation.

Does installing project-level agent teams require global state modifications?

No, installing project-level agent teams does not require global state modifications. The system atomically creates or removes symlinks exclusively within the project's .claude directory, ensuring each project maintains an explicit and isolated set of agents and tools.