oh-my-opencode-slim

Configure agents, models, prompts, skills, and MCPs for oh-my-opencode-slim plugin setups.

Updated Feb 25, 2026
One-click install
npx skills add https://github.com/voiddreamz/dotfiles --skill oh-my-opencode-slim-voiddreamz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: oh-my-opencode-slim
Source: https://github.com/voiddreamz/dotfiles/tree/main/.config/opencode/skills/oh-my-opencode-slim
Command: npx skills add https://github.com/voiddreamz/dotfiles --skill oh-my-opencode-slim-voiddreamz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Tuning an oh-my-opencode-slim setup involves scattered JSON/JSONC config files, preset structures, and markdown prompt override files, making it easy to apply changes in the wrong place or break existing settings. This Skill guides safe, minimal configuration edits so agent behavior improves without clobbering user customizations. ## Core Features & Use Cases - Agent and model tuning: Adjust models, variants, skills, and MCP permissions per built-in agent (orchestrator, oracle, librarian, explorer, designer, fixer, observer, council) within presets. - Prompt customization: Append or replace built-in agent prompts via markdown override files, with preset-specific variants and a defined lookup order. - Custom agent creation: Define focused specialist agents under agents.<name> with prompt and orchestratorPrompt for Orchestrator routing. - Use Case: If the Orchestrator repeatedly spawns overlapping parallel writers, the Skill proposes a narrow rule in orchestrator_append.md, asks for confirmation, applies it, and notes the restart requirement. ## Quick Start Ask the assistant to review your oh-my-opencode-slim config and propose a cheaper model assignment for the explorer and librarian agents.

Frequently Asked Questions about oh-my-opencode-slim

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I change the model for a specific agent in oh-my-opencode-slim?▼

Edit the active preset under `presets.<preset>.<agent>` in `~/.config/opencode/oh-my-opencode-slim.json` or `.jsonc` and set the `model` and optionally `variant` fields. Project-local `.opencode/oh-my-opencode-slim.json` overrides are checked before user config.

How do I customize a built-in agent prompt in oh-my-opencode-slim?▼

Create a markdown file like `~/.config/opencode/oh-my-opencode-slim/orchestrator_append.md` to append instructions, or `orchestrator.md` to fully replace the prompt. Built-in agents do not support `prompt` fields in the JSON config; markdown override files are the supported mechanism.

Can I add custom agents to oh-my-opencode-slim config?▼

Yes, unknown keys under top-level `agents` become custom agents. They can define `model`, `prompt`, `orchestratorPrompt`, `skills`, and `mcps` directly in the config, unlike built-in agents which require markdown files for prompt changes.

Does oh-my-opencode-slim config require a restart to take effect?▼

Config, prompt, agent, skill, MCP, and plugin changes generally apply on the next OpenCode run. Restart OpenCode if you need the changes to take effect immediately in the current session.

What is the difference between agent.md and agent_append.md prompt files?▼

The `{agent}.md` file fully replaces the bundled prompt and must restate all essential behavior, while `{agent}_append.md` only adds instructions after the existing prompt. Prefer append files for small tuning; if both exist, the replacement loads first and the append is added after.