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.

▲

detkin 3 hours ago | parent [-]

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

▲

bberenberg 3 hours ago | parent [-]

Yup I agree with the consistent access across surfaces ideal. WorkOS has some cool piping to support this and uses it for their internal version of the same thing. I think everyone experimenting here is a good thing. I expect we’ll end up with a few good commonly use OSS approaches, a few tech companies with NIH syndrome versions for their needs, and commercial options like we have with past technologies. These are more reflections of culture amongst buyers than anything else.

	▲	detkin 3 hours ago \| parent [-]
		It also wouldn't surprise me if the model companies ship a strong version of this to try to lock us all in a bit more. I hope that's not the case, or at the very least one storage and distribution system will work for all harnesses.