opencode-primitives
Installation
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)
- Skills: https://opencode.ai/docs/skills
- Plugins: https://opencode.ai/docs/plugins/
- MCP servers: https://opencode.ai/docs/mcp-servers/
- Config (opencode.json, locations, precedence): https://opencode.ai/docs/config/
Key Facts To Apply
Skills
- Skill files live in
.opencode/skills/<name>/SKILL.mdor global~/.config/opencode/skills/<name>/SKILL.md. - Skills are discovered by walking up to the git worktree and loading any matching
skills/*/SKILL.mdin.opencode/or.claude/skills/. SKILL.mdrequires 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.jsonpermissions (permission.skillallow/deny/ask).
Related skills
More from different-ai/openwork
solidjs-patterns
SolidJS reactivity + UI state patterns for OpenWork
558opencode-bridge
Bridge between OpenWork UI and OpenCode runtime
543tauri-solidjs
Tauri 2.x + SolidJS stack for OpenWork native app
506opencode-mirror
Maintain the local OpenCode mirror for self-reference
483openwork-core
Core context and guardrails for OpenWork native app
472browser-setup-devtools
Guide users through browser automation setup using Chrome DevTools MCP only. Use when the user asks to set up browser automation, Chrome DevTools MCP, browser MCP, or runs the browser-setup command.
97