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

93%

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

92%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 exemplary operational skill: executable commands at every step, explicit validation and approval checkpoints, and well-structured single-file organization with clear one-level-deep references. The only ding is a handful of trimmable explanatory asides.

DimensionReasoningScore

Conciseness

The body is overwhelmingly lean and project-specific (Auto-Tag schedule, train semantics, recovery matrix) with no padding of concepts Claude already knows, but a few asides could be trimmed, e.g. 'The `-c` and `/dev/null` keep `git` from signing the tag and opening an editor'. Minor instances of over-explanation fit the 4 anchor rather than the every-token-earns-its-place 5.

4 / 5

Actionability

Fully executable, copy-paste-ready shell throughout: setup snippets, run lookup commands, candidate preview via a worktree, tag verification, and two ready-to-use Slack post templates with clearly marked placeholders (RUN=<run-id>, NEXT_SHA=<commit>). Commands cover the common cases plus recovery paths, matching the 5 anchor.

5 / 5

Workflow Clarity

Monday steps 1-4 and Tuesday steps 1-6 are clearly sequenced with explicit validation checkpoints ('Only `complete` with `no_unaddressed_breaks` is clean', 'gh run watch <run-id> --exit-status', release asset verification), approval gates before every destructive operation, and a Recovery table providing feedback loops. Destructive operations all have verification, so the workflow-clarity cap does not apply.

5 / 5

Progressive Disclosure

No bundle files exist, and this single-file checklist is appropriately so: a usage table for entry points, Guardrails up front, background, Setup, day-by-day procedures, Recovery, and Related sections make navigation easy, while references (RFC 0014, CI.md, release-version-selection.md, sibling skills) are clearly signaled and one level deep. Nothing that belongs in a separate file is inlined.

5 / 5

Total

19

/

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 action coverage with an explicit trigger-keyword clause that clearly answers both what and when. The only weakness is that several generic release phrases create minor overlap risk with closely related release skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions covering the full rotation - 'checks the pre-release train, triages failures and the compatibility review, and drafts the coordination post' plus 'promotes the qualified pre-release after approval, verifies publication, and starts the next train'. Coverage is comprehensive across both days, not merely several actions with gaps, so it matches the 5 anchor rather than 4.

5 / 5

Completeness

Explicitly answers both what (multi-action checklist description per day) and when (an explicit 'Trigger keywords - ...' clause equivalent to 'Use when...'). Both are concrete and explicit, matching the 5 anchor; the explicit trigger clause avoids the missing-'when' cap.

5 / 5

Trigger Term Quality

Nine natural trigger phrases users would actually say: 'release captain, weekly release, Tuesday release, cut the release, release checklist, pre-release status, release train, start next train, stable release'. Includes synonyms and role-specific variations, matching the comprehensive-coverage anchor; 4 would require missing natural terms, which is not the case.

5 / 5

Distinctiveness Conflict Risk

Clear niche (weekly OpenShell release captain rotation) with distinct triggers like 'release captain', 'release train', and 'start next train', but generic phrases such as 'cut the release', 'stable release', and 'release checklist' could overlap with closely related release-process skills (the bundle itself references a sibling 'release-openshell' skill). Mostly distinct with minor overlap risk fits 4 better than 5.

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

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.