You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, all skills registered in .skill-lock.json are globally visible across all modes. Although SKILL.md supports a modeSlugs frontmatter field to declare which modes a skill belongs to, the platform does not filter skills based on this field when building the available_skills list.
Manually adding modeSlugs to local skills/*/SKILL.md files is not a durable solution — well-known source updates overwrite local changes.
Context (who is affected and when)
When the source is updated
Desired behavior (conceptual, not technical)
Add project-level and user-level configuration mechanisms for declaring skill-to-mode binding relationships, thereby overriding the global registration information — without modifying any skill source files.
Constraints / preferences (optional)
No response
Request checklist
I've searched existing Issues and Discussions for duplicates
This describes a specific problem with clear context and impact
Activity