alt Hacker NewsShow HN: Sx 2.0 – Share AI skills with your team through a Dropbox folder
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/sleuth-io/sx-extensions.
It's Apache-2.0 and you can download it here https://github.com/sleuth-io/sx.
Comments
Hey Dylan, long time. The solution we landed on was that the skills should be authored by a small set of people who know what they’re doing and made available to non technical team members “magically”. This means either use your IT systems to push the configs, or embed them into an agent that doesn’t live on the desktop. We’ve gone the latter route and are building a whole company around solving this for regulated customers.
We've adopted a simple/similar Dropbox-based approach for skills and rules - each person's ~/.claude/skills is actually symlinked to a folder just for them inside a shared Dropbox folder, one that others on our (small) team can see and edit as well.
This solves a set of problems around people writing skills that reference artifacts or other skills that only exist on their system, and/or that reference their own name/information as the creator, and not knowing to make them self-contained and replicable. Luckily, adapting your colleagues' skills to self-contained versions and pulling them into your folder is trivial to instruct an agent to do. And you can have meta-skills that do this on the fly if a colleague has a skill that would unblock your project! (Editing to add a tip: make sure all the folders are set to offline visibility in Dropbox, rather than being loaded on demand from online.)
The courtesy simply has to be that you don't write into other people's skill folders unless/until they ask you to maintain something for them - at which point the words "I am assuming direct control" are said with all the necessary gravity and effect.
It's great to see someone putting UI and guardrails around this pattern!
We hosted shared skills via a git repo.
Simple pull & push would do.
I feel that skills should live in the repo folder so they can be used by everyone on the project.
Why not a private GitHub repo? It's hard to believe that the technical team could not write 1 skill which all non-technical teams could use to sync their skills to GitHub.
What's wrong with git?
Will a team wise GitHub repo a better solution?
- free version control - one line set up
[flagged]
I can't think of anything worse than sharing skills via Dropbox. The version management and AIBoM problems that generates is extremely painful. There's no way to track which version LLM is being used or match it against the skill, and people will likely load up too many skills.
You don't have to expose git repos to end users to use git, or some other database, to provision skills.