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.
Same thoughts. Get a team github repository and add the marketplace.
Show HN: Sx 2.0 – Share AI skills with your team through a Dropbox folder
31–38 of 38 posts
Re: Show HN: Sx 2.0 – Share AI skills with your team through a Dropbox folder
#32I 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.
It would probably be worse to fax them to your teammates
I mean
Honestly from a BoM and version control standpoint, the fax might work out to be superior… they come timestamped; pop them in a filing cabinet, and…
Re: Show HN: Sx 2.0 – Share AI skills with your team through a Dropbox folder
#33Why 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.
> And there was no way you were going to get your legal team to install and learn git.
Re: Show HN: Sx 2.0 – Share AI skills with your team through a Dropbox folder
#34What's wrong with git?
Absolutely nothing, if it fits your usecase, but how do you handle e.g. reusing the same skill in multiple repos?
Are you manually keeping all copies in sync?
Re: Show HN: Sx 2.0 – Share AI skills with your team through a Dropbox folder
#35Re: Show HN: Sx 2.0 – Share AI skills with your team through a Dropbox folder
#36Who needs Dropbox? At my shop we're sharing skills with rsync...
Re: Show HN: Sx 2.0 – Share AI skills with your team through a Dropbox folder
#37Earlier quoted context omitted.
It would probably be worse to fax them to your teammates
I mean Honestly from a BoM and version control standpoint, the fax might work out to be superior… they come timestamped; pop them in a filing cabinet, and…
Legitimately, it would work better. I could bulk fax Skills to each of the branch offices on Monday afternoon in preparation for the AI teleconference bridge meeting at 8AM. They can fax back any suggested improvements on Friday.
Because the thermal paper fades you would need freshly faxed Skills every few weeks or the turbo encabulator would misfeed when they were loaded. In fact, I'd have the local steno pool ladies feed in a weekly fax with authorisation codes for each Skill, and without that it just wouldn't load.
Y2K technology for the win.
Re: Show HN: Sx 2.0 – Share AI skills with your team through a Dropbox folder
#38We'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/…
[dead]