CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

release-openshell

Pick the latest qualified OpenShell prerelease and tag its commit as stable. Create and qualify a prerelease first when none exists.

Quality

82%

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 dense, executable runbook: copy-paste gh commands for every path (stable promotion, prerelease seeding, next candidate, support branch, retry), explicit pre-promotion gating, and error-recovery instructions for failed publications. It assumes Claude's competence and adds only project-specific knowledge, with only minor room for tightening prose and adding sub-headers for navigation.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence throughout — no explanation of gh, tags, or workflow concepts — and nearly every sentence carries project-specific operational facts ('Release selects the highest-numbered vX.Y.Z-pre.N reachable from that branch...'). A few long sentences and version-specific facts (e.g. 'openshell 0.1.7 is the last core-built wheel') could be tightened or isolated, matching anchor 4 rather than the uniformly lean anchor 5.

4 / 5

Actionability

Commands are copy-paste ready and cover the common cases: 'gh workflow run release.yml --ref main', 'gh workflow run release-prerelease.yml --ref main -f tag=vX.Y.Z-pre.1', and the support-branch example 'gh workflow run release-prerelease.yml --ref release/0.4' with explicit instruction to substitute the real branch. This fully matches anchor 5.

5 / 5

Workflow Clarity

The sequence is explicit (inspect the latest passing prerelease, present the candidate to the maintainer, dispatch Release once approved, watch and report) with hard validation gates — 'Wait for the entire Pre-release run to pass before promoting it' and 'Inspect the selected candidate in the promotion job summary' — and error-recovery loops like 'If qualification passed but publication failed, rerun the failed jobs before promoting the candidate.' Anchor 5's explicit checkpoints and feedback loops are all present.

5 / 5

Progressive Disclosure

There are no bundle files and all content is operational guidance that belongs inline, organized under '# Release OpenShell' and '## Python SDK'. The main flow runs ~75 lines as continuous paragraphs without sub-headers separating promotion, prerelease creation, and edge-case rules — a minor organization gap matching anchor 4, not 3 (nothing clearly belongs in a separate file) and not 5 (an 80+ line body would benefit from clearer internal navigation).

4 / 5

Total

18

/

20

Passed

Description

70%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 uses third person and names several concrete, specific actions in a distinct niche (OpenShell release promotion), so specificity and distinctiveness are strong. However, it entirely lacks a 'when to use' clause, which caps completeness at 3, and its trigger vocabulary omits natural synonyms like 'publish' or 'promote'.

Suggestions

Add an explicit trigger clause, e.g. 'Use when releasing OpenShell, promoting a prerelease to a stable tag, or when the user asks to publish or cut an OpenShell release.'

Include natural trigger synonyms such as 'publish', 'promote', and 'cut a release' alongside 'prerelease' and 'stable' so user phrasing variants match.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'Pick the latest qualified OpenShell prerelease', 'tag its commit as stable', 'Create and qualify a prerelease first' — with only minor coverage gaps (no mention of dispatching workflows or watching/reporting the run). It exceeds the 1–2 actions of anchor 3 but is not comprehensively covering all capabilities for a 5.

4 / 5

Completeness

The 'what' is clear (pick a qualified prerelease and tag it stable; create one if none exists), but there is no 'Use when...' clause or equivalent explicit trigger guidance — 'when none exists' is conditional logic, not usage timing. Per the rubric guideline, a missing explicit trigger caps completeness at 3; it is not 2 because the 'what' is concrete, not vague.

3 / 5

Trigger Term Quality

Includes natural terms users would say — 'prerelease', 'stable', 'tag', 'release' (via prerelease/stable context) — but misses common synonyms like 'publish', 'promote', or 'cut a release'. Good coverage, a few natural terms missing, matching anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

'OpenShell prerelease' and 'tag its commit as stable' define a clear niche with distinct triggers; no other plausible skill would trigger on this description. Matches anchor 5 — minimal conflict risk.

5 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 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

Total

14

/

16

Passed

Repository

NVIDIA/OpenShell

Path

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