We’ve been hitting the same operational pattern at every engineering team using AI tooling: one person builds up a vault of skills, MCP configs, slash commands, and rule files that 10x their output, and the rest of the team can’t replicate the setup. Git + CLAUDE.md gets you part of the way for one repo. Claude Code plugins and vendor marketplaces help for sharing inside one vendor’s ecosystem. Neither handles sharing the same asset across 30 repos, scoping a skill to a single team without duplicating it across plugins, or installing the same asset into multiple AI clients in the same team. sx is our attempt at the missing primitive. Apache-2.0, written in Go. Treats skills, MCP servers, commands, agents, hooks, and rules as versioned packages with a lockfile and a scope model (org / team / repo / path / individual). Translates one asset into the format each client expects: Claude Code, Cursor, Copilot, Cline, Codex, Gemini, Kiro, claude.ai, chatgpt.com. Repo: https://github.com/sleuth-io/sx Full writeup: https://www.sleuth.io/post/there-s-an-npm-shaped-hole-in-the-ai-tooling-stack/ Honest ask: does this match a problem your team is hitting, or are git and plugins enough? submitted by /u/detkin
Originally posted by u/detkin on r/ClaudeCode
You must log in or # to comment.