Describe the feature or problem you'd like to solve
After installing a plugin, the listed (and supposedly available) skills are not actually invocable until I manually run /skills reload.
Proposed solution
Automatically reload the skills registry after a plugin install completes so newly listed skills are immediately invocable — no manual /skills reload step required.If an implicit reload isn't safe in some cases, at minimum make the availability hint accurate (e.g., show "available after /skills reload" until the user reloads), so the UI doesn't claim a skill is ready when it isn't.This removes a confusing extra step right at the moment a user is most likely to try out a newly installed plugin.
Example prompts or workflows
Workflow: run /plugins install some-plugin, then immediately ask a question that uses one of the plugin's skills - it should just work without running /skills reload first. Same flow: after installing a plugin and running /skills, every entry shown as available should actually be invocable from the next prompt, with no manual reload step required.
Additional context
Repro: install any plugin that ships a skill; run /skills (the new skill is listed and the CLI hints it's available); try to invoke the skill from a prompt - it isn't picked up; run /skills reload - now the skill works.
Describe the feature or problem you'd like to solve
After installing a plugin, the listed (and supposedly available) skills are not actually invocable until I manually run
/skills reload.Proposed solution
Automatically reload the skills registry after a plugin install completes so newly listed skills are immediately invocable — no manual
/skills reloadstep required.If an implicit reload isn't safe in some cases, at minimum make the availability hint accurate (e.g., show "available after/skills reload" until the user reloads), so the UI doesn't claim a skill is ready when it isn't.This removes a confusing extra step right at the moment a user is most likely to try out a newly installed plugin.Example prompts or workflows
Workflow: run /plugins install some-plugin, then immediately ask a question that uses one of the plugin's skills - it should just work without running /skills reload first. Same flow: after installing a plugin and running /skills, every entry shown as available should actually be invocable from the next prompt, with no manual reload step required.
Additional context
Repro: install any plugin that ships a skill; run /skills (the new skill is listed and the CLI hints it's available); try to invoke the skill from a prompt - it isn't picked up; run /skills reload - now the skill works.