Context
When using multiple skill packs alongside obsidian-skills (e.g. a bootcamp pack,
personal skills, etc.), it becomes hard to identify which skill belongs to which
pack directly from the autocomplete list.
Claude Code Desktop shows a small origin popup on hover (e.g. "(obsidian)"),
but OpenCode has no such UI — all skills appear flat in autocomplete with no
indication of their source.
Proposal
Prefix all skill names with obs-:
defuddle → obs-defuddle
json-canvas → obs-json-canvas (OR obs-canvas)
obsidian-bases → obs-bases
obsidian-cli → obs-cli
obsidian-markdown → obs-markdown
This convention is already emerging in the community for multi-pack setups.
The prefix is short, unambiguous, and consistent with the plugin name.
Why this matters
- Autocomplete search is substring-based, so typing
cli still finds obs-cli
- No discoverability loss, significant clarity gain in mixed environments
- Aligns with how other packs are being named (e.g.
bc- for bootcamp,
sys- for system utilities)
Would you consider adopting this convention? Happy to submit a PR if useful.
Context
When using multiple skill packs alongside obsidian-skills (e.g. a bootcamp pack,
personal skills, etc.), it becomes hard to identify which skill belongs to which
pack directly from the autocomplete list.
Claude Code Desktop shows a small origin popup on hover (e.g. "(obsidian)"),
but OpenCode has no such UI — all skills appear flat in autocomplete with no
indication of their source.
Proposal
Prefix all skill names with
obs-:defuddle→obs-defuddlejson-canvas→obs-json-canvas(ORobs-canvas)obsidian-bases→obs-basesobsidian-cli→obs-cliobsidian-markdown→obs-markdownThis convention is already emerging in the community for multi-pack setups.
The prefix is short, unambiguous, and consistent with the plugin name.
Why this matters
clistill findsobs-clibc-for bootcamp,sys-for system utilities)Would you consider adopting this convention? Happy to submit a PR if useful.