Closed RomanGoEmpire closed 8 months ago
That looks good, @RomanGoEmpire. I haven't gotten a chance to test it yet but do have some feedback on your question.
I am not sure if it should be a class or just a collection of methods that can be called by the agents.
Having a class that contains different functions (capabilities) that fall into the same context makes sense to me. If they are individual functions it will be harder to group them together. Building these classes for certain domains/interactions allows us to create tool loaders that will provide the available functions to all agents that need a certain skill/ability. For example, the need to communicate and collaborate using GitHub. There can be a generic class for Git, and also specific tool classes for BitBucket, GitLab, etc.
There could even be a Tool Loading Agent (TLA) that provides the right set of tools for agents during agent instantiation. This is very much on topic with the current primary directives. Let's get more perspectives on this in the discussions.
Thanks! Let's merge this and get more eyes on it. Thanks for including a readme.
GitHub API Wrapper Prototype
This merge request presents a prototype method demonstrating the use of GitHub as a communication platform through the GitHub API wrapper.
This tool should provide the essential methods for the agents to
Additional info
Question
I am not sure if it should be a class or just a collection of methods that can be called by the agents.
Please review the changes and provide feedback.