---
name: teamai
description: >-
  Make every team AI native — TeamAI syncs a team's AI skills, rules, docs and env across AI coding tools. Use when the task operates on team-shared AI configuration or team knowledge: setting up a team repo, joining one, managing members, syncing with pull or push, or checking team status. Also use to build or query a codebase knowledge base for a large multi-repo project (architecture analysis, architecture reverse-engineering, code-to-knowledge, team-wiki-codebase, architecture wiki), and to share what a session taught you back to the team (share session learnings, contribute a learning, share what I learned with my team), including after a friction reminder, and to run a team workflow. Triggers include "set up teamai", "join the team repo", "sync team skills", "team wiki", "share what I learned", "run a team workflow", "which workflows does the team have", "start <workflow>", and running /teamai. Talking about a team needs no skill; operating on what the team shares does.
allowed-tools: Bash(teamai skill:*), Bash(npx teamai-cli skill:*), Bash(teamai list workflows:*), Bash(npx teamai-cli list workflows:*), Bash(teamai workflow start --describe:*), Bash(teamai workflow next:*), Bash(teamai workflow report:*), Bash(teamai workflow respond:*), Bash(npx teamai-cli workflow start --describe:*), Bash(npx teamai-cli workflow next:*), Bash(npx teamai-cli workflow report:*), Bash(npx teamai-cli workflow respond:*)
title: teamai
canonical_url: https://skilld.dev/gh/tencent/teamai-cli/teamai
last_updated: 2026-11-15T17:04:25.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install tencent/teamai-cli/teamai`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/teamai`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/tencent/teamai-cli/teamai) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/teamai`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/teamai --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/teamai --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# teamai

Make every team AI native — one shared foundation for the skills, rules, docs and env a team works with.

Install: `npm i -g teamai-cli@latest` (Node.js >= 20). If `teamai skill get` is not recognised, the installed CLI predates it; upgrade the same way.

## Start here

This file is a discovery stub, not the usage guide. Load the workflow from the CLI before running anything, so the instructions match the installed version:

```bash
teamai skill get core             # daily work: routing, pull, push, status, doctor
teamai skill get core --full      # adds the full command reference and troubleshooting
```

The CLI serves skill content that always matches the installed version, so instructions never go stale. The content in this stub cannot change between releases, which is why it just points at `skill get`.

## Specialized workflows

```bash
teamai skill get setup            # day 0: create a team repo (admin) or join one (member), manage, uninstall
teamai skill get wiki             # large multi-repo codebase: architecture reverse-engineering and knowledge base
teamai skill get share            # turn what this session taught you into a team learning (needs recall on)
teamai skill get workflow         # drive a requested team workflow from this coding session
teamai skill get workflow-local   # run a workflow unattended: CI, cloud agents, a handed-off run
```

Publishing a skill, rule or doc the user already has is in `core`; it needs no recall.

A friction reminder at the end of a turn means `teamai skill get share`.

`teamai skill list` shows everything the installed version serves. `teamai skill path <name>` prints the directory holding a skill's scripts and templates.
