sx 2.0 - Share AI skills via Dropbox without Git or Terminal
Show HN: Sx 2.0 – Share AI skills with your team through a Dropbox folder
sx 2.0 is a native desktop app for Mac, Windows, and Linux that transforms shared cloud folders into AI skill servers. It solves the distribution gap for non-technical teams by allowing users to share AI skills, MCP configs, and commands through Dropbox, Google Drive, or OneDrive without requiring Git or a terminal. The app automatically translates assets into formats for Claude Code, Cursor, Copilot, and Gemini, ensuring seamless integration. With a new extension system for team health monitoring and a plain-text vault format, sx 2.0 makes AI knowledge sharing accessible to marketing, legal, and ops teams while retaining full power for developers.
Your teammate drops a skill in the shared folder, you click one button, and it's live in your AI client.
- angry_octet
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.
- bberenberg
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.
- btown
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!
- est
We hosted shared skills via a git repo.
Simple pull & push would do.
- try-working
I feel that skills should live in the repo folder so they can be used by everyone on the project.