CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

release-management

Prepares a MockServer release by recommending the release version from Semantic Versioning rules and `changelog.md`, checking release readiness, and listing the exact Buildkite release parameters. Use when users say "prepare release", "release version", "run the release pipeline", "which version should we release", or need to verify changelog and secret readiness before triggering the release pipeline.

Quality

89%

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

81%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 runbook: exact commands, named credentials, explicit pass/fail criteria, and genuine feedback loops for every failure mode. Its weaknesses are redundancy — the credential-liveness story is told two to three times — and a monolithic 225-line layout where a credentials/monitoring reference file would reduce token load.

Suggestions

State the liveness-vs-presence rationale (including the 8.0.0 npm incident) once in Readiness Checks and reference it from Required Inputs instead of repeating the anecdote and the preflight-gate description in both sections.

Move the per-credential verdict definitions and required/advisory credential catalog into a references/ file (e.g. references/credentials.md) and keep only the fail/pass decision rule inline in readiness check 5.

Move the verbatim Monitor & Verify URL list into a reference file and keep a one-line pointer plus the rule to substitute <release-version>, cutting ~15 lines of always-loaded URLs.

DimensionReasoningScore

Conciseness

The body is dense with novel repo-specific operational knowledge, but the liveness-vs-presence rationale is repeated: the 8.0.0 npm-token anecdote appears in Required Inputs and again in readiness check 5, and the preflight credential gate is explained in Required Inputs and re-explained in check 5. This matches anchor 3 ('mostly efficient but includes some unnecessary explanation or could be tightened') rather than anchor 4, since the redundancy exceeds minor trimming.

3 / 5

Actionability

Guidance is fully executable and copy-paste ready: exact `bk build create` commands with clearly marked placeholders and the `-e PUBLISH_SNAPSHOT=true` flag, specific script paths (`scripts/release/check-release-credentials.sh`, `scripts/release/check-perf-preflight.sh`), named credentials, and exact verification URLs. This matches anchor 5; it is well above anchor 4's 'minor gaps'.

5 / 5

Workflow Clarity

The process is clearly sequenced (required inputs → ordered version rules 1–4 → six numbered readiness checks → output format) with explicit validation checkpoints and error-recovery feedback loops: builds must end 'passed, not skipped' and be re-created if superseded, red compare steps get a fix/re-run/accept decision path, and UNVERIFIED outcomes name the fault to fix before re-running. Matches anchor 5.

5 / 5

Progressive Disclosure

A single well-sectioned file with clear headers and no nested references, which is good structure (anchor 4). It falls short of anchor 5 because at ~225 lines the inlined credential catalog (~40 lines of verdicts and ARNs) and the verbatim 11-URL Monitor & Verify list are content that could be split into reference files; it stays above anchor 3 because organization and signaling are genuinely clear.

4 / 5

Total

17

/

20

Passed

Description

95%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: it states concrete capabilities tied to named artifacts, gives an explicit 'Use when' clause with multiple natural trigger phrasings, and occupies a distinct niche (MockServer/Buildkite release preparation) with negligible conflict risk. The only weakness is that 'checking release readiness' summarizes rather than enumerates the credential-liveness and perf-gate checks that dominate the skill body.

DimensionReasoningScore

Specificity

Names three concrete actions with mechanisms ('recommending the release version from Semantic Versioning rules and `changelog.md`', 'checking release readiness', 'listing the exact Buildkite release parameters'), matching the 'several specific actions; minor gaps in coverage' anchor. The readiness sub-checks (credential liveness, perf gate) are folded into the generic 'checking release readiness' rather than enumerated, keeping it just below the comprehensive anchor 5.

4 / 5

Completeness

Explicitly answers both 'what' (recommend version from SemVer + changelog, check readiness, list Buildkite parameters) and 'when' ("Use when users say..." with concrete trigger phrases), exactly matching the anchor 5 example pattern. It is clearly above anchor 4, whose 'when' is less specific.

5 / 5

Trigger Term Quality

Quotes natural user utterances in both imperative and question form — "prepare release", "release version", "run the release pipeline", "which version should we release", "verify changelog and secret readiness" — giving comprehensive paraphrase coverage of how users would phrase this need. No common phrasing for this trigger space is missing, so it fits the anchor 5 rather than anchor 4's 'a few natural terms missing'.

5 / 5

Distinctiveness Conflict Risk

"MockServer release", "Buildkite release parameters", and "changelog.md" establish a clear niche with distinct triggers and minimal conflict risk with any generic skill. This matches anchor 5; nothing in the description is broad enough to trigger the wrong skill.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 4 missing, 4 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository

mock-server/mockserver-monorepo

Path

.opencode/skills/release-management/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.