CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

release-captain

Run the weekly OpenShell release captain checklist. Monday checks the pre-release train, triages failures and the compatibility review, and drafts the coordination post. Tuesday promotes the qualified pre-release after approval, verifies publication, and starts the next train. Trigger keywords - release captain, weekly release, Tuesday release, cut the release, release checklist, pre-release status, release train, start next train, stable release.

Quality

96%

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

Excellent operational skill: fully executable commands, a clearly sequenced two-day workflow with explicit approval and verification checkpoints, and lean project-specific content. Structure and one-level-deep external references make it easy to navigate with nothing inlined that belongs elsewhere.

DimensionReasoningScore

Conciseness

The body is dense with project-specific operational detail and never explains concepts Claude already knows; even the one flag aside ('The `-c` and `/dev/null` keep `git` from signing the tag and opening an editor') covers a non-obvious incantation and earns its tokens, matching the lean/efficient anchor.

5 / 5

Actionability

Every step is backed by copy-paste-ready shell with defined placeholders (RUN=<run-id>, TAG=vX.Y.Z-pre.N, PREV, NEXT_SHA), concrete gh/git/jq commands, and fill-in post templates, covering the common cases including failure paths.

5 / 5

Workflow Clarity

Monday steps 1-4 and Tuesday steps 1-6 are numbered, cross-referenced, and gated by explicit approval checkpoints ('with the exact command and target SHA'), with a verification step (gh run watch --exit-status, release assets, PyPI) and a Recovery table mapping symptoms to actions as feedback loops.

5 / 5

Progressive Disclosure

The skill is a single cohesive checklist with no bundle files to split; sections are clearly organized (usage table, guardrails, background, setup, day-by-day steps, recovery) and deeper material (RFC 0014, release-version-selection, CI.md, related skills) is linked one level deep and clearly signaled in the Related section.

5 / 5

Total

20

/

20

Passed

Description

96%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: concrete day-by-day capabilities, explicit trigger guidance, and a clear named niche. The only weakness is overlap risk with the related release-openshell skill on generic release-phrasing triggers.

Suggestions

Qualify the generic trigger phrases toward the captain role (e.g. 'release captain checklist', 'ship the weekly OpenShell release') so they do not collide with the related release-openshell skill's triggers.

State the scope boundary versus release-openshell in one clause (e.g. 'covers the full weekly captain rotation including the Monday pre-flight and next-train startup'), keeping it distinct from the short Tuesday procedure.

Consider dropping the least distinctive keyword ('stable release') in favor of one a captain would more naturally say, such as 'promote the pre-release'.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions covering both days of the duty ('checks the pre-release train', 'triages failures and the compatibility review', 'drafts the coordination post', 'promotes the qualified pre-release after approval', 'verifies publication', 'starts the next train'), matching the comprehensive-coverage anchor rather than the minor-gaps anchor below.

5 / 5

Completeness

It explicitly answers 'what' ('Run the weekly OpenShell release captain checklist' with per-day duties) and 'when' via a dedicated trigger-keyword clause, so both halves are concrete and explicit.

5 / 5

Trigger Term Quality

Nine natural trigger phrases ('release captain, weekly release, Tuesday release, cut the release, release checklist, pre-release status, release train, start next train, stable release') include verb phrasings a user would actually say, covering synonyms and role variations comprehensively.

5 / 5

Distinctiveness Conflict Risk

The 'OpenShell' niche and role-specific terms ('release captain', 'start next train', 'pre-release status') are distinct, but generic phrases like 'cut the release', 'release checklist', and 'stable release' would equally trigger the closely related 'release-openshell' skill that covers the same Tuesday procedure, fitting the minor-overlap anchor rather than the minimal-conflict one.

4 / 5

Total

19

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

relative_links

Relative link issues: 2 suspicious

Warning

Total

13

/

16

Passed

Repository

NVIDIA/OpenShell

Path

.agents/skills/release-captain/SKILL.md

Revision

c4688aa

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill