CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

90%

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

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

An excellent operational skill: fully executable commands, explicit validation checkpoints with a fallback loop, and a clean section structure. The only deductions are minor — slight redundancy between the overview and detail sections, a version-pinned detail outside a deprecation section, and all content inlined in one file.

DimensionReasoningScore

Conciseness

The body is mostly lean operational commands with no padding of concepts Claude already knows, and the env -i rationale is project-specific and justified. Minor trimmable instances remain — the Core Workflow partially repeats later sections, and the time-sensitive "OpenCode 1.17.11" version pin sits outside any deprecated/old-patterns section — matching anchor 4 rather than 5.

4 / 5

Actionability

Every step is fully executable copy-paste bash: npm pack with a temp destination, tarball install and version check, complete opencode.json heredocs, full env -i opencode run invocations with timeout, an rg log-signature search, and a fill-in reporting template. Both the isolated and host-provider common cases are covered, matching anchor 5.

5 / 5

Workflow Clarity

An 8-step numbered workflow carries explicit validation checkpoints: opencode debug config verification with a three-item Confirm checklist, the expected "OK" result, "No matches should appear" for the crash-signature search, and a recovery loop ("If OpenCode needs provider aliases... run a second non-isolated smoke"). This matches anchor 5; the operation is a read-only smoke test so the destructive/batch cap does not apply.

5 / 5

Progressive Disclosure

Well-organized single-file skill with clear sections (Core Workflow, Pack Candidate, Isolated Config, Runtime Smoke, Host-Provider Smoke, Reporting Template) and no nested or dead references — the referenced bundle directories do not exist and no external files are cited. At ~155 lines with everything inlined (e.g., the reporting template and host-provider variant), the under-50-line simple-skill exception does not apply, matching anchor 4 rather than 5.

4 / 5

Total

18

/

20

Passed

Description

87%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 strong description with an explicit what-and-when structure, concrete enumerated triggers, and a highly distinctive niche. Keyword coverage is good though not exhaustive of natural synonyms, and the action side is slightly narrower than the object side.

DimensionReasoningScore

Specificity

The description names the domain and enumerates several concrete validation targets ("packed plugin artifact, release branch, crash fix, OpenCode runtime compatibility, or model-specific smoke test") with only minor coverage gaps. It exceeds anchor 3 (more than 1-2 concrete actions) but the action verbs themselves are limited (test/validate), keeping it below anchor 5.

4 / 5

Completeness

It explicitly answers both "what" ("Test an oh-my-opencode-slim release candidate or bugfix before publishing") and "when" via a concrete "Use when validating..." clause enumerating specific triggers. This matches anchor 5; it is not 4 because the "when" is fully explicit rather than improvable.

5 / 5

Trigger Term Quality

Natural trigger phrases like "release candidate", "smoke test", "crash fix", "release branch", and "before publishing" match what a user would actually say. Coverage is good but not comprehensive — variants like "regression test" or "pre-publish check" are missing, matching anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

The description names the specific project (oh-my-opencode-slim), runtime (OpenCode), and even a specific version (1.17.11), giving it a clear niche with distinct triggers and minimal conflict risk with any generic skill. This clearly matches anchor 5.

5 / 5

Total

18

/

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

alvinunreal/oh-my-opencode-slim

Path

.agents/skills/release-smoke-test/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.