opencode-primitives

different-ai/openwork · updated Apr 8, 2026

$npx skills add https://github.com/different-ai/openwork --skill opencode-primitives
0 commentsdiscussion
summary

Use this skill whenever OpenWork behavior is implemented directly on top of OpenCode primitives (skills, plugins, MCP servers, opencode.json config, tools/permissions). It anchors decisions to the official OpenCode documentation and keeps terminology consistent in the UI.

skill.md

Purpose

Use this skill whenever OpenWork behavior is implemented directly on top of OpenCode primitives (skills, plugins, MCP servers, opencode.json config, tools/permissions). It anchors decisions to the official OpenCode documentation and keeps terminology consistent in the UI.

Doc Sources (Always cite when relevant)

Key Facts To Apply

Skills

  • Skill files live in .opencode/skills/<name>/SKILL.md or global ~/.config/opencode/skills/<name>/SKILL.md.
  • Skills are discovered by walking up to the git worktree and loading any matching skills/*/SKILL.md in .opencode/ or .claude/skills/.
  • SKILL.md requires YAML frontmatter: name + description.
  • Name rules: lowercase alphanumeric with single hyphens (^[a-z0-9]+(-[a-z0-9]+)*$), length 1-64, must match directory name.
  • Description length: 1-1024 characters.
  • Access is governed by opencode.json permissions (permission.skill allow/deny/ask).

Plugins

  • Local plugins live in .opencode/plugins/ (project) or ~/.config/opencode/plugins/ (global).
  • npm plugins are listed in opencode.json under plugin and installed with Bun at startup.
  • Load order: global config, project config, global plugins dir, project plugins dir.

MCP Servers

  • MCP servers are defined in opencode.json under mcp with unique names.
  • Local servers use type: "local" + command array; remote servers use type: "remote" + url.
  • Servers can be enabled/disabled via enabled.
  • MCP tools are managed via tools in config, including glob patterns.
  • OAuth is handled automatically for remote servers; can be pre-registered or disabled.

Config (opencode.json)

  • Supports JSON and JSONC.
  • Precedence order: remote .well-known/opencode -> global ~/.config/opencode/opencode.json -> custom path -> project opencode.json -> .opencode/ directories -> inline env overrides.
  • .opencode subdirectories are plural by default (agents/, commands/, plugins/, skills/, tools/, themes/), with singular names supported for compatibility.

When to Invoke

  • Adding or adjusting OpenWork flows that reference skills, plugins, MCP servers, or OpenCode config.
  • Designing onboarding guidance that mentions skill/plugin installation, config locations, or permission prompts.
  • Implementing UIs that surface OpenCode primitives (skills tab, plugin manager, MCP toggles).

Usage

Call skill({ name: "opencode-primitives" }) before implementing or documenting any OpenWork behavior that maps to OpenCode primitives.

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.670 reviews
  • Zara Farah· Dec 16, 2024

    I recommend opencode-primitives for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Yuki Anderson· Dec 12, 2024

    Solid pick for teams standardizing on skills: opencode-primitives is focused, and the summary matches what you get after install.

  • Aisha Garcia· Dec 8, 2024

    opencode-primitives fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Chaitanya Patil· Dec 4, 2024

    I recommend opencode-primitives for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Anika Li· Dec 4, 2024

    opencode-primitives reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Yuki Thomas· Nov 27, 2024

    I recommend opencode-primitives for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Piyush G· Nov 23, 2024

    opencode-primitives fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Aisha Verma· Nov 23, 2024

    We added opencode-primitives from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Tariq Menon· Nov 15, 2024

    Useful defaults in opencode-primitives — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Emma Martinez· Nov 7, 2024

    opencode-primitives fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

showing 1-10 of 70

1 / 7