CtrlK
BlogDocsLog inGet started
Tessl Logo

openseo-release-notes

Cut an OpenSEO release — bump the version, draft user-facing release notes from commits since the last tag, run a review + subagent-verification pass, and open a "release: vX.X.X" PR. Use when the user asks to prepare a release, bump the version, or write release notes.

67

Quality

81%

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

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

A well-sequenced, actionable release workflow with a strong verification loop, hindered mainly by inlined curation/style detail that would benefit from a separate exemplar reference file. No bundle files exist, so progressive disclosure is purely section-based.

Suggestions

Move the canonical style exemplar and the curation do/don't list into a references/release-notes-style.md and link to it, keeping SKILL.md a lean overview (improves progressive_disclosure and conciseness).

Add a concrete tie-breaker command or ordering rule for "when torn between including and cutting" so the curation step is fully deterministic.

Add an explicit re-validation step after applying verified review comments (e.g. re-run the reviewer against the revised draft) to close the verification feedback loop.

DimensionReasoningScore

Conciseness

The body is densely operational and assumes Claude's competence (git/gh commands, no basic-concept padding), but the multi-paragraph curation rules and negative-list sub-bullets could be trimmed without losing load-bearing detail.

4 / 5

Actionability

Concrete, runnable commands (git tag, git log, gh pr view, gh release create) and exact formatting rules make it largely executable; gaps remain where steps reference judgement ("cut aggressively", "when torn") without a concrete tie-breaker command.

4 / 5

Workflow Clarity

A clear numbered 5-step sequence with an explicit review+verify feedback loop (spawn reviewer, adversarial verification subagents, apply only verified comments), but the verification step lacks a concrete re-check after applying fixes.

4 / 5

Progressive Disclosure

Well-organized sections, but it is a single monolithic SKILL.md with no bundle files (references/scripts/assets absent) and no one-level-deep references; the extensive style exemplar guidance is fully inlined rather than split into a reference file.

3 / 5

Total

15

/

20

Passed

Description

92%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, specific description that clearly states both the capabilities and the triggering user requests in third person. Minor additional trigger synonyms would round it out, but it is already comprehensive.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "bump the version", "draft user-facing release notes from commits since the last tag", "run a review + subagent-verification pass", and "open a 'release: vX.X.X' PR" — giving comprehensive coverage of the skill's behavior.

5 / 5

Completeness

Explicitly answers both what (bump version, draft notes, review+verify, open PR) and when ("Use when the user asks to prepare a release, bump the version, or write release notes") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger phrases like "prepare a release", "bump the version", and "write release notes" are present, but a few common variations (e.g. "cut a release", "ship a release") and synonyms are not covered.

4 / 5

Distinctiveness Conflict Risk

The OpenSEO release-cutting niche with a 'release: vX.X.X' PR deliverable is highly specific and unlikely to trigger for unrelated skills.

5 / 5

Total

19

/

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.

Validation14 / 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
every-app/open-seo
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.