apm vs teamai-cli
Microsoft's dependency manager for agent context — declare skills, prompts, plugins and MCP servers in apm.yml; one install reproduces the setup across 8 clients with lockfile pinning and org policy. — versus — Tencent's team-level agent config manager: skills, rules, agents, hooks, MCP and env live in a shared git repo and sync into Claude Code, Codex, Cursor, CodeBuddy, OpenCode and more on every session.
Both declare and install skills, prompts, MCP servers and hooks into multiple coding agents from a versioned manifest; apm is a per-project dependency manager, teamai is a team-wide sync with push/pull against a shared repo.
| apm | teamai-cli | |
|---|---|---|
| Stars | 3.8k | 3.6k |
| Forks | 356 | 230 |
| Language | Python | TypeScript |
| License | MIT | NOASSERTION |
| Last activity | yesterday | yesterday |
| Topics | coding, skills | skills, coding |
| Curated connections | 5 | 5 |
apm — the curator's take
The team/enterprise answer: apm.yml ships with the repo, so `git clone && apm install` gives every developer identical agent context — lockfile, transitive dependencies, drift detection, and an apm-policy.yml a security team can enforce with tighten-only inheritance. It's the only skill manager with a real governance story (SBOM export, MCP trust gates). NOT for quick personal use — manifest ceremony is overkill for 'just install this skill', where skillkit or asm is faster — and it targets 8 major clients, not the 40+ long tail. Young project; treat the roadmap as direction, not promise.
teamai-cli — the curator's take
The right tool when the unit is a team, not a developer: an admin curates one 'shared-experience' repo, `teamai init <repo>` installs it per project or per user, and every agent session auto-pulls updates. Coverage is broad (Claude Code, Codex, Cursor, CodeBuddy, WorkBuddy, OpenCode, OpenClaw, Hermes…) and the beta Context/Improvement layers (learnings, codebase graph, sessions, dashboard) push toward a company-wide agent memory. Solo developers should look at apm or skillkit instead — the git-repo-plus-write-access model is overhead without teammates. Tencent-first ecosystem (CodeBuddy, CNB, TGit) — check the matrix for your harness before committing.