release

Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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.

A concise, well-sequenced release runbook with explicit verification and safety guardrails appropriate to its destructive nature. Making the CI-watching and version-selection steps more concrete would round out the actionability.

Suggestions

Replace 'watch burrito-release until it finishes' with a concrete command or link for monitoring the workflow run.

Add an explicit command for finding the latest tag (e.g. `git tag --sort=-v:refname | head -1`) so the 'next patch' step is executable rather than descriptive.

Dimension	Reasoning	Score
Conciseness	Lean and efficient throughout — every numbered step and the closing guardrails earn their place with no padding or explanation of concepts Claude already knows.	5 / 5
Actionability	Mostly executable with concrete commands (`make -C elixir all`, the `git tag`/`git push` snippet), but 'watch burrito-release until it finishes' and 'use the next patch after the latest vX.Y.Z tag' remain slightly abstract.	4 / 5
Workflow Clarity	A clear six-step sequence with explicit validation checkpoints (verify the merged mix.exs version, verify build/smoke/release jobs pass) plus destructive-op guardrails against tagging uncommitted revisions or moving published tags.	5 / 5
Progressive Disclosure	A simple under-50-line skill with well-organized numbered sections and no need for external references, satisfying the simple-skill exception for full marks.	5 / 5
	Total	19 / 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 tight, well-constructed description that pairs concrete release actions with an explicit trigger clause and a clearly distinct niche. Slightly broader keyword coverage (e.g. 'publish', 'version bump') would push the trigger-term score to full marks.

Dimension	Reasoning	Score
Specificity	Lists four concrete release actions — 'bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow' — giving comprehensive coverage of the task.	5 / 5
Completeness	Explicitly answers both 'what' (the four release actions) and 'when' via the concrete 'Use when asked to release, tag, or retag Symphony' trigger clause.	5 / 5
Trigger Term Quality	'release, tag, or retag Symphony' are natural user phrases with a synonym pair (tag/retag), but common variations like 'publish', 'cut a release', or 'version bump' are absent.	4 / 5
Distinctiveness Conflict Risk	Scoped to a named product (Symphony) and its Burrito release workflow with distinct triggers, giving it a clear niche with minimal conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: openai/symphony
Path: .codex/skills/release/SKILL.md
Commit: be10a1b

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.