sx

I've been using a project called SX https://github.com/sleuth-io/sx to manage them. It has its quirks, but overall I find it to be very useful. One thing I've had to write as a layer on top of it is a way to assemble agent-specific CLAUDE.md / AGENTS.md from fragments. For example, I have a little fragment that has all agents respond to me in ordered list format. (Since they often ask a bunch of question all jumbled throughout a response, the ordered list format allows me to respond to those specific questions.) And I also have a growing anti-Claudeism fragment as well. Then I combine this with project-specific fragments and have it assembled into into a single CLAUDE.md / AGENTS.md. The layer also does a little reporting on the length of the resulting files and notifies me if it ever grows beyond a certain size.

Hi all, author here. SX started as a CLI to let developers share skills across AI clients without having to rely on git for storage. This allowed sharing at the Repo/Team/Org and Personal level. However, the more we spoke to users the more we realized that non-technical users were actually using skills more and more but they had no way to share. And there was no way you were going to get your legal team to install and learn git. SX 2.0 is targeting non-technical teams by adding a native Mac, Windows and Linux app. Our vault format was reworked so it can be used directly as a claude or codex plugin. And by storing your vault in Dropbox, Google Drive, iCloud or others you can be up and sharing in under a minute. 2.0 also adds an extension system with extensions that manage Skill Evals, LLM de-duping, metics and much more https://github.com/

If you want to share skills using something that has versioning, automatic updates, and focused on teams vs the internet at large, consider sx - https://github.com/sleuth-io/sx

If you want to share skills (and other tools) with teams at scale, consider sx - https://github.com/sleuth-io/sx [yup, my project :)]

Claude Code is amazing for individuals but terrible for teams. I spent the last six months building my perfect mix of MCP servers, subagents, commands and skills. Claude Code writes 100% of the code now, but sharing this with my team? Painful. 1. Blog posts and workshops don't work (and don't scale) 2. Committing tools to N repos means N PRs. A tool changes? N more PRs. 3. Same tools, different files or folders for each AI assistant; not everyone uses Claude Code It is like 1999 all over again; FTPing files up to prod and versioning with ".bak" suffixes. So I built sx. It is your team's private NPM for Claude Code (and others). How it works: # Set a git repo as your vault sx init --type git git@github.com:my-org/sx-vault.git # Add a local skill, command, mcp, etc sx add my-skill When your team installs sx, they automatically ge

Skills have been really helpful in my team as we've been encoding tribal knowledge into something that other developers can easily take advantage of. For example, our backend architecture has these hidden patterns, that once encoding in a skill, can be followed by full stack devs doing work there, saving a ton of time in coding and PR review. We then hit the problem of how to best share these and keep them up to date, especially with multiple repositories. It led us to build sx - https://github.com/sleuth-io/sx, a package manager for AI tools.