CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

code-mate-opencode

Run OpenCode non-interactively for coding tasks. Use when the user asks to delegate work to OpenCode.

Quality

83%

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

92%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 tight, well-structured, instruction-only skill: it specifies the exact command, pre-flight validation, failure conditions, and safe permission/authentication policies with almost no wasted tokens. The only notable gap is that the JSON event stream the skill requires Claude to parse is never exemplified.

DimensionReasoningScore

Conciseness

The body is lean and operational throughout — "set a finite timeout, normally 10 minutes", "Do not add `--auto` merely to avoid a denied permission" — with zero concept explanations or padding; every token earns its place.

5 / 5

Actionability

Gives the copy-paste-ready command "opencode run \"<prompt>\" --format json" and the pre-flight check "command -v opencode", but instructs Claude to "Parse stdout as a JSON event stream and treat an error event ... as failure" without showing the event schema, a minor gap.

4 / 5

Workflow Clarity

Clear numbered sequence with a pre-flight validation step ("Check availability with command -v opencode"), explicit failure conditions ("error event or nonzero exit"), and defined fallback behavior ("stop and ask the user"); the single action is unambiguous, and the skill is not destructive or batch (workspace changes are explicitly gated), so no validation cap applies.

5 / 5

Progressive Disclosure

The skill is under 50 lines, self-contained with no bundle files, and organized into well-signaled sections ("Run", "Authentication And Permissions"), which per the rubric's simple-skill guideline earns full credit.

5 / 5

Total

19

/

20

Passed

Description

66%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.

A serviceable description that answers both what and when in third person with a named, distinctive tool. Its weaknesses are thin trigger coverage (one phrasing) and a single-action 'what' that undersells the skill's capabilities.

Suggestions

Add one or two more concrete actions to the 'what' clause (e.g., "Run OpenCode non-interactively for coding tasks such as analyzing failing tests, reviewing code, or making edits, then summarize the results").

Broaden the trigger clause with natural variations: "Use when the user asks to delegate work to OpenCode, mentions OpenCode, or wants a coding task run via opencode run".

Mention the non-interactive/JSON-output nature as a trigger cue (e.g., "...or asks for OpenCode results as JSON") so users phrasing the request around automation also match.

DimensionReasoningScore

Specificity

"Run OpenCode non-interactively for coding tasks" names the domain and one concrete action, matching the anchor for 1-2 concrete actions without comprehensive coverage; it does not list the several specific actions required for anchor 4.

3 / 5

Completeness

Both parts are present — what: "Run OpenCode non-interactively for coding tasks"; when: "Use when the user asks to delegate work to OpenCode" — but the 'when' is a single clause that could be more explicit with additional trigger variations, so it falls short of the anchor requiring multiple concrete trigger phrases.

4 / 5

Trigger Term Quality

Relevant keywords are limited to "OpenCode" and "delegate work"; common natural variations users would say ("run OpenCode", "ask OpenCode", "have OpenCode fix...") are missing, matching the some-keywords-but-missing-synonyms anchor rather than good coverage.

3 / 5

Distinctiveness Conflict Risk

"OpenCode" is a specific named tool and the delegation trigger is distinct, giving the skill a clear niche with minimal risk of triggering for the wrong skill; it does not sit between anchors.

5 / 5

Total

15

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

CherryHQ/cherry-studio

Path

resources/code-cli-skills/code-mate-opencode/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.