Gotcha. What would the ideal look like? Someone could create a financial doc they want to share then tell their agent to "Share foo.md with my team", and it would via mcp? On the backend, that mcp server takes the file and packages it into the plugin, which hopefully auto-updates?
Makes sense. Would a tool that let non-tech people easily share and distribute skills without needing git be worth adoption? Would the info being shared just be skills or something else?
This is an underrated comment. You could have the best product out there, but AI has not only lowered the effort for competitors but has flooded traditional ways to get your product known, from outbound sales to content marketing. Sometimes make you question whether there are customers anymore.
Why stop at skills though? If you are trying to solve the provisioning problem for agent tools, shouldn't that also include MCP, commands, hooks, rules, etc in addition to skills?
I could be wrong, but I don't think there is anything in the skills spec that prohibits a skill from having binaries? A skill may even choose to embed them to be able to run in sandboxed environments.
Agreed on skills not being static. Of course, with the way the internet works, I don't want them to be too dynamic either :)
If you want to share skills using something that has versioning, automatic updates, and focused on teams vs the internet at large, consider sx - https://github.com/sleuth-io/sx
Sleuth is a SaaS deployment tracker that pulls deployments from source repositories, feature flags, and other sources, in addition to pushes via curl. You can see Sleuth used to, well, track Sleuth at https://app.sleuth.io/sleuth