OK! I made this PR for a frontend improvement that's been missing for me personally: github.com/OpenHands/OpenHands/pull/16124 Basically I added filters to filter the skills on the

/skills

page by category. More screenshots and info in the PR and referenced issue.

This has also been something I wanted off and on when setting up skills. Will the categories work with other skills that get added in?

Yep, for skills that come from the extensions catalog. The category isn't hardcoded here, it's generated from the

category

field on each skill's marketplace entry and baked into

SKILLS_CATALOG

, so a new skill with a category just shows up in the rail with no canvas change. User and project skills are the exception though: in the current iteration they all land in the "other" category. Because

/api/skills

drops SKILL.md frontmatter, so a local

category:

never reaches the frontend. They're still filterable by Source (personal/project/public) and if the agent server were to start sending frontmatter it would work with no frontend change.

I pulled the branch down but couldn't get the

/skills

route to run. Might need a merge from main back into it?

Did you also pull down the supplementary branch in the extensions repo and followed the "how to test" instructions mentioned in the PR?

I did not. Completely missed that facepalm

You're not the first to miss it... I think we wired our brains to skip the "AI summary" section of the PR body already 😅

Might need to bump the automations PR and make sure folks are good with it too. I'm not super familiar with the marketplace taxonomy stuff so I don't know how this may or may not effect any of it