I see it as the solution being out there in “idea space”, and by having the agent search beforehand we can more efficiently explore this space before converging on the final solution.
Research-Driven Agents: When an agent reads before it codes
41–50 of 81 posts
Re: Research-Driven Agents: When an agent reads before it codes
#42Re: Research-Driven Agents: When an agent reads before it codes
#43Re: Research-Driven Agents: When an agent reads before it codes
#44I've been making skills from arxiv papers for a while. I have a one for multi-object tracking for example. It has a SKILL.md describing all important papers (over 30) on the subject and a folder with each paper's full content as reStructuredText. To feed Arxiv papers to LLMs I found that RST gives the best token count/fidelity ratio. Markdown lacks precision. LateX is too verbose. I have a script with the paper's url…
Re: Research-Driven Agents: When an agent reads before it codes
#45Re: Research-Driven Agents: When an agent reads before it codes
#46Re: Research-Driven Agents: When an agent reads before it codes
#47Earlier quoted context omitted.
Having a "indexed global data collection" of the markdown would be a kumbaya moment for AI. There's so much data out there but finite disk space. Maybe torrents or IPFS could work for this?
I'm actually sort of working on this! https://github.com/ctoth/propstore -- it's like Cyc, but there is no one answer. Plus knowledge bases are literally git repos that you can fork/merge. Research-papers-plugin is the frontend, we extract the knowledge, then we need somewhere to put it :)