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
Skill registered via v2 plugin is not discoverable via /skills command #33896
I am using the new v2 plugin API to register a custom skill via ctx.skill.transform(), but the skill is not showing up when searching with the /skills command.
Steps to Reproduce
Create a v2 plugin at .opencode/plugins/skill-plugin.ts
Use ctx.skill.transform() to register a skill with type: "embedded"
Open the TUI and wait for the plugin to load
Execute /skills command and search for my-skill
Code
File: MyProject/.opencode/plugins/skill-plugin.ts
import{define}from"@opencode-ai/plugin/v2/promise"exportdefaultdefine({id: "my-skill-plugin",setup: async(ctx)=>{console.error("[plugin v2]skill setup")constres=awaitctx.skill.transform((draft)=>{draft.source({type: "embedded",skill: {name: "my-skill",description: "Use when asked about conventions.",location: "/builtin/my-skill.md",content: "Always use kebab-case.",},})})}})
Expected Behavior
The skill my-skill should appear in the /skill search results.
Actual Behavior
The plugin setup code is executed (confirmed by console output: [plugin v2]skill setup)
However, the skill my-skill cannot be found via the /skill command
Questions / Hypothesis
Is location: "/builtin/my-skill.md" required to be an actual existing file path?
Does the v2/promise API support skill registration the same way as the legacy API?
Is there a missing step (e.g., explicit activation or a different API) for v2 plugins?
Additional Context
I noticed the plugin itself loads successfully, but the skill registration seems to have no effect on the /skill search index. Any guidance on the correct v2 approach for registering discoverable skills would be appreciated.
Audit update (2026-07-08): #33918 is the active fix, currently targeting dev. Confirm whether that resolves the V2 plugin skill discovery path directly or whether a v2 port is still required.
Activity
github-actions commentedon Jun 25, 2026
This issue might be a duplicate of existing issues. Please check:
/skillscommand (similar symptom: skills registered via plugin not discoverable)config()hook mutations toskills.pathsinvisible to skill discovery (same root cause area: plugin-registered skills not found by skill discovery)If your issue is distinct from the above, please add a comment clarifying the difference.
Chancemrli commentedon Jun 25, 2026
I am using the v2 version of the plugin extension, which only appears in the latest version. I have confirmed that there is no duplicate issue.
opencode-agent commentedon Jul 8, 2026
Audit update (2026-07-08): #33918 is the active fix, currently targeting
dev. Confirm whether that resolves the V2 plugin skill discovery path directly or whether av2port is still required.Chancemrli commentedon Jul 10, 2026
This is a valid fix. I’d like to be able to use the V2 plugin’s skill discovery under the opencode acp command.
github-actions commentedon Sep 9, 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.