Hacker News new | ask | show | jobs
by usrusr 12 days ago
Instead of requiring each session to understand the n tools used to solve a particular problem, you bundle up the solution in a conventional script (that's what I meant by "can", as in canning) that the agent can use with very little documentation in the context. When the model is smart enough to figure out the composition of underlying tools during regular execution, it will also be able to do the canning up as a script and write the lightweight documentation that turns the script into a skill. Subsequent use will only require that lightweight documentation in context.
1 comments

Won't you just end up with hundred of very specific scripts that can only do a very narrow thing? And now they'll all have their description and name in context.
depends on how many different problems the agent has to solve?