Best OpenCode skills: what to install and how to choose
OpenCode has no skills ranking, so choose by what loads cleanly: how its old and new docs differ, permissions, IDs and a free starter set. Read 21 Nov 2026.
- For
- OpenCode users choosing skills to install
- Written for
- OpenCode
- Time
- 6 min read · updated Nov 21, 2026
The short answer
OpenCode’s docs give no catalog, rating or install count for skills, so there is no “best” list to trust, and this page does not make one. What you can choose well is skills that load cleanly. OpenCode keeps two sets of docs, and they disagree on the rules that decide whether a skill loads: the new docs take a skill’s ID from its folder path and ignore a mismatched name, while the old docs require name to equal the folder name. Use a lowercase kebab-case folder, the same name, a clear description, and one copy of each skill, and it loads under both. Then set an allow, ask or deny permission for the ones you don’t want loaded without asking.
Searching for the best OpenCode skills finds lists of skills for every agent, because OpenCode reads the same SKILL.md folders as the others. What is specific to OpenCode is how it decides which skills to load, and that is where choices go wrong. This page uses OpenCode’s own documentation, read on 21 November 2026, and says where its two sets of docs differ. The OpenCode page has the install steps.
There are two sets of OpenCode docs
The OpenCode docs site labels its main set “V2 (latest)” and keeps the previous set at /v1/docs, headed as a previous version. Which one applies depends on the OpenCode you run, so read the rows below against the one you use. Where a row says the new docs don’t describe something, that is all it means: we did not test OpenCode.
If you pick skills for a team that may run either version, the folder that loads under both is a lowercase kebab-case name (1 to 64 characters, letters, numbers and single hyphens), a SKILL.md inside it, a name equal to that folder, a description of 1 to 1,024 characters, and no second copy of the same skill in another location.
Where skills for OpenCode come from
OpenCode reads ~/.config/opencode/skills and .opencode/skills as its own folders, and also ~/.claude/skills and ~/.agents/skills and their project versions. So a skill written for another agent can be used by copying its folder into one of those places, and OpenCode can also pull a set from a web catalog. The new docs describe a catalog as a base URL with an index.json that lists each skill by name, version and files, with same-origin relative paths. Agent skills marketplaces compares how each agent adds a catalog.
Read a skill before you copy it in, since a skill can tell your agent to run scripts. Safety checks before running a skill is the short list, and Anthropic skills and Claude skills on GitHub cover where public ones live. Whether a skill’s instructions suit OpenCode depends on the tools it names; the format is shared, the tools are not. If you use the OmO program that grew out of an OpenCode plugin, Oh My OpenCode covers what it adds.
A free starter set
Lookbk lists every skill for six agents, OpenCode among them, and its installer can write OpenCode’s folder. We have not recorded a run of any Lookbk skill in OpenCode, so treat these as skills written for the format, not tested in it. Each page shows what the skill rendered from its own example. These four are free.
Run the installer with the last part of a skill page’s address. With --shared it writes ~/.agents/skills/<skill> only, which keeps one copy because OpenCode also reads ~/.claude/skills. Start a new session afterwards and ask which skills it can load.
Decide what can load without asking
OpenCode lets you set a rule per skill ID, with wildcards. In the latest docs the rules sit in a list and the last match wins, so put the broad rule first and the exceptions after it.
The previous docs write the same idea as a map. allow loads at once, ask asks you first, and deny hides the skill from the agent and rejects loading it.
If a skill does not show up
The skill is not in the list
Check the file is named
SKILL.mdin capitals, or in the latest docs a Markdown file at the root of a source. Add adescription: without one, the latest docs say the skill is not advertised.It loads, but under a different name than you expect
In the latest docs the ID comes from the folder path, not
name, soteams/release/SKILL.mdisreleasewhatever itsnamesays. IDs are case-sensitive.It loads the wrong version
Another source defines the same ID. In the latest docs the later source wins, so a project
.opencode/skillscopy beats one in~/.config/opencode/skills. In the previous docs, delete the duplicate.It never starts
Check the skill permission for
askand approve the prompt, and check thatopencode/autoinvokeis notfalse.
Common questions
- What are the best OpenCode skills?
- There is no ranking to rely on: OpenCode’s documentation lists no catalog, rating or install count for skills. Choose skills that load cleanly under the docs you follow, read each one before you add it, and keep one copy of each.
- Where does OpenCode look for skills?
- In
~/.config/opencode/skills,~/.claude/skillsand~/.agents/skillsfor every project, and in.opencode/skills,.claude/skillsand.agents/skillsinside one. The latest docs add folders and web catalogs named in theskillssetting ofopencode.json. - Does a skill’s name have to match its folder in OpenCode?
- In the previous docs, yes. In the latest docs, no: the folder path sets the ID and
nameis only a label. Keeping them equal works under both. - Can I use Claude Code skills in OpenCode?
- OpenCode reads
~/.claude/skillsand.claude/skills, so aSKILL.mdfolder there is found. Whether the skill’s instructions fit OpenCode depends on the tools it names, which we have not tested. - How do I stop OpenCode loading a skill?
- Set a
denypermission for its ID, which hides it and rejects loading. In the latest docs,opencode/autoinvoke: falsein its metadata only hides it from the model’s list, and it can still be loaded by ID or with@skill-id. - Is there an OpenCode skills marketplace?
- The docs describe web catalogs you add yourself, as a base URL with an
index.json. They name no store. Agent skills marketplaces compares how the other agents add catalogs.
Sources
What this guide says about other companies’ tools comes from their own documentation, checked on Nov 21, 2026.
Did this guide help?
Read next
All guidesWhere skills live: folders for every agent
The folders Claude Code, Codex, Cursor and other agents read skills from, which copy wins when two share a name, and what cloud agents can see.
Agent skills marketplaces: how each agent adds a catalog
There is no one skills marketplace for every agent. How Claude Code, Cursor, OpenCode, Gemini CLI, Codex and Copilot each add a catalog, from their own docs.
SKILL.md format: the header fields each agent reads
SKILL.md header fields side by side for the Agent Skills spec, Claude Code, Cursor, Codex, OpenCode and Copilot: what travels between them and what does not.
Oh My OpenCode (now OmO): what it is and how to install it
Oh My OpenCode is now OmO. What changed, how its README installs it, what the install script does, how it carries OpenCode skills over, and its license.
Install a skill in any agent
Install a Lookbk skill in Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI or OpenCode: where each looks, how to check it loaded and how to run it.
See a skill’s result before you install it.
Every skill page shows what it makes, what it needs and which agents can run it.



