Draft PR of a skill to help build apps: github.com/OpenHands/extensions/pull/593 I'm not sure what normal testing looks like for this repo so if anyone sees anything out of place LMK

I just took a quick look at the skill. I didn't look at the content yet, but there are a couple of quick things we can test upfront that shouldn't take much time. Just a few points, though you might have already tested them: • Did you try asking the agent to create an app across a few different conversations to manually confirm that the skill gets triggered? (Just to verify the description is accurate.) • Are the scripts in the skill working? Have you tried running them?

I've been using the skill and making updates to have agents build some of the examples in github.com/OpenHands/canvas-apps so I've got some confidence there. The scripts are being run when the agents utilize the skill to verify so I think so. I could try pulling this final update down and doing another build to verify and share the usage. That could help give some more confidence before merge

Another point: this is not a default now, i.e., you have to actively selection that.

Have we ever talked about adding a skill-awareness skill that is small but tells the agent about other bigger skills so they could ask the user to enable them or something. For example if we don't enable this by default but a user says help me build a canvas app the agent might be able to say 'hey you can enable this series of skills that would help with that'. Like I use skills.sh/vercel-labs/agent-skills/vercel-react-best-practices a lot which helps with building react apps but it isn't included in our own extensions

This make more sense. So we give just a short text and, in the case, people can activate skills at their wish

Yea, that could be a good pattern to keep default turned on skills simple. Maybe others have a strong opinion. I do think for this skill I'm going to update the PR to make it a default skill. The pi comparison of "just tell canvas to build an app" is important

Agree with this being default. It’s a different world when the agent knows itself and helps people customize it 🙌

Now that we discuss this, I don’t know if the agent can use

invoke_skill

on a non-default non-enabled skill?

No it can not. Two points: • the agent doesn't know the name of the skill • and also if it knows the skill name, the skill is not loaded or/and can be missing

I mean like, if I tell it, “use frontend-design for this”… I expect it to figure it out actually, even if not with invoke…

so the agent probably will search in internet and search for this skill in our marketplace, I suppose.

Oh you mean if it’s not enabled, it’s not installed on its VM/local ?

Oh you mean if it’s not enabled, it’s not installed on its VM/local ?

Not sure but it can be the case. I should double check