Index of every page on this site: llms.txt
All skills
tencent avatar

/setup

@df433c6
by tencenttencent/teamai-cli5.9k stars
531
Run it yourself

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.

  • 6 files
  • 74.9 KB
  • Updated last month
  • GitHub
Use this Skill: https://skilld.dev/gh/tencent/teamai-cli/setup

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈50 tokens for metadata: the name and description. ≈1.2k when used: this file. ≈18k more on demand in 5 files.

Description uses 2.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈202 characters, or 2.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.

Rules for these flows

  1. Always use a full URL for the team repo (e.g. https://github.com/your-org/your-repo). 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, which detected tools were skipped and why (e.g. CodeBuddy design), and any installed hooks that still need trust (e.g. Codex with automatic trust disabled or unavailable). Verify the real per-tool result with teamai doctor and teamai hooks list.
  3. teamai init does not pull. It saves the config and installs hooks. It does not copy team skills, rules or MCP. In workspace scope it creates a tool directory only for a tool named with --agent, or picked when a person runs it in a terminal. Those resources arrive on that tool's next session start, or when you run teamai pull. Run from an agent shell (no terminal), a workspace-scope init without --agent creates no tool directory: the directory appears when the user opens that tool in the project, and that session start pulls.
  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.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at df433c6. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 days ago.

Activeupdated last month

README badge

README badge for tencent/teamai-cli/setup