Why no skills support? #159
Description
This is more of a discussion than an issue, but I think it's necessary to be addressed directly or else you'll keep getting PRs for skills support.
I have see there have already been two PRs for skills declined, in one case saying this would be better addressed as an external package.
I am curious as to why it is the preference for Laravel to exclude direct support of skills? It seems to me that it would be good if the framework took advantage of this package to express an opinion as to how to organize skills for AI agents?
I think the skills concept in AI agents is a hugely successful means to empower agents to be prepared to respond to a large spectrum of possible actions without bloating the context window with too much information out of the gate. Aside from the significant token cost increase from doing so, eventually such agents become pretty poor at deciding what to do, whereas if skills are prepared to respond to keywords then the response can be focused.
Tools are definitely great for delegating, and I like leaning toward a bias in favor of using tools wherever that works, but I find that skills are a great way to help an agent decide which tool to call or how to handle unusual edge cases.
In the end, I think if Laravel AI SDK decides to exclude direct support for skills, it will force most everyone to select third-party solutions. That isn't bad in itself, but I think it's worth documenting why that's the preference so that people can understand how best to compliment the goals of this project.
Thanks!