CtrlK
BlogDocsLog inGet started
Tessl Logo

release-openspec

Use this skill when releasing OpenSpec: audit merged work and changeset coverage, decide whether a catch-up changeset PR is needed, prepare or resume the Changesets Version Packages PR, cut a beta or stable release, verify publishing, and polish GitHub release notes. Also use when asked whether an open release PR is complete, what the next release step is, or to continue a release paused for human approval.

77

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

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.

The content is a well-structured, executable release state machine with strong validation checkpoints and a clean one-level reference. Its only weakness is mild verbosity in the principles/rationale phrasing.

Suggestions

Tighten the 'Principles' bullets to imperative facts, dropping rationale phrasing to recover token budget without losing guidance.

Consider moving the long audit classification list into the references file if it bloats the overview for non-audit invocations.

DimensionReasoningScore

Conciseness

The body is mostly lean and action-oriented with no basic-concept over-explanation, but the 'Principles' section and some rationale-style sentences add tokens that could be trimmed; it sits above the midpoint but not at the leanest anchor.

4 / 5

Actionability

Provides concrete, copy-paste-ready commands with exact flags and field names (e.g., 'gh release list ... --exclude-drafts --exclude-pre-releases', 'pnpm exec changeset status'), covering the common release cases fully.

5 / 5

Workflow Clarity

Sequenced multi-step processes carry explicit validation checkpoints ('Validate before pushing: pnpm exec changeset status', base-to-head Version Packages PR validation, 'Verify all three artifacts independently') plus a 'Handle failures' feedback loop, matching the top anchor.

5 / 5

Progressive Disclosure

A clear overview split into well-organized sections with a single, well-signaled one-level-deep reference to references/release-notes.md (a real file), keeping navigation easy and content appropriately placed.

5 / 5

Total

19

/

20

Passed

Description

100%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 specific, well-triggered, and complete, naming concrete release actions alongside explicit 'when' clauses in third person. It is a strong, low-conflict description.

DimensionReasoningScore

Specificity

Lists multiple concrete release actions ('audit merged work and changeset coverage, decide whether a catch-up changeset PR is needed, prepare or resume the Changesets Version Packages PR, cut a beta or stable release, verify publishing, and polish GitHub release notes'), giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both 'what' (the enumerated release actions) and 'when' (two 'Use this skill when'/'Also use when' clauses with concrete trigger phrases), matching the top anchor.

5 / 5

Trigger Term Quality

Includes natural trigger phrases users would actually say ('Use this skill when releasing OpenSpec', 'Also use when asked whether an open release PR is complete, what the next release step is, or to continue a release paused for human approval'), covering the common ways the request surfaces.

5 / 5

Distinctiveness Conflict Risk

Scoped to a clear niche (releasing OpenSpec) with distinct release-workflow triggers, making overlap with unrelated skills minimal.

5 / 5

Total

20

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Fission-AI/OpenSpec
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.