[FEATURE]: Add visual feedback for valid skill slash commands

[gpaiva00]

Feature hasn't been suggested before.

• I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

When a user types a valid skill slash command, the prompt input should show subtle visual confirmation that the skill exists.

The leading valid skill token should render with blue/bold feedback while preserving the raw prompt text and normal submit behavior.

This applies to skill-backed commands from synced command data where source === "skill", without changing autocomplete, command registration, APIs, or SDK output.

[github-actions]

This issue doesn't fully meet our contributing guidelines.

What needs to be fixed:

• No issue template was used. This appears to be a feature request, so please use the Feature Request template, which requires: a title starting with [FEATURE]:, a verification checkbox confirming the feature hasn't been suggested before, and a description of the enhancement.

Please edit this issue to address the above within 2 hours, or it will be automatically closed.

---

This issue might be a duplicate of existing issues. Please check:

• [FEATURE]: Add $ trigger for skills autocomplete in the prompt composer #20982: Feature request to add $ trigger for skills autocomplete in the prompt composer — overlaps with skill invocation discoverability
• [FEATURE]: support $skill-name syntax for invoking specific skills inline #24587: Feature request for $skill-name inline syntax to explicitly invoke skills — similar goal of surfacing skill usage in the prompt input

If you believe this was flagged incorrectly, please let a maintainer know.

[github-actions]

Thanks for updating the issue! It now follows the contributing guidelines and feature request template. Your request is clear and concise. We appreciate you taking the time to make the necessary edits.

[github-actions]

To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.