Conciseness

The body is lean and information-dense — a decision table ('Scope... Controls when the agent triggers'), WHY-annotated anti-patterns, and copy-paste blocks with no explanation of concepts Claude already knows. Minor trimming is possible: the permission YAML in Quick Start substantially duplicates the GOOD example in Anti-Patterns, which keeps it just below the anchor-5 'every token earns its place' bar. It is clearly above anchor 3, which requires unnecessary explanation.

Actionability

Guidance is mostly executable: a complete copy-paste agent file, a concrete permission block, a BAD/GOOD permission and prompt comparison, and a verification command ('Run `bun run opencode` and type `/agents`'). Minor gaps keep it from anchor 5: troubleshooting flows for stated triggers like 'My agent ignores context' are only reachable via the reference file, and 'Phase 1.5 — Research' gives no inline pointer to how/where to research.

Workflow Clarity

The Creation Workflow gives a clear 4-phase sequence with an explicit iteration checkpoint ('Show draft, iterate until user approves') and an inline validation step ('Run `bun run opencode` and type `/agents` to confirm the new agent appears'). It falls short of anchor 5 because the phases themselves are one-line summaries — detailed sub-steps and error-recovery guidance are deferred to references/agent-patterns.md rather than the checkpoints being fully explicit inline; nothing here is destructive or batch, so no cap applies.

Progressive Disclosure

Good structure: an ~85-line overview with clearly labeled sections, two one-level-deep references that exist in the bundle and are well signaled with per-file descriptions ('references/agent-patterns.md — Creation phases, patterns...', 'references/opencode-config.md — Full frontmatter schema...'). The gap from anchor 5 is the Eval Scenarios section, whose three links (evals/scenario-0..2/task.md) point to files that do not exist in the bundle — broken navigation links, though the core reference structure is solid, placing this above anchor 3.

Specificity

Opens with concrete actions ('Create and refine OpenCode agents via guided Q&A') and the trigger clauses enumerate concrete tasks ('configuring AGENTS.md frontmatter', 'setting subagent_type', 'defining allowed-tools', 'restricting permissions', 'writing a system prompt'). It lists several specific capabilities with only minor gaps (e.g., troubleshooting/refinement actions are implied via examples rather than stated), so it sits above anchor 3 ('1-2 concrete actions, not comprehensive') but below anchor 5, which would require a fuller list of stated capability actions rather than mostly trigger-side task phrasing.

Completeness

Explicitly answers 'what' ('Create and refine OpenCode agents via guided Q&A') and 'when' via a full 'Use when...' clause with concrete trigger conditions plus example request phrasings. This directly matches the anchor-5 example structure (capability statement + 'Use when...' + concrete triggers); it is clearly above anchor 4, where the 'when' would be less explicit or lack concrete phrases.

Trigger Term Quality

Comprehensive natural-language coverage including synonyms, technical config keys users would quote ('AGENTS.md frontmatter', 'subagent_type', 'allowed-tools', 'mode: subagent', 'permission block', 'Task tool'), and five example user utterances ('Create an agent for code reviews', 'My agent ignores context', 'Add a database expert subagent', 'Make my agent faster', 'Agent triggers on wrong requests'). This matches the anchor-5 pattern of covering natural terms, synonyms, and exact phrasings; no common variations are obviously missing.

Distinctiveness Conflict Risk

The niche is clear ('OpenCode agents', 'AGENTS.md frontmatter', 'Task tool delegation pattern') with distinct triggers, but a few phrases like 'writing a system prompt' and 'Make my agent faster' are generic enough to overlap with general prompt-engineering or agent-tuning skills. That is minor overlap risk with closely related skills (anchor 4) rather than the minimal-conflict, fully distinct profile of anchor 5.