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

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.