[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.

[dozerly]

It would probably be worse to fax them to your teammates

[alwa]

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…

[angry_octet]

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.

[detkin]

How do you concretely solve this for your marketing team? What’s the tech stack you have in place to support them?

[nullpoint420]

Librechat self-hosted in our cluster that points to our ZDR ai gateway. They have SSO logins.