setup git:20261003.e1dd70dA

Immutable. This exact content never changes and is served at /api/v1/blob/ddd27b309c0e7a04.

---
name: setup
description: >-
  TeamAI day 0 and repo lifecycle: create a team repo as admin, join an existing team as a member,
  manage members, roles, MCP and env, and uninstall. Loaded on demand by the teamai discovery stub.
---

# teamai — setup and lifecycle

You run the commands; the user only makes choices when you ask. **They may not
know Git** — never explain branches, commits or clones.

## Before anything

```bash
node --version      # must be >= 20
teamai --version    # install once with: npm install -g teamai-cli
```

Then pick the flow. A user **setting up a new team** becomes its admin and creates
the repo; a user **joining an existing team** needs a repo URL from their admin. A
would-be member without a URL is still the **join** flow — `join-member.md` tells
them how to ask for it. Do not send them to the create-repo flow because the URL
is missing.

| The user wants to…                                                          | Load this                                   |
|-----------------------------------------------------------------------------|---------------------------------------------|
| Set up TeamAI for a team from scratch (create the repo)                      | `{SKILL_DIR}/references/setup-admin.md`     |
| Join their team, with or without a repo URL                                  | `{SKILL_DIR}/references/join-member.md`     |
| Publish or update skills, rules, MCP, env; invite members; manage roles      | `{SKILL_DIR}/references/manage-admin.md`    |
| Remove TeamAI from this machine                                              | `{SKILL_DIR}/references/uninstall.md`       |
| Publish one skill or contribute a doc                                        | `"$(teamai skill path core)/references/contribute-member.md"` |
| Anything that breaks along the way                                           | `"$(teamai skill path core)/references/troubleshooting.md"` |

Supported Git providers are Tencent TGit, GitHub, GitLab and CNB;
`{SKILL_DIR}/references/setup-admin.md` carries the detection probe, the sign-in
and create-repo URLs, and the per-provider caveats, and points at
`{SKILL_DIR}/references/provider-tgit.md` for everything TGit-specific.

## Rules for these flows

1. **Always use a full URL** for the team repo (e.g.
   `https://github.com/yourorg/yourrepo`). Never the `owner/repo` short form.
2. **Don't limit which AI tools get set up — cover all of them by default.**
   Unless the user names specific tools, do **not** pass `--agent` to restrict the
   install. Let `teamai init` set up every AI tool already installed (omitting
   `--agent` gives an interactive picker; select all detected tools). **After init,
   report which agents were set up** — in the user's language, which tools now
   auto-start TeamAI, and which detected tools were skipped and why (e.g. Codex
   trust-gate, CodeBuddy design). Verify the real per-tool result with
   `teamai doctor` and `teamai hooks list`.
3. **`teamai init` ends with a pull.** In user scope, and in project scope for each
   tool named with `--agent` (or picked in init's tool picker when a person runs it
   in a terminal), the team's skills, rules and MCP servers are in place when init
   exits; there is no need to run `teamai pull` after it. Run from an agent shell
   (no terminal), a project-scope init without `--agent` creates no tool directory: a tool's directory appears and
   fills when the user opens that tool in the project. Init also injects a
   session-start hook that keeps resources synced from then on.
4. **Finish with `teamai doctor`.** Every setup or onboarding flow ends by running
   it and resolving what it reports before you call the job done.

Every public command and every flag, including the flags `--help` hides, is listed in
`teamai skill get core --full` under `references/commands.md`. Do not guess a flag:
there is no member-invite flag, for instance — inviting happens on the Git
platform's website, as `manage-admin.md` describes.

## References

In the files below, `{SKILL_DIR}` is the directory `teamai skill path setup` prints; a reference file you open on its own writes that directory as `SKILL_DIR` in braces.

| File | When to load it |
|---|---|
| `{SKILL_DIR}/references/setup-admin.md` | Creating a team repo: provider detection, auth, repo creation, first push. |
| `{SKILL_DIR}/references/join-member.md` | Joining an existing team from a repo URL. |
| `{SKILL_DIR}/references/manage-admin.md` | Day-to-day admin: publishing resources, roles, projects, MCP, env, members. |
| `{SKILL_DIR}/references/uninstall.md` | Removing TeamAI from a machine or from one agent. |
| `{SKILL_DIR}/references/provider-tgit.md` | Tencent TGit: reachability probe, `gf` install and login, repo creation on init. |

`teamai skill get setup --full` prints this skill with all five appended.