Backward compatibility broken - enforcement of the /skill directory naming

[Melodeiro]

Description

Hello!
Im using different agents solution as it fits my requirements better. It is working inside of a /skills directory. Can you, please made an option to not to crash the opencode if there are /skills directory?

OpenCode version

Any 1.0.205+

Steps to reproduce

Install 1.0.205 version or higher
create ~/.config/opencode/skills directory
open opencode

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

[github-actions]

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

• Inconsistency in docs for where to install skills #6171: Inconsistency in docs for where to install skills - discusses the difference between ~/.opencode/skill and ~/.config/opencode/skill
• Global skills are not loaded #6292: Global skills are not loaded - related issue where skills in global config folder are not being discovered
• Skill discovery doesn't match Claude Code's skills/ directory structure #6177: Skill discovery doesn't match Claude Code's skills/ directory structure - related to skill directory naming compatibility

Feel free to ignore if none of these address your specific case.

[Melodeiro]

Here is an implementation which im using for reference. Maybe you can get some insights as well https://github.com/joshuadavidthomas/opencode-agent-skills

[rekram1-node]

are you disabling the native skills support then? I think opencode supoorts those same features

[Melodeiro]

@rekram1-node, the most desired option for me is dynamic discovery of skills, using semantic search, to make the context less bloated.

How can i disable the error message that /skills directory is wrong one? As i understood from the source code it is included in INVALID_DIRS and assertValid, and prevents opencode from starting up entirely

[rekram1-node]

not possible to disable on ur end without source code changes

[Melodeiro]

Yeah thats what im asking about, at least make it a non-strict rule, only as a warning

[rekram1-node]

we will change this on our end

[rekram1-node]

fixed in next release: b9ef09a