Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Agentic Resource Discovery Specification

agenticresourcediscovery.org

Post reply on HN
Print view View original

11–20 of 23 posts

Re: Agentic Resource Discovery Specification

#11

Post by nimonian »

gavinray wrote: post #3

I work at a company with an LLM-adjacent tool. The best solution we could find for this problem was a combination of a Wiki + "Saved Programs" (executable scripts). When you ask a question, the system does a fuzzy Wiki search to see if any topic has relevant info. Wiki links serve as "graph edges" that form a Knowledge Graph. So lets say I ask "What products from the FOOBAR API sold least last month?" The agent would…

Very close to this at my company. We have docs each of which having its description in the yaml. An MCP tool lists the doc sections, a full section with its descriptions, or the entire contents of a doc. A kind of progressive disclosure. Works really well. We even write "skills" this way so they can be used in all our chat environments.

Re: Agentic Resource Discovery Specification

#12

Post by _pdp_ »

Why not ask the agent to read .well-known/agent.md (or better yet something.com/agent.md) and do a bootstrap if it is allowed! to do so. It can download skills, configure mcps, etc.

There is no need for another file IMHO.

Re: Agentic Resource Discovery Specification

#13

Post by jonkomet »

iandanforth wrote: post #6

This is search. Please don't reinvent search with a new acronym. Agents can use Google. They can also see all the same signals humans do to judge quality. Maybe there's a need for a specialized directory, but does it need a spec or an acronym? No.

[dead]

Re: Agentic Resource Discovery Specification

#14

Post by verdverm »

wslh wrote: post #2

This seems useful as a standard interface, but, again, doesn’t solve the harder discovery problem. Once there is value in appearing in the top results, the system inherits the same adversarial dynamics as SEO/app stores, spam, scams, etc.

The homepage makes it clear this is not another centralized registry susceptible to such issues. The goal is to have a common mechanism inside enterprises. A key aspect here is having agents appear in discovery, so they can call each other. You can see this in pattern Gemini Enterprise

Re: Agentic Resource Discovery Specification

#18

Post by nostrebored »

Building an ontology of how people think of and organize information, processes, and actions is not solved via markdown. It’s not well solved intra company much less inter. The systems that do solve some of this are optimizing for unstructured retrieval and will continue to.

Imposing a structure on this unstructured discovery feels like it ignores all progress in IR, and imposes a farcical structure that doesn’t have a tangible benefit.

Re: Agentic Resource Discovery Specification

#20

Post by xtiansimon »

gavinray wrote: post #3

I work at a company with an LLM-adjacent tool. The best solution we could find for this problem was a combination of a Wiki + "Saved Programs" (executable scripts). When you ask a question, the system does a fuzzy Wiki search to see if any topic has relevant info. Wiki links serve as "graph edges" that form a Knowledge Graph. So lets say I ask "What products from the FOOBAR API sold least last month?" The agent would…

Does this solution use a private/local LLM or something else? Sorry if the answer is obvious. I’ve just started considering this for an internal wiki to my company.
Post reply on HN