Fetching from the wire…
Public story · 2026-09-08 · high
The tool pushes shared skills, MCP servers and knowledge from one git repo into six different coding assistants at once.
Why now: The project crossed 2,113 stars after a single day added 1,215 of them, per its GitHub page as of September 8.
teamai-cli has 2,113 stars and 142 forks. It syncs a team's skills, rules, MCP servers and knowledge from one shared git repo into Claude Code, Codex, CodeBuddy, WorkBuddy, OpenCode and Cursor, at either project or user scope.
Most teams handle this the opposite way. Each developer keeps a personal skill directory and installs whatever looks useful that week, with no review step before it reaches their editor. teamai-cli treats the shared repo as the thing you distribute, with write access granted to teammates instead of to a random GitHub star count.
That's a real fix for a real problem. Skill files pulled from wherever tend to be inconsistent quality, and a repo with review on it catches the bad ones before they reach six different tools at once. One person fixes a broken MCP server config, everyone's setup updates.
What the project page doesn't say is how conflicts get resolved when two team members edit the same skill, or what happens when Claude Code's skill format diverges from Cursor's. Six target tools means six surfaces to keep compatible, and that maintenance cost doesn't show up in a star count.
1,215 stars in one day is 57% of the repo's total. That says a lot of people hit the same problem at once and not much about whether the tool holds up under daily use. I'd want to see it running on a real team's repo for a month before calling the pattern solved.
Each link below shares sources, entities, or timing with this story.
affaan-m/ECC (36.3k forks, MIT) bundles 67 agents, 284 skills, 94 legacy command shims, and "instincts", patterns learned from prior sessions with confidence scores that auto-recall when relevant, plus a .ecc/memory/ markdown vault that's explicitly cross-harness, so context s...
EchoVault solves the "agent amnesia" problem — coding agents forgetting everything between sessions. It runs as an MCP server giving agents three tools: memory_context (load prior decisions), memory_search (find specific memories), and memory_save (persist learnings). Storage...
ismcpgoodyet.com tracks Codex, Cursor, Claude Code, Grok and OpenCode. Tasks, the feature for long-running work, is absent across all five. The stateless spec revision dated 2026-07-28 is only partially supported by Codex and Claude Code. Cursor has no tools/list pagination. s...
v0.10.0 (~84.8k stars, Apache-2.0) ships no agent of its own and drives whichever CLI you already have, Claude Code, Codex, Cursor, Copilot, OpenClaw, Gemini, Kimi, Qwen, Cline, plus BYOK OpenAI-compatible endpoints, via od mcp install <agent>. It produces single-page HTML pro...
akitaonrails/ai-memory (1,229 stars, +184 this week, MIT, Rust, 900 commits) inverts the usual design: hooks emit sanitized lifecycle observations during a session, and the server compiles them into coherent wiki pages at session end or PreCompact, "compiled from observations...
Everyone writing SKILL.md files has absorbed the same folklore. Keep the top file thin. Push detail into reference files. Let the agent walk the tree as needed. More layers, more context efficiency. A controlled study submitted July 20 tested that across InfiniteBench, three a...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.