Overview
TeamAI CLI is an open-source command-line tool from Tencent that treats a git repository as the source of truth for how a team's AI coding agents behave. An admin publishes skills, rules, docs, environment variables, hooks, agents and MCP servers into that repo; every member runs `teamai init` against its URL once, and from then on each AI session pulls whatever the admins have published, with no manual sync step.
The tool is organised in three layers. Team Execution is the part that is fully shipping: `init`, `pull` and `push` for the shared harness of skills, rules, agents, hooks, MCP and env. Team Context (beta) adds recall, shared learnings, a codebase graph and a team wiki so an agent starts a session knowing something about the codebase. Team Improvement (beta) collects session friction, usage stats and a digest so real sessions turn into new shared skills and rules.
Support is deliberately multi-agent. The README's coverage table gives Claude Code, Codex, Cursor, CodeBuddy and Qoder a tick in every column, with narrower support for WorkBuddy, OpenCode, OpenClaw, Hermes, DeepSeek Harness and ZCode. Resources install at project scope by default or at user scope with `--scope user`. TeamAI CLI is published on npm as `teamai-cli` under the MIT license and needs Node.js 20 or newer plus git.
What it does
- One shared git repo holds the team's skills, rules, docs, env, hooks, agents and MCP servers; members pull the latest automatically on every AI session
- Multi-agent by design: Claude Code, Codex, Cursor, CodeBuddy, WorkBuddy, OpenCode, OpenClaw, Hermes, DeepSeek Harness, Qoder and ZCode
- `teamai push` sends a local skill or rule back to the team repo through a merge-request style review flow
- Project scope by default, or `--scope user` to install shared resources under the home directory for every project on the machine
- Team Context (beta): recall, shared learnings, a codebase graph and a team wiki so agents do not start each session from zero
- Team Improvement (beta): session records, usage stats and a digest dashboard built from friction signals in real sessions
- Works with GitHub, GitLab (hosted or self-hosted), GitCode, CNB, TGit and private git services
Getting started
TeamAI CLI installs from npm and needs Node.js 20 or newer plus git. One admin creates the shared team repo; everyone else only runs `teamai init` against its URL.
Install the CLI
Install globally from npm, then confirm the binary is on your path.
npm install -g teamai-cli
teamai --versionAdmin: create and initialise the team repo
Create an empty repository on your git host, grant write access to the team, then point `teamai init` at it. The README suggests naming it TeamAi-<team-name>.
teamai init https://github.com/yourorg/yourrepoMember: join at project or user scope
Project scope is the default and installs the shared resources under the current project. User scope installs them under your home directory so they apply everywhere.
cd /path/to/my-project
teamai init https://github.com/yourorg/yourrepo
# or, for every project on this machine
teamai init https://github.com/yourorg/yourrepo --scope userUse a self-hosted GitLab instance
Set the instance URL and a personal access token with `api` scope before running init.
export GITLAB_URL=https://git.example.com
export GITLAB_TOKEN=glpat-xxxxxxxxxxxxxxxx
teamai init https://git.example.com/yourgroup/yourrepoInstall team packages
Team-wide npm packages and Claude Code plugins are installed explicitly with the `packages` command, renamed from `install` in v0.24.0-beta.2.
teamai packagesCommands and code are distilled from the project's own documentation — always check the official repo for the latest.
When to use it
- Stop copy-pasting the same agent rules into a dozen private config directories and let a reviewed git workflow distribute them instead
- Give a new joiner a working agent configuration on day one by having them run a single `teamai init`
- Keep a shared setup working when team members use different agents, so someone moving from Cursor to Claude Code keeps the same skills and rules
- Publish a skill you wrote locally back to the whole team through `teamai push` and a merge request
How TeamAI CLI compares
TeamAI CLI alongside other open-source agent skills & plugins tools AI/TLDR tracks, ranked by GitHub stars.
| Tool | Stars | What it does |
|---|---|---|
| Superpowers | ★ 284k | A composable skills plugin that installs a spec-first, TDD, subagent-driven development methodology into Claude Code, Codex, Cursor, Gemini CLI and other coding harnesses. |
| Skills for Real Engineers | ★ 258k | Matt Pocock's everyday agent skills for coding agents, covering alignment grilling, planning, code review and research — small, composable and meant to be edited. |
| ECC | ★ 255k | An installable plugin that adds 68 agents, 286 skills, hooks, rules, memory and an agent-config security scanner to Claude Code, Codex and other coding harnesses. |
| Addy’s Agent Skills | ★ 93.1k | A pack of production engineering skills for AI coding agents, with nine lifecycle slash commands — /spec, /plan, /build, /test, /review, /ship — installable into 70+ agents. |
| Humanizer | ★ 45.8k | An agent skill that rewrites AI-sounding prose against a list of 25 named writing patterns, grouped into five sections and applied without changing the claims in the text. |
| Claude for Financial Services | ★ 34.8k | Anthropic reference agents, skills and MCP connectors for investment banking, equity research, private equity and wealth management, as Cowork plugins or Managed Agents. |
| Anthropic-Cybersecurity-Skills | ★ 32.5k | A community-built library of 800+ agentskills.io-format cybersecurity skills for AI agents, each mapped to MITRE ATT&CK, NIST CSF 2.0, ATLAS, D3FEND, NIST AI RMF and MITRE F3. |
| TeamAI CLI | — | Tencent's CLI that stores a team's agent skills, rules, docs, hooks, env and MCP servers in one shared git repo and syncs them into every member's coding agent |