https://github.com/OpenHands/agent-canvas/pull/720 - This fixes an issue brought up by @modern-fireman-99755 where we don't identify "Built-In" vs "Personal" Skills, and the design was generally old. I've added a top header and cleaned up the design a touch. I've kept the current tags ie. Knowledge, Repository, etc. but I think we'll want to revisit them in light of current work in skills. The Available Skills modal is the first UI that groups skills by where they come from. I initially used Personal and Built-in based on Vasco's feedback, but those terms don’t match the rest of the app. The backend already speaks in

project

/

user

/

public

(

load_project

,

load_user

,

load_public

). The Skills settings page uses “default skills” for the catalog. But perhaps we want to change this if it's too vague? Decision: section headers are Project skills → User skills → Public skills, aligned with the API. Let me know if there are opinions. I felt it should be kept consistent with the docs but also feel like calling skills Built-in or Default may be more descriptive than Public. Thoughts? @hundreds-twilight-32833

I'll check out the PR if I can today. I still don't know what Knowledge is in that screenshot 🫠

in short: a "knowledge" skill is a trigger-activated content/context But perhaps we should use another name/tag for that