CtrlK
BlogDocsLog inGet started
Tessl Logo

release-smoke-test

Test an oh-my-opencode-slim release candidate or bugfix before publishing. Use when validating a packed plugin artifact, release branch, crash fix, OpenCode runtime compatibility, or model-specific smoke test such as OpenCode 1.17.11 message transform regressions.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

A tight, executable smoke-test procedure with clear sequencing, built-in validation checkpoints, and a reporting template, organized into well-signaled sections without padding.

DimensionReasoningScore

Conciseness

Lean and assumes competence: no exposition of basic concepts, just executable setup, config, and verification commands where every token earns its place.

3 / 3

Actionability

Fully executable copy-paste bash with exact paths, env invocations, and a concrete ripgrep signature-search command rather than pseudocode.

3 / 3

Workflow Clarity

Numbered core workflow plus explicit validation checkpoints ('plugin_origins has exactly one entry', 'No matches should appear') and a reporting template, with feedback guidance for isolation failures.

3 / 3

Progressive Disclosure

Self-contained with clearly labeled sections (Pack Candidate, Isolated Config, Runtime Smoke, Reporting Template); no bundle files are present or needed, and navigation is straightforward.

3 / 3

Total

12

/

12

Passed

Description

100%

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 highly specific, third-person description with an explicit 'Use when' trigger clause and concrete validation targets, leaving little ambiguity about scope or activation.

DimensionReasoningScore

Specificity

Lists several concrete actions and targets ('validating a packed plugin artifact, release branch, crash fix, OpenCode runtime compatibility, or model-specific smoke test'), matching the multi-specific-action anchor rather than the partial score-2 example.

3 / 3

Completeness

Explicitly states what ('Test an oh-my-opencode-slim release candidate or bugfix before publishing') and when via an explicit 'Use when' clause with concrete triggers.

3 / 3

Trigger Term Quality

Natural terms a user would say ('release candidate', 'bugfix', 'before publishing', 'crash fix', 'smoke test', 'release branch') are well covered; not just technical jargon.

3 / 3

Distinctiveness Conflict Risk

Narrowly scoped to a named plugin and specific OpenCode version regressions, with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
alvinunreal/oh-my-opencode-slim
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.