How I manage skills and MCP servers across AI coding agents

Keeping AI Coding Agents in Sync Working with AI coding agents recently has meant switching between them more often than I expected. Sometimes a model hits token limits. Sometimes rate limits kick in. Sometimes a different model simply performs better for a task. So during the same project I often move between tools like Codex, Cursor, Gemini, Claude Code, or Copilot . Most coding agents now support roughly the similar concepts: skills MCP servers local tools and config filesystem discovery But they do not share state. That leads to some practical problems. if I install a new MCP in one agent, I have to install it again in the other agents. If I update a skill, I have to make sure every agent is using the updated version. If I try a new agent, the entire setup has to be recreated again. Over time the setups drift apart. The Idea I wanted one workspace to define the environment, with agents acting as consumers of that definition. That became skills-sync . skills-sync is a CLI for keepin