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.

72

Quality

88%

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

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.

The body is a tight, executable runbook with concrete commands, explicit validation checkpoints, and clear sequencing. It respects Claude's competence and avoids restating known concepts, with only minor trims possible.

DimensionReasoningScore

Conciseness

Largely lean with copy-paste commands and no padding of concepts Claude already knows; the few explanatory prose lines (e.g. 'Use env -i for the cleanest smoke') earn their place by justifying non-obvious decisions, fitting the efficient-but-trimmable 4 anchor rather than the fully lean 5.

4 / 5

Actionability

Fully executable, copy-paste-ready bash covering pack, install, isolated config, runtime smoke, log search, and host-provider smoke, matching the 5 anchor for concrete commands covering common cases.

5 / 5

Workflow Clarity

Clear numbered Core Workflow sequence with explicit validation checkpoints (verify plugin_origins count, expected 'OK' result, crash-signature log search with 'No matches should appear') and a feedback loop for isolation failures, plus a reporting checklist, matching the 5 anchor.

5 / 5

Progressive Disclosure

Well-organized into clearly signaled sections (Pack Candidate, Isolated Config, Runtime Smoke, Host-Provider Smoke, Reporting Template) with no nested references and all content appropriately inline, fitting the good-structure 4 anchor; no external bundle files exist to warrant a 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.

The description is well-crafted: third-person voice, explicit what-and-when structure, concrete actions, and a distinct niche. It avoids vague fluff and over-claims while covering realistic trigger scenarios.

DimensionReasoningScore

Specificity

Lists several concrete actions (test release candidate, test bugfix, validate packed artifact, release branch, crash fix, runtime compatibility, model-specific smoke test) with only minor coverage gaps, matching the 'several specific actions' anchor rather than the fully comprehensive 5.

4 / 5

Completeness

Explicitly states what it does ('Test an oh-my-opencode-slim release candidate or bugfix before publishing') and when to use it with concrete trigger phrases ('Use when validating...'), matching the 5 anchor that requires both clearly and explicitly.

5 / 5

Trigger Term Quality

Good natural keyword coverage including 'release candidate', 'bugfix', 'packed plugin artifact', 'crash fix', and 'smoke test', with only a few common synonyms missing, fitting the 4 anchor above the 3.

4 / 5

Distinctiveness Conflict Risk

Targets a clear, narrow niche (oh-my-opencode-slim release smoke testing) with highly specific triggers and minimal overlap risk with other skills, matching the 5 anchor.

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.

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.