Live data from Hacker News

Show HN: Sx 2.0 – Share AI skills with your team through a Dropbox folder

sleuth-io.github.io

1–10 of 38 posts

Show HN: Sx 2.0 – Share AI skills with your team through a Dropbox folder

#1
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.

Show HN: Sx 2.0 – Share AI skills with your team through a Dropbox folder
sleuth-io.github.io

Re: Show HN: Sx 2.0 – Share AI skills with your team through a Dropbox folder

#5
post #4

We hosted shared skills via a git repo. Simple pull & push would do.

I agree that that works pretty well for developers who work with a code repository everyday. But, if you're working on a mono-repo, you can end up with more skills loading than you'd like pretty quickily.

Have you had success with non-technical people using git as their primary sharing source?

Re: Show HN: Sx 2.0 – Share AI skills with your team through a Dropbox folder

#6
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.

Re: Show HN: Sx 2.0 – Share AI skills with your team through a Dropbox folder

#7

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 cu…

Hey man! Yeah, many of the non-techincal folks I've spoken to are using claude.ai or chatgpt.com. But I've been amazed at how many are using Claude CoWork or even Claude Code.

The theme seems to be wanting the same set of knowledge across any and every tool they use, without having to worry much about the mechanics of the how.

I agree that for security and governance conscious orgs a more robust server-side solution is probably what's needed. We've built that vault for sx as well. However, I am seeing that many larger orgs have decided to just build it themselves. There was a post from Mike at Gusto the other day saying as much.

The cost for build has just gotten so low now...

Re: Show HN: Sx 2.0 – Share AI skills with your team through a Dropbox folder

#8
post #5
post #4

We hosted shared skills via a git repo. Simple pull & push would do.

I agree that that works pretty well for developers who work with a code repository everyday. But, if you're working on a mono-repo, you can end up with more skills loading than you'd like pretty quickily. Have you had success with non-technical people using git as their primary sharing source?

yeah skills overwhelming is a problem. Splitting into sub-dirs works for now.

For us it's mostly developers.

Re: Show HN: Sx 2.0 – Share AI skills with your team through a Dropbox folder

#10
post #5
post #4

We hosted shared skills via a git repo. Simple pull & push would do.

I agree that that works pretty well for developers who work with a code repository everyday. But, if you're working on a mono-repo, you can end up with more skills loading than you'd like pretty quickily. Have you had success with non-technical people using git as their primary sharing source?

Git has easy to use GUI tools, particularly if you’re willing to use GitHub. I have not had trouble getting non technical staff to use it (book editors, graphic designers, writers, copywriters)
Post reply on HN