Skip to content
Founding Lifetime: every Pro skillfirst 100 members · $169 onceUpgrade
Lookbk
Sign In

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.

How skills work in OpenCode’s old and new docs
TopicPrevious docs (V1)Latest docs (V2)
What the skill is calledname is required, 1 to 64 characters, and must match the folder nameThe file path decides the ID. name is only a display label, and V2 does not enforce a match with the folder
Frontmattername and description required; description 1 to 1,024 characters; license, compatibility and metadata optionalAll of it is optional at runtime, but a skill with no description is not advertised to the model
Where it looksSix <name>/SKILL.md locations, and for a project it walks up from your folder to the git worktreeThe same six places, plus any folder or web catalog in the skills array of opencode.json. A Markdown file at the root of a source counts too
Two skills, one nameNames must be unique across all locationsThe later source wins, in a documented order from built-in skills up to your own skills entries
How the model loads oneskill({ name: "git-release" })The skill tool with { "id": "git-release" }, or you write @git-release in your prompt
Hide it from the modelA deny permission, or switch the skill tool off for an agentA deny permission, or opencode/autoinvoke: false in the skill’s metadata. The skill stays registered and can still be loaded by ID. The page does not describe switching the tool off
Permission settingsA permission.skill map of patterns to allow, deny or askA permissions list of rules with action, resource and effect; the last matching rule wins

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.

Kinetic Title Drop: an example of what it makes
Free
video
Kinetic Title DropClaude CodeCodexCursor+3 more agents
Swiss Grid Deck: an example of what it makes
Free
slides
Swiss Grid DeckClaude CodeCodexCursor+3 more agents
Editorial OG Card: an example of what it makes
Free
image
Editorial OG CardClaude CodeCodexCursor+3 more agents
Mono Editorial Landing: an example of what it makes
Free
web
Mono Editorial LandingClaude CodeCodexCursor+3 more agents

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.

Terminal
curl -fsSL https://lookbk.dev/cli.js | node - add kinetic-title-drop --shared

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.

opencode.jsonc (latest docs)
{
  "permissions": [
    { "action": "skill", "resource": "*", "effect": "allow" },
    { "action": "skill", "resource": "internal-*", "effect": "deny" },
    { "action": "skill", "resource": "experimental-*", "effect": "ask" }
  ]
}

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.

opencode.json (previous docs)
{
  "permission": {
    "skill": {
      "*": "allow",
      "internal-*": "deny",
      "experimental-*": "ask"
    }
  }
}

If a skill does not show up

  • The skill is not in the list

    Check the file is named SKILL.md in capitals, or in the latest docs a Markdown file at the root of a source. Add a description: 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, so teams/release/SKILL.md is release whatever its name says. 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/skills copy beats one in ~/.config/opencode/skills. In the previous docs, delete the duplicate.

  • It never starts

    Check the skill permission for ask and approve the prompt, and check that opencode/autoinvoke is not false.

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/skills and ~/.agents/skills for every project, and in .opencode/skills, .claude/skills and .agents/skills inside one. The latest docs add folders and web catalogs named in the skills setting of opencode.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 name is only a label. Keeping them equal works under both.
Can I use Claude Code skills in OpenCode?
OpenCode reads ~/.claude/skills and .claude/skills, so a SKILL.md folder 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 deny permission for its ID, which hides it and rejects loading. In the latest docs, opencode/autoinvoke: false in 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?

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.