CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

opencode-design-agents

Create and refine OpenCode agents via guided Q&A. Use when creating an agent file, improving an existing agent, configuring AGENTS.md frontmatter, setting subagent_type, defining allowed-tools, restricting permissions, designing agent routing, writing a system prompt, configuring mode: subagent, setting a permission block, or working with the Task tool delegation pattern. Examples: 'Create an agent for code reviews', 'My agent ignores context', 'Add a database expert subagent', 'Make my agent faster', 'Agent triggers on wrong requests'.

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

90%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, token-efficient overview with copy-paste-ready examples and genuine one-level-deep progressive disclosure. The two gaps are the dead eval-scenario links and validation being placed in Quick Start rather than woven into the creation workflow itself.

Suggestions

Remove the Eval Scenarios section or correct the evals/scenario-*/task.md paths — the linked files do not exist in the bundle, which undermines navigation trust.

Fold the validation step ('run `bun run opencode` and confirm via `/agents`') into the Creation Workflow as an explicit final checkpoint after Phase 3, so the sequence ends with verify-not-assume.

Add one line of error-recovery guidance (e.g., 'if the agent does not appear, check frontmatter YAML syntax') to close the feedback loop that is currently only implied by Phase 3.

DimensionReasoningScore

Conciseness

Lean body where every token earns its place: a decision table, terse anti-patterns with one-line WHYs, and a 'When NOT to use' section. 'An agent is a markdown file with YAML frontmatter' is OpenCode-specific convention, not knowledge Claude already has, so it is not padding.

5 / 5

Actionability

Fully executable guidance: copy-paste-ready frontmatter and permission YAML blocks, the exact target path '.opencode/agents/<name>.md', and a concrete verification command ('Run `bun run opencode` and type `/agents` to confirm'). Common cases are covered by worked examples.

5 / 5

Workflow Clarity

Clear phase sequence (1, 1.5, 2, 3) with a review feedback loop ('Show draft, iterate until user approves') and a validation checkpoint (run + `/agents` confirm). Not 5: the validation step lives in Quick Start rather than being integrated into the workflow sequence, and error-recovery/troubleshooting detail is delegated entirely to the reference file with only one-line phase summaries inline.

4 / 5

Progressive Disclosure

Good structure with two well-signaled, one-level-deep references (references/agent-patterns.md and references/opencode-config.md) that exist and match their in-body descriptions. Not 5: the Eval Scenarios section links 'evals/scenario-0..2/task.md' but no evals directory exists in the bundle, leaving dead navigation links.

4 / 5

Total

18

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is explicit about both capability and triggers, with concrete user-quoted examples that make routing unambiguous. Its only weakness is mild redundancy in the 'Use when' list ('setting subagent_type', 'configuring mode: subagent', 'setting a permission block' overlap somewhat), which does not affect any dimension's anchors.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — 'creating an agent file, improving an existing agent, configuring AGENTS.md frontmatter, setting subagent_type, defining allowed-tools, restricting permissions, designing agent routing, writing a system prompt' — with comprehensive coverage of the agent-design domain. Score 4 would require a coverage gap, and none is evident.

5 / 5

Completeness

Explicitly answers both what ('Create and refine OpenCode agents via guided Q&A') and when ('Use when creating an agent file, improving an existing agent, ...') with concrete trigger phrases, structurally matching the top anchor example.

5 / 5

Trigger Term Quality

Comprehensive natural terms including synonyms ('agent', 'subagent', 'permissions', 'system prompt', 'AGENTS.md') plus quoted phrases users would naturally say: 'Create an agent for code reviews', 'My agent ignores context', 'Make my agent faster', 'Agent triggers on wrong requests'. Nothing commonly-said is missing, so it matches the comprehensive anchor rather than the 'a few natural terms missing' anchor.

5 / 5

Distinctiveness Conflict Risk

Clear niche (OpenCode agent design) with platform-specific triggers like 'AGENTS.md', 'subagent_type', and 'Task tool delegation pattern' that are unlikely to fire for unrelated skills; minimal conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 missing, 3 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository

pantheon-org/tekhne

Path

skills/agentic-harness/opencode-toolkit/design-agents/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.