Is your feature request related to a problem?
New users who install ObsidiBot and configure skills never see them appear in the Obsidian command palette (Ctrl+P) unless they discover and manually enable the "Register skills as Ctrl+P command" setting. The setting defaults to off, so skills are silently invisible to the command palette — a capability that users would almost certainly want enabled from the start.
Describe the solution you'd like
Change the default value of the "Register skills as Ctrl+P command" plugin setting from false to true.
This makes skills immediately discoverable via Ctrl+P on a fresh install without any manual configuration required.
Describe alternatives you've considered
- Keep default as
false: Maintains current behaviour; users who don't want command palette entries can disable it. However, the discoverability cost for new users outweighs the benefit of a cleaner palette for users who never configure skills.
- First-run prompt: Ask users on first install whether to enable this. Adds friction and complexity for a low-risk default change.
Use Case
Any new user who installs ObsidiBot and adds skills to their vault. Without this change, they must know to visit settings and enable the option before their skills are accessible from Ctrl+P. With true as the default, skills "just work" from the command palette immediately.
Additional Context
This is a low-risk, single-line default value change. No behavioural logic changes required — only the initial value in the settings definition. Users who prefer not to have skills in Ctrl+P can still disable the setting explicitly.
Implementation Suggestions
In the plugin's settings registration code, change the default for registerSkillsAsCommands (or equivalent field) from false to true.
Is your feature request related to a problem?
New users who install ObsidiBot and configure skills never see them appear in the Obsidian command palette (Ctrl+P) unless they discover and manually enable the "Register skills as Ctrl+P command" setting. The setting defaults to off, so skills are silently invisible to the command palette — a capability that users would almost certainly want enabled from the start.
Describe the solution you'd like
Change the default value of the "Register skills as Ctrl+P command" plugin setting from
falsetotrue.This makes skills immediately discoverable via Ctrl+P on a fresh install without any manual configuration required.
Describe alternatives you've considered
false: Maintains current behaviour; users who don't want command palette entries can disable it. However, the discoverability cost for new users outweighs the benefit of a cleaner palette for users who never configure skills.Use Case
Any new user who installs ObsidiBot and adds skills to their vault. Without this change, they must know to visit settings and enable the option before their skills are accessible from Ctrl+P. With
trueas the default, skills "just work" from the command palette immediately.Additional Context
This is a low-risk, single-line default value change. No behavioural logic changes required — only the initial value in the settings definition. Users who prefer not to have skills in Ctrl+P can still disable the setting explicitly.
Implementation Suggestions
In the plugin's settings registration code, change the default for
registerSkillsAsCommands(or equivalent field) fromfalsetotrue.