oh-my-opencode-slim

Configure agents, models, prompts, skills, and MCPs for oh-my-opencode-slim in OpenCode.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Tuning an OpenCode agent setup requires knowing which config files, prompt override paths, and schema rules oh-my-opencode-slim supports, and mistakes can silently change cost, permissions, or delegation behavior. This Skill guides safe, minimal configuration changes so agents behave the way you want across future sessions. ## Core Features & Use Cases - Agent and model tuning: Assign 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 agents: Define narrow specialist agents under agents.<name> with prompt and orchestratorPrompt so the Orchestrator routes work correctly. - Use Case: You notice the Orchestrator keeps spawning parallel writers that conflict. The Skill proposes a small rule in orchestrator_append.md, asks for confirmation, applies it, and reminds you to restart OpenCode. ## 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. The change applies on the next OpenCode run or after a restart.

How do I customize a built-in agent prompt in OpenCode?▼

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; only markdown override files work.

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

Yes, unknown keys under top-level `agents` become custom agents. Custom agents may define `prompt` and `orchestratorPrompt` directly in the JSON config, plus model, skills, and MCPs, unlike built-in agents.

Which config file takes precedence, .json or .jsonc?▼

The `.jsonc` file takes precedence over `.json` for user-level oh-my-opencode-slim config. Project-local files under `<project>/.opencode/` are checked before user-level config.

Why did my OpenCode config change not take effect?▼

Config, prompt, agent, skill, MCP, or plugin changes typically require an OpenCode restart to load. The change should apply on the next OpenCode run; restart OpenCode if you need it immediately.