release-manager
Specialized release management for morphir-dotnet. Use when user asks to prepare releases, execute releases, monitor deployments, validate releases, resume failed releases, update changelog, create release notes, or manage release workflow. Triggers include "release", "deploy", "publish", "changelog", "version", "release notes", "what's new".
64
77%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/release-manager/SKILL.mdQuality
Discovery
100%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 strong skill description that clearly defines its scope (morphir-dotnet release management), lists specific concrete actions, and provides explicit trigger guidance with both a 'Use when' clause and a 'Triggers include' list. It uses proper third-person voice throughout and is concise without unnecessary padding.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: prepare releases, execute releases, monitor deployments, validate releases, resume failed releases, update changelog, create release notes, and manage release workflow. | 3 / 3 |
Completeness | Clearly answers both 'what' (specialized release management for morphir-dotnet with specific actions listed) and 'when' (explicit 'Use when' clause plus a 'Triggers include' list with natural keywords). | 3 / 3 |
Trigger Term Quality | Includes a comprehensive set of natural trigger terms users would actually say: 'release', 'deploy', 'publish', 'changelog', 'version', 'release notes', 'what's new'. These cover common variations well. | 3 / 3 |
Distinctiveness Conflict Risk | Scoped specifically to 'morphir-dotnet' release management, which is a very clear niche. The combination of project-specific context and release-focused triggers makes it highly unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
55%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is extremely comprehensive and actionable with excellent workflow clarity, concrete commands, and well-structured release playbooks with validation checkpoints. However, it is massively over-length for a single SKILL.md file — it should serve as a concise overview pointing to separate files for playbooks, script documentation, troubleshooting, and best practices. The verbosity and lack of progressive disclosure severely undermine its effectiveness as a context-window-friendly skill.
Suggestions
Split into multiple files: move each playbook (standard, hotfix, pre-release, recovery) into separate referenced markdown files, and keep only a summary table with links in SKILL.md
Move automation script documentation (prepare-release.fsx, monitor-release.fsx, etc.) into a separate SCRIPTS.md reference file — the main skill only needs to mention which script to use at each step
Remove generic best practices ('Stay calm', 'Never rush', 'Document everything') and explanations of well-known concepts (semantic versioning rules, Keep a Changelog format) that Claude already knows
Move the troubleshooting section and continuous improvement/feedback system into separate referenced files to reduce the main skill to under 200 lines
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~800+ lines. Massive amounts of content that could be split into referenced files. Explains concepts Claude already knows (semantic versioning rules, what a changelog is, basic git commands). Best practices sections are generic advice ('Stay calm', 'Never rush') that waste tokens. The continuous improvement section alone is enormous and largely aspirational rather than actionable. | 1 / 3 |
Actionability | Provides concrete, executable commands throughout — gh workflow run, dotnet fsi scripts with specific flags, git commands with exact arguments, NuGet queries. Templates include copy-paste ready markdown. Script usage sections include specific flags, output descriptions, and exit codes. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflows with explicit phases, time estimates, validation checkpoints, and feedback loops. The standard release playbook has 5 clearly sequenced phases with numbered steps. Recovery playbook includes a decision table for resumable vs non-resumable failures. Checklists are provided for verification steps. The PR workflow explicitly requires waiting for checks before proceeding. | 3 / 3 |
Progressive Disclosure | Monolithic wall of text with everything inlined into a single massive file. References scripts (prepare-release.fsx, monitor-release.fsx, etc.) and templates but no bundle files are provided. Content like the 4 separate playbooks, automation script documentation, troubleshooting guide, and best practices should each be in separate referenced files. The skill tries to be both an overview and a complete reference manual simultaneously. | 1 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (1234 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- finos/morphir-dotnet
- Commit
7c0c06d
- 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.