For agent canvas skills, do we want to cache all o...
# proj-agent-canvas
q
For agent canvas skills, do we want to cache all of the openhands extensions skills? Alternatively we can curate a few default skills that seem most relevant for local use
✅ 1
m
I’ve already completed that. I’m currently testing it with the latest SDK version, and once that’s confirmed, I’ll proceed to merge the Agent-Canvas front-end PR. Afterward, the public skills will be available thankyou
q
just to clarify, how are you doing this? Are you using the agent server for skills persistence?
m
just to clarify, how are you doing this? Are you using the agent server for skills persistence?
I created and merged this pull request: refactor: optimize caching for public skills loading
q
Ah ok cool, seems like we're duplicating work I can close my PR then
Are you also working on creating skills flow which uses the agent server to persist the skill?
m
Regarding the front-end pull request, Vasco has submitted a similar one. I plan to review his PR with the latest SDK version and, once verified, proceed with merging it. fix(skills): populate slash menu and skills modal
Are you also working on creating skills flow which uses the agent server to persist the skill?
I am not working on this thankyou
q
Cool can we make sure we're using the openhands typescript client for pulling/saving skills from the agent server It doesn't like thats the case
m
We are utilizing
SkillsClient
from typescript-client to retrieve the list of skills.
thonk 1
q
Hmm how is that possible? I only merged the sdk pr as of today Is the typescript client PR above a duplication?
m
The
SkillsClient
in the typescript-client already includes
getSkills
. However, the current version of the TypeScript client does not provide create, update, or delete (CUD) operations.
✅ 1
q
Cool got it thanks for clarifying!
I'll close my PR then
m
Here is the output from Vasco’s PR. I’ve reviewed and tested his changes thankyou
🙌 1
ty 1