Quickstart
From zero to a production-ready agent team in under a minute.
1. Install atl
# macOS / Linux
brew install agentteamland/tap/atl
# Windows
scoop bucket add agentteamland https://github.com/agentteamland/scoop-bucket
scoop install atlFull matrix: Install guide.
2. Create a project directory
mkdir my-new-app && cd my-new-appatl expects to operate inside a project — it will create a .claude/ directory here for the team's agents, skills, and rules.
3. Discover a team
atl search dotnetYou'll see matching entries from the public registry, including software-project-team.
4. Install the team
atl install software-project-teamIn a few seconds:
- The team is cloned into the shared cache (first time only)
- 13 agents, 2 skills (
create-new-project,verify-system), and 1 rule are symlinked into.claude/ team.jsonis recorded in.claude/.team-installs.json
You now have a full .NET + Flutter + React + Docker agent team wired into your project.
5. Inspect what you installed
atl listShows the teams installed in this project, their effective agent counts, and the inheritance chain.
6. Use it in Claude Code
Open Claude Code in this directory. The team's skills are available as slash commands:
/create-new-project MyApp— scaffolds a full stack (Phase 1–5: gather → scaffold → build → verify → commit)/verify-system— runs an end-to-end health check on containers, ports, apps, and pipelines
And every agent (api-agent, socket-agent, worker-agent, flutter-agent, react-agent, database-agent, redis-agent, rmq-agent, infra-agent, code-reviewer-agent, project-reviewer-agent, design-system-agent, ux-agent) is available for Claude to delegate to.
7. Keep up to date
When the team author ships improvements:
atl updateAll installed teams pull, dependencies resolve, symlinks refresh. Nothing in your project code changes.
What just happened?
You installed a curated, version-pinned, dependency-aware set of agents into a project with a single command. Every other project that installs the same team gets the same configuration — and the same updates when the author ships them.
Next
- Concepts — the mental model behind teams, agents, skills, and rules.
- CLI reference — every command in detail.
- Write your own team — publish a team to the registry.