Repository navigation
[FEATURE]: support $skill-name syntax for invoking specific skills inline #24587
Closed as not planned
Description
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
It would be useful to have a shorthand syntax like $skill-name to explicitly tell the agent to use a specific skill during a conversation — similar to how Codex handles skill invocation.
Current behavior:
Skills are only auto-detected based on task context, or invoked via slash commands like /skill-name. There's no way to inline-reference a specific skill mid-prompt.
Proposed behavior:
Allow $skill-name (e.g. $git-commit, $mermaid-diagrams) anywhere in a prompt to explicitly load and apply that skill for the current task.
Use case:
When the auto-detection doesn't pick up the right skill, or when the user knows exactly which skill they want applied — a quick inline reference saves time vs. restructuring the prompt.
Reacted by Salih, Stevanus Pangau, KIRILL GOLIKOV, Darenome, Jake and Thevetat
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon Apr 27, 2026
This issue might be a duplicate of existing issues. Please check:
$skill-name— essentially the same feature request (inline$skill-namesyntax in prompts)$trigger for skills autocomplete in the prompt composer #20982: Add$trigger for skills autocomplete in the prompt composer — closely related, proposes$as an autocomplete trigger for skills with inline insertionPlease review these issues and consider adding your input there instead of opening a new one.
salihdev0 commentedon May 16, 2026
This is absolutely necessary. Even without the $ symbol, when you try a usage like
/<skill-name> /<second-skill-name>, autocomplete doesn't open for/<second-skill-name>. We need to fix this. Also, it fully reflects the skill content (as also mentioned in number #27686).Presmanes3 commentedon May 17, 2026
This would be a great feature to implement, with / to keep consistency over comands, etc...
jjdubski commentedon May 26, 2026
@salihdev0 @Presmanes3 and others that are interested. Please checkout my PR #29217 and support with a comment/reaction :)
github-actions commentedon Jul 26, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.