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
{{ message }}
Repository navigation
[FEATURE]: hierarchical skill autocomplete with /skill: prefix in TUI #35854
I have verified this feature I'm about to request hasn't been suggested before.
Problem
Skills are currently excluded from the TUI / autocomplete (autocomplete.tsx explicitly filters out source === "skill"). You can type /<skill-name> and it works, but there's no autocomplete to discover available skills — you have to use the /skills dialog instead.
Proposal: /skill: prefix for hierarchical autocomplete
Instead of dumping all skills into the flat / list (would clutter it), add a dedicated /skill: prefix:
/skill: → shows all skill groups
/skill:superpower → shows skills under superpower
/skill:superpower:brainstorming → select and invoke
The : naturally maps to the group:name convention many skills already follow (e.g. superpower:brainstorming, taste-skill:soft-skill).
Technical note
The full pipeline already supports this — skill names flow from SKILL.md → command registration → ACP sync → TUI, and submitting /<skill-name> works end-to-end. The missing piece is only the autocomplete UI layer.
Agreed with the duplicate check — this largely overlaps with #34410. My specific proposal (hierarchical /skill: prefix for namespacing) is more of an implementation approach within that same scope.
Closing in favor of #34410. I'll add my implementation notes over there.
Activity
github-actions commentedon Jul 8, 2026
This issue might be a duplicate of existing issues. Please check:
@and/as skill invocation/discovery triggers in the TUI prompt — very similar scope/autocomplete menu — overlapping problem areasteponeerror commentedon Jul 8, 2026
Agreed with the duplicate check — this largely overlaps with #34410. My specific proposal (hierarchical
/skill:prefix for namespacing) is more of an implementation approach within that same scope.Closing in favor of #34410. I'll add my implementation notes over there.
steponeerror commentedon Jul 8, 2026
Closing as duplicate of #34410. The hierarchical prefix idea has been noted over there.