release
Worktrunk release workflow. Use when user asks to "do a release", "release a new version", "cut a release", or wants to publish a new version to crates.io and GitHub.
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description with excellent trigger terms and completeness. Its main weakness is that it could be more specific about the concrete actions performed during the release workflow (e.g., version bumping, tagging, changelog generation). The distinctiveness is strong due to the project-specific naming and platform references.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Bumps version numbers, creates git tags, publishes crates to crates.io, and creates GitHub releases' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('release workflow') and mentions publishing to crates.io and GitHub, but doesn't list the specific concrete steps involved (e.g., bumping version numbers, creating tags, running tests, generating changelogs). It's more of a summary than a detailed capability list. | 2 / 3 |
Completeness | Clearly answers both 'what' (Worktrunk release workflow, publishing to crates.io and GitHub) and 'when' (explicit 'Use when' clause with multiple trigger phrases). The when clause is explicit and well-defined. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger phrases: 'do a release', 'release a new version', 'cut a release', 'publish a new version', 'crates.io', 'GitHub'. These are exactly the phrases a user would naturally say when requesting this workflow. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — 'Worktrunk release workflow' is project-specific, and the combination of crates.io + GitHub publishing with release-specific trigger terms creates a clear niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a highly actionable and well-sequenced release workflow with excellent concrete commands and validation checkpoints throughout. Its main weakness is length — the changelog section alone is longer than many entire skills, and the content would benefit from being split across files with clear references. The skill demonstrates strong project-specific knowledge that Claude genuinely needs, though some sections (like the subagent prompt template) could be more concise.
Suggestions
Extract the CHANGELOG review section (including contributor credits, issue reporter credits, and verification) into a separate CHANGELOG_GUIDE.md and reference it with a one-line link from the main workflow.
Add a quick-reference summary at the top listing just the 12 steps as a numbered checklist (one line each) before the detailed explanations, so Claude can orient quickly on repeat uses.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long (~200+ lines) with substantial detail on changelog verification, contributor crediting, and issue reporter crediting. While much of this is project-specific knowledge Claude wouldn't have, the subagent prompt template and extensive explanation of when to credit could be tightened. The changelog section dominates the skill and could benefit from being split into a separate file. | 2 / 3 |
Actionability | Nearly every step includes exact, copy-paste-ready commands (cargo release, git commands, gh commands). The troubleshooting section provides concrete recovery commands. The subagent prompt template is fully specified. Very little is left to interpretation. | 3 / 3 |
Workflow Clarity | The 12-step workflow is clearly sequenced with explicit validation checkpoints (run tests first, semver-checks before bump, mandatory changelog verification via subagent, user confirmation before proceeding). The reset-and-recommit pattern in steps 7-9 is well-explained with rationale. Error recovery is addressed in troubleshooting. | 3 / 3 |
Progressive Disclosure | The skill is monolithic — all content is inline in a single file. The extensive changelog guidance (credit contributors, credit issue reporters, link docs, mandatory verification) could be split into a separate CHANGELOG_GUIDE.md with a brief reference from the main workflow. The skill would benefit from a quick-reference summary at the top with detailed sections linked separately. | 2 / 3 |
Total | 10 / 12 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 — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
- Repository
- max-sixty/worktrunk
- Commit
a1de9c7
- 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.