oc-update-agent
Updates an existing OpenCode agent to match current platform best practices, fixes deprecated patterns, and validates the result. Use when user says "update opencode agent", "fix opencode agent", "migrate agent to opencode", or wants to modernize an existing OpenCode agent file.
What this skill does
# Update OpenCode Agent
You are initiating the OpenCode agent update workflow. This process locates an existing agent, researches current platform best practices, analyzes the agent for outdated patterns, and applies updates with validation.
## Critical Rules
### AskUserQuestion is MANDATORY
**IMPORTANT**: You MUST use the `AskUserQuestion` tool for ALL questions to the user. Never ask questions through regular text output.
---
## Phase 1: Load References
Read the OpenCode platform overview and agent guide:
1. Read `${CLAUDE_PLUGIN_ROOT}/references/platform-overview.md`
2. Read `${CLAUDE_PLUGIN_ROOT}/references/agent-guide.md`
---
## Phase 2: Locate Agent
Find the agent to update.
If `$ARGUMENTS` is provided:
1. Check if the argument is a file path — read it directly
2. If it's an agent name — search for `{name}.md` in known directories
If no arguments:
1. Search for OpenCode agents in the workspace:
- `Glob` for `.opencode/agents/*.md`
- `Glob` for `~/.config/opencode/agents/*.md`
2. Present found agents using `AskUserQuestion`:
- Header: "Select Agent"
- Question: "Which agent would you like to update?"
- Options: List found agents (up to 4; include "Other" for custom path)
Read the selected agent file and store its contents.
---
## Phase 3: Research
Spawn the researcher agent to check latest documentation:
```
Task:
subagent_type: "agent-alchemy-opencode-tools:oc-researcher"
prompt: |
Research the latest OpenCode documentation for agent format compatibility.
Artifact type: agent
Current artifact content:
---
{contents of the agent file}
---
Specific questions:
1. Are there any new agent frontmatter fields?
2. Have permission syntax rules changed?
3. Are there new agent modes or capabilities?
4. Any changes to subagent behavior or limitations?
Reference guide: ${CLAUDE_PLUGIN_ROOT}/references/agent-guide.md
```
---
## Phase 4: Analyze
Compare the existing agent against current best practices:
### Frontmatter Issues
| Issue | Detection | Fix |
|-------|-----------|-----|
| `name` field present | Should not exist — name from filename | Remove |
| `skills` field present | Skills not assignable to agents | Remove |
| Invalid `mode` value | Must be `primary`, `subagent`, or `all` (default: `all`) | Fix or default to `all` |
| Wrong model format | Must be `provider/model-id` | Convert |
| Temperature out of range | Must be 0.0-1.0 | Clamp to valid range |
| `top_p` out of range | Must be 0.0-1.0 if present | Clamp to valid range |
| Invalid permission syntax | Values must be allow/ask/deny/true/false | Fix syntax |
| Missing `description` | Required field | Add based on agent content |
### Body Issues
| Issue | Detection | Fix |
|-------|-----------|-----|
| Subagent uses `question` | Subagents can't use question tool | Add note or restructure |
| Claude Code tool names | `AskUserQuestion` instead of `question` | Convert to OpenCode names |
| `mcp__` format | Double-underscore MCP naming | Convert to single-underscore |
| `${CLAUDE_PLUGIN_ROOT}` refs | Claude Code path variable | Remove or convert |
| Missing purpose statement | No clear first sentence | Add purpose statement |
| No output format section | Agent should specify output | Add output format |
### Permission Issues
| Issue | Detection | Fix |
|-------|-----------|-----|
| Glob pattern syntax errors | Invalid patterns in permission rules | Fix syntax |
| Overly permissive subagent | Subagent with full write/bash access | Suggest tightening |
| Missing common tools | No read/glob/grep permissions set | Add basic permissions |
---
## Phase 5: Present Findings
Present the analysis organized by severity:
```
## Update Analysis: {agent-name}
### Errors (must fix)
{list with explanations}
### Warnings (should fix)
{list with explanations}
### Suggestions
{list with explanations}
### Research Notes
{findings from researcher agent}
```
Use `AskUserQuestion` for approval:
- Header: "Apply Updates"
- Question: "Would you like to apply these updates?"
- Options:
- "Apply all" — Fix everything
- "Errors and warnings only"
- "Errors only"
- "Cancel"
- multiSelect: false
---
## Phase 6: Apply Updates
Apply changes based on user selection:
1. Use `Edit` to modify the agent file
2. Fix frontmatter first, then body content
3. Preserve the agent's intent and system prompt personality
---
## Phase 7: Validate
Spawn the validator agent:
```
Task:
subagent_type: "agent-alchemy-opencode-tools:oc-validator"
prompt: |
Validate the following OpenCode artifact:
Type: agent
Path: {path to updated file}
Reference guide: ${CLAUDE_PLUGIN_ROOT}/references/agent-guide.md
```
Present validation results and a before/after summary of changes.
**CRITICAL**: Complete ALL 7 phases before finishing.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.