Worth knowing before anyone installs Tencent’s teamai-cli on the strength of its front page: the automatic half runs off a hook, and 3 of the 11 agents it lists have none. The rest of it I like.

Tencent has published teamai-cli, which treats that as distribution rather than discipline. One git repo holds skills/, rules/, hooks/hooks.yaml, mcp/mcp.yaml, agents/, docs/ and a culture.md that gets injected into each agent’s CLAUDE.md or AGENTS.md. Install is npm install -g teamai-cli, then teamai init <repo-url> against a repo the team can write to.

The flow is the point: teamai push opens a branch and a merge request, a reviewer merges, and the next session’s SessionStart hook runs teamai pull so the change lands in everyone’s local tools. teamai roles and teamai tags mean nobody is forced to sync skills they do not use.

I counted what it promises per agent before getting interested, since that is what decides whether it reaches your machine. Skills and docs are filled on all 11 agents in the table, hooks and MCP on 8. The automatic pull is itself a hook, so on OpenClaw, Hermes and DeepSeek Harness my read is that you are pulling by hand.

Worth knowing: the shared env/ resource explicitly is not for secrets, and the recall and dashboard halves are both marked beta. Repo: https://github.com/Tencent/teamai-cli

Has a rule ever landed in your shared setup that you would have blocked if you had seen the diff first?