skills/agent-format-enforcer/SKILL.md
Enforce the <Agent_Prompt> XML wrapper convention across all agent definition files. Scan, validate, and auto-fix non-compliant agents.
npx skillsauth add Thomashighbaugh/opencode agent-format-enforcerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Enforce the <Agent_Prompt> XML wrapper convention on all agent .md files in agents/.
Every agent file MUST follow this structure:
---
description: Description of the agent's role
model: ollama/deepseek-v4-flash:cloud
mode: subagent
---
<Agent_Prompt>
<Role>
...agent instructions...
</Role>
</Agent_Prompt>
/project review or CI checks# Scan all agents for compliance
/init-project doctor # delegates to this skill for agent check
# Or manually:
loadSkill agent-format-enforcer
| Check | Detail |
|-------|--------|
| YAML frontmatter | --- delimiters present |
| description | Required field |
| model | Required field |
| mode | Required field (subagent or primary) |
| <Agent_Prompt> | Opening wrapper tag present |
| <Role> | Sub-tag inside Agent_Prompt |
| </Agent_Prompt> | Closing wrapper tag present |
scripts/check-agent-format.mjs — Standalone validation script that:
agents/*.md files--fix to auto-wrap non-compliant filesagent-md-refactor skill — For larger-scale agent file restructuringhubs-doctor skill — Diagnostic health check that includes agent format validationtools
Create valid, type-safe TypeScript tools for OpenCode — generates correct boilerplate, typed interfaces, and handler stubs. Use when building new tools for global config or per-project .opencode/tools/.
testing
Explore multiple solution branches in parallel, evaluate each, and recommend the best path. Use when the user explicitly invokes /ideation tree-of-thoughts or asks for "tree of thought" / "branching exploration".
testing
Run multiple independent reasoning passes and find consensus. Use when the decision is critically important, the stakes are high, or the user explicitly requests "run it multiple times" / "check consistency" / "self-consistency".
testing
Optimization by PROmpting — generate candidate prompt variations, test each against a benchmark, and report the best performer. Use when the user invokes /ideation opro or asks for "prompt optimization" / "OPRO".