CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

publish

Publish oh-my-opencode to npm by triggering the GitHub Actions publish workflow and verifying its artifacts. Ship-only: never runs pre-publish-review or re-reviews merged code unless the user explicitly asks. Argument: <patch|minor|major|explicit-semver>. Triggers: publish, release, deploy, npm publish.

Quality

83%

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

70%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 an exceptionally actionable, well-sequenced release runbook with validation at every stage — top marks for actionability and workflow clarity. Its weaknesses are redundancy (the completion contract and Discord mandate are repeated across four CRITICAL sections) and a total absence of progressive disclosure: all 470 lines live inline with no reference files, including time-sensitive details that will drift.

Suggestions

Collapse the four CRITICAL sections into a single completion-contract section (trigger-to-verification checklist with the failure policy), and let the individual steps carry their own instructions instead of restating the contract at each layer.

Move the Step 6 release-summary style guide (rules, good/bad examples, 'LAST RELEASE BEFORE THE OMO NATIVE CLI PUBLIC RELEASE' heading) and the Step 7.5 Discord template into a references/ file (e.g. references/release-notes.md), keeping only the command and the pointer inline.

Move volatile details — the release bot ID, Discord channel ID, and the '~30 min' stage timeline derived from recent runs — into a single reference file or variables block so they can be updated without touching the core workflow.

DimensionReasoningScore

Conciseness

The body is noticeably padded: four separate CRITICAL sections ("PUBLISH IS SHIP-ONLY", "THREE RELEASE SURFACES", "DISCORD TOO", "NO EARLY TURN-END AFTER TRIGGER") restate the same completion contract, and phrases like "A skipped Discord step is a workflow failure" and "DO NOT stop after creating the GitHub release" appear verbatim in multiple sections. It also embeds time-sensitive details (hard-coded bot/channel IDs, "~30 min total" from "recent real runs") that will drift. This matches anchor 2 (several unnecessary or padded sections) rather than anchor 3 (mostly efficient with some trimming possible).

2 / 5

Actionability

Every step is copy-paste executable: `gh workflow run publish.yml --ref dev -f "bump=${RELEASE_INPUT}"` with run-URL validation, `gh run view "${RUN_ID}" --json status,conclusion,jobs --jq ...`, `npm view oh-my-opencode version`, `agent-discordbot message send 1454708427392680067 ...`, plus a concrete Discord message template and a literal TodoWrite list. This fully matches the anchor-5 copy-paste-ready standard with common cases covered.

5 / 5

Workflow Clarity

Steps 0–9 are explicitly sequenced with validation checkpoints at every surface (release existence via `gh release view`, npm version comparison, platform binary spot-checks, Codex metadata stamp) and a five-item completion checklist. Error handling is specified with a feedback path (poll while drafting, `gh run view --log-failed` → report → stop; report external failures and continue remaining steps), matching anchor 5 including feedback loops and a checklist.

5 / 5

Progressive Disclosure

There are no references/, scripts/, or assets/ directories — the entire ~470-line workflow is inline in SKILL.md. Header structure is good and navigable (so above anchor 2), but content that clearly belongs in separate files is inlined, such as the Step 6 release-summary style guide with good/bad examples, the Discord message template, and the timeline table. This matches anchor 3 (some structure, content that should be separate is inline, no clearly signaled references).

3 / 5

Total

15

/

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 strong: third person, concrete about what it does and when to trigger it, with explicit trigger terms and a clear negative boundary that prevents mis-triggering against review skills. The only gap is that it undersells the full workflow (release notes, Discord, multi-package verification) that the body defines as mandatory.

DimensionReasoningScore

Specificity

"Publish oh-my-opencode to npm by triggering the GitHub Actions publish workflow and verifying its artifacts" names several concrete actions (npm publish, workflow trigger, artifact verification) plus an explicit boundary ("never runs pre-publish-review or re-reviews merged code"), but omits major workflow surfaces the body treats as core (release notes drafting, Discord announcement), so it is not comprehensive.

4 / 5

Completeness

The 'what' is explicit ("Publish oh-my-opencode to npm by triggering the GitHub Actions publish workflow and verifying its artifacts") and the 'when' is explicit with concrete trigger phrases ("Triggers: publish, release, deploy, npm publish"), plus argument guidance. Both questions are answered clearly and explicitly, matching the anchor-5 example structure.

5 / 5

Trigger Term Quality

"Triggers: publish, release, deploy, npm publish" gives good natural keyword coverage, but misses common variations users would say such as "ship", "cut a release", "version bump", or "announce". It sits above anchor 3 (good coverage, a few terms missing) but below anchor 5 (no synonym-level coverage).

4 / 5

Distinctiveness Conflict Risk

The description names the specific package ("oh-my-opencode"), its specific mechanism (GitHub Actions publish workflow), and an explicit negative boundary ("never runs pre-publish-review or re-reviews merged code unless the user explicitly asks"), giving it a clear niche with minimal conflict risk against generic review or deploy skills.

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

code-yeongyu/oh-my-openagent

Path

.agents/skills/publish/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.