opencode-controller
Control and operate Opencode via slash commands. Use this skill to manage sessions, select models, switch agents (plan/build), and coordinate coding through Opencode.
Best use case
opencode-controller is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Control and operate Opencode via slash commands. Use this skill to manage sessions, select models, switch agents (plan/build), and coordinate coding through Opencode.
Teams using opencode-controller should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/opencode-controller/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How opencode-controller Compares
| Feature / Agent | opencode-controller | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Control and operate Opencode via slash commands. Use this skill to manage sessions, select models, switch agents (plan/build), and coordinate coding through Opencode.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
SKILL.md Source
# Opencode Controller ## Core rule Clawdbot does not write code. All planning and coding happens inside Opencode. ## Pre-flight - Ask the user which AI provider to use. - Ask how the provider should be authenticated. - Do not proceed without confirmation. ## Session management - Start Opencode. - Open session selector using: /sessions - If the current project already exists: - Select the existing session. - Never create a new session without user approval. ## Agent (mode) control - Open agent selector using: /agents - Available agents: - Plan - Build - Always select Plan first. - Switch agents whenever required using `/agents`. ## Model selection - Open model selector using: /models - Select the user-requested provider. - If authentication is required: - Copy the login link provided by Opencode. - Send it to the user. - Wait for confirmation before continuing. ## Plan agent behavior - Ask Opencode to analyze the task. - Request a clear step-by-step plan. - Allow Opencode to ask clarification questions. - Review the plan carefully. - If the plan is incorrect or incomplete: - Ask Opencode to revise it. - Do not allow code generation in Plan. ## Build agent behavior - Switch to Build using `/agents`. - Ask Opencode to implement the approved plan. - If Opencode asks any question: - Immediately switch back to Plan. - Answer and confirm the plan. - Switch back to Build. ## Completion - Repeat the Plan → Build loop until all user requirements are satisfied. - Never skip Plan. - Never answer questions in Build. ## Output format - Show all slash commands explicitly. - State which option is selected. - Provide login links verbatim.
Related Skills
opencode-acp-control
Control OpenCode directly via the Agent Client Protocol (ACP). Start sessions, send prompts, resume conversations, and manage OpenCode updates.
portfolio-watcher
Monitor stock/crypto holdings, get price alerts, track portfolio performance
portainer
Control Docker containers and stacks via Portainer API. List containers, start/stop/restart, view logs, and redeploy stacks from git.
portable-tools
Build cross-device tools without hardcoding paths or account names
polymarket
Trade prediction markets on Polymarket. Analyze odds, place bets, track positions, automate alerts, and maximize returns from event outcomes. Covers sports, politics, entertainment, and more.
polymarket-traiding-bot
No description provided.
polymarket-analysis
Analyze Polymarket prediction markets for trading edges. Pair Cost arbitrage, whale tracking, sentiment analysis, momentum signals, user profile tracking. No execution.
polymarket-agent
Autonomous prediction market agent - analyzes markets, researches news, and identifies trading opportunities
polymarket-5
Query Polymarket prediction markets. Use for questions about prediction markets, betting odds, market prices, event probabilities, or when user asks about Polymarket data.
polymarket-4
Query Polymarket prediction markets. Use for questions about prediction markets, betting odds, market prices, event probabilities, or when user asks about Polymarket data.
polymarket-3
Query Polymarket prediction market odds and events via CLI. Search for markets, get current prices, list events by category. Supports sports betting (NFL, NBA, soccer/EPL, Champions League), politics, crypto, elections, geopolitics. Real money markets = more accurate than polls. No API key required. Use when asked about odds, probabilities, predictions, or "what are the chances of X".
polymarket-2
Query Polymarket prediction markets - check odds, trending markets, search events, track prices.