Been seeing a lot of these lately, but none of them are truly viral. From what I understand, agentic resources have three storage levels.
1. Personal Skills/Resources (best to store in your .claude)
2. Repository-level resources (Best to store inside your repository)
3. Cross-repository resources (Best to store in registries/Standalone repositories)
there is also live discovery in an organization, think microservices, but your business team can deploy them too
I suspect aaif will look like cncf, dominated by enterprise and polluted to the point you cannot even comprehend the map, the land grabs are palpable and disuading
they already have a gateway listed we have no interest in (envoy required dependency, no thanks), planning to use GoModel instead
Been seeing a lot of these lately, but none of them are truly viral. From what I understand, agentic resources have three storage levels. 1. Personal Skills/Resources (best to store in your .claude) 2. Repository-level resources (Best to store inside your repository) 3. Cross-repository resources (Best to store in registries/Standalone repositories)
This spec is what makes these truly useful: https://agenticresourcediscovery.org/
Reference implementations: https://agenticresourcediscovery.org/ref_implementations/#ve...
Possible acceptance to the Agentic AI Foundation: https://github.com/AgenticResourceRegistry/AgenticResourceRe... (https://github.com/aaif/project-proposals/issues/59)
there is also live discovery in an organization, think microservices, but your business team can deploy them too
I suspect aaif will look like cncf, dominated by enterprise and polluted to the point you cannot even comprehend the map, the land grabs are palpable and disuading
they already have a gateway listed we have no interest in (envoy required dependency, no thanks), planning to use GoModel instead