Menu
Create OpenCode plugins and know where to load them.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | plugin-creator |
| description | Create OpenCode plugins and know where to load them. |
plugins/*.js or plugins/*.ts~/.config/opencode/plugins/*.js or .tsAdd npm plugin packages in opencode.json:
{
"$schema": "https://opencode.ai/config.json",
"plugin": ["opencode-helicone-session", "opencode-wakatime"]
}
export const MyPlugin = async ({ project, client, $, directory, worktree }) => {
return {
// Hook implementations go here
}
}
~/.cache/opencode/node_modules/.Follow the official OpenCode plugin docs: https://opencode.ai/docs/plugins/ Use the docs as the escape hatch when unsure.
Create new OpenCode agents with a gpt-5.2-codex default.
Create OpenCode custom commands for repeatable tasks.
Create targeted Cal links for specific people or teams
Use Chrome MCP to verify OpenWork UI flows, especially any feature that touches remote behavior. Triggers when user mentions: - "test with chrome mcp" - "ui verification" - "remote behavior test"
Start the OpenWork dev stack via Docker and verify real user flows via Chrome MCP. Triggers when user mentions: - "dev-up.sh" - "docker dev stack" - "verify in chrome mcp" - "test the real flow"
Run owpenbot/openwrk integration tests with Telegram test tokens. Triggers when user mentions: - "owpenbot tests" - "telegram test tokens" - "openwrk integration test"