Would love to hear more about how you thought about access controls. For example, not everyone will be able to see every file in Google Drive. So presumably you need to ensure this is restricted at the Claude Code level, but also in your publishing platform?
Glad you liked it! Right now access is inherited, users are able to see via Claude only what they would see manually. But if they expose something restricted via publishing platform - that's indeed something we are thinking about. There are pros and cons to any decision here TBH.
tbh with you, it’s a challenge ahead, right now the volume isn’t that big yet (not all of users are creating skills) but pretty soon it will be and we are trying to understand how to build the hierarchy of skills that will be manageable (through plugins/certifications/etc.)
Thank you for sharing. This is awesome.
Would love to hear more about how you thought about access controls. For example, not everyone will be able to see every file in Google Drive. So presumably you need to ensure this is restricted at the Claude Code level, but also in your publishing platform?
Glad you liked it! Right now access is inherited, users are able to see via Claude only what they would see manually. But if they expose something restricted via publishing platform - that's indeed something we are thinking about. There are pros and cons to any decision here TBH.
So does that mean the user oauths into all the tools they can access when the first set Claude up?
And then if they publish something, it includes their oauth token or something like that (and that’s the potentially problematic bit)?
I may or may not be vibe coding a system based on your post…
Yes, pretty much like this. It has it caveats but overall we try to just inherit users permissions.
so you have 1k people adding to claude skills, how do you ensure they arent degrading the system?
tbh with you, it’s a challenge ahead, right now the volume isn’t that big yet (not all of users are creating skills) but pretty soon it will be and we are trying to understand how to build the hierarchy of skills that will be manageable (through plugins/certifications/etc.)