Repository navigation
/skill-name doesn’t invoke full skill system #24831
Description
Description
If you use the /skill-name command it will only copy the base skill prompt and not invoke the skill like it is supposed to. Therefore additional skill referenced files can not be found and do on.
Plugins
No response
OpenCode version
No response
Steps to reproduce
- make a skill which has a second reference file in it. The prompt should state it should answer with the info from the reference file
- use /skill-name and see how the agent tries to search for the reference file and likely doesn’t find it
- Use a prompt which says that it should use the skill and see how the skill is invoked and the reference info can be fetched directly
Screenshot and/or share link
No response
Operating System
No response
Terminal
No response
Activity
github-actions commentedon Apr 28, 2026
This issue might be a duplicate of existing issues. Please check:
/skill-namecommand doesn't work as expected — though that issue focuses on the skill not being found/searchable, while this one is about the skill being invoked but not loading its referenced files. If these are related, it may be worth consolidating.rekram1-node commentedon May 3, 2026
This is intentional behavior, not a bug
wienans commentedon May 4, 2026
@rekram1-node referring to your answere here this issue is still valid. As it is focusing on the fact that /skill-name does not invoke the skill itself.
#25439 (comment)
frankxhunter commentedon May 8, 2026
Hi, I want to work on this, is anyone working on it?
wienans commentedon May 9, 2026
@frankxhunter i am not sure I proposed a change in a PR but they closed it as they want to go away from the command pattern for skills. #25439 (comment)
So I think they have their own idea and yours might be closed too.
syahmiharith commentedon May 26, 2026
I traced this to skills being exposed through
Command.Serviceassource: "skill"withtemplate = item.content.Based on #25439, the fix should avoid extending the command-template path and route skill invocations through the skill tool behavior instead. I can send a small PR with a regression test for a skill that references an adjacent file.
fix: plugin spinner TTY check and skill file resolution
fix: plugin spinner TTY check and skill file resolution
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.
wienans commentedon Jul 26, 2026
@rekram1-node is that addressed in V2?