release-manager
Skill para coordenar release, versionamento, changelog, release notes, rollout, rollback e comunicacao interna. Use quando a mudanca estiver pronta para empacotamento e liberacao controlada.
65
56%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/24-release-manager/SKILL.mdQuality
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.
The description effectively identifies its niche (release coordination) and includes an explicit 'Use when' clause with a clear trigger condition. It has strong trigger term coverage with natural keywords. The main weakness is that the capabilities are listed as topic areas rather than concrete actions, making it slightly vague on what specific operations the skill performs.
Suggestions
Replace the topic-listing style with concrete action verbs, e.g., 'Gera changelogs automaticamente, cria tags de versao semantica, redige release notes, planeja rollback e comunica status internamente' instead of just listing the concepts.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (release management) and lists several related concepts (versionamento, changelog, release notes, rollout, rollback, comunicacao interna), but these read more as topic areas than concrete actions. It says 'coordenar' but doesn't specify what concrete steps are performed (e.g., 'generates changelogs', 'creates semantic version tags', 'drafts rollback plans'). | 2 / 3 |
Completeness | The description answers both 'what' (coordenar release, versionamento, changelog, release notes, rollout, rollback, comunicacao interna) and 'when' ('Use quando a mudanca estiver pronta para empacotamento e liberacao controlada'), with an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms a user would say: 'release', 'versionamento', 'changelog', 'release notes', 'rollout', 'rollback', 'comunicacao interna', 'empacotamento', 'liberacao'. These are terms users would naturally use when requesting help with release coordination. | 3 / 3 |
Distinctiveness Conflict Risk | The skill occupies a clear niche around release coordination and deployment lifecycle. The combination of release, versioning, changelog, rollout/rollback, and internal communication is distinctive and unlikely to conflict with other skills like general CI/CD, code review, or documentation skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads as a high-level role description rather than actionable guidance for performing release management. It lacks concrete examples, executable steps, templates, or format specifications that would enable Claude to actually produce release artifacts. The multiple sections (Entradas, Saidas, Checklist, Evidencia) are largely redundant and don't compensate for the absence of a clear workflow.
Suggestions
Add a concrete, sequenced workflow (e.g., 1. Gather approved changes → 2. Generate changelog in specific format → 3. Draft release notes → 4. Define rollback procedure → 5. Validate with checklist → 6. Communicate) with explicit validation checkpoints between steps.
Include at least one concrete example of a changelog entry, release note, and rollback plan format so Claude knows exactly what output to produce.
Consolidate the redundant sections (Saidas Esperadas, Checklist Base, Evidencia de Conclusao) into a single actionable checklist to improve token efficiency.
Add a brief inline example or template snippet for the release plan rather than only pointing to 'templates/release-plan.md', so the skill is useful even without that file loaded.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but contains redundancy across sections (e.g., 'Saidas Esperadas', 'Checklist Base', and 'Evidencia de Conclusao' largely repeat the same information about changelog, release notes, rollout, and rollback). Some sections like 'Quando Nao Usar' state obvious constraints. | 2 / 3 |
Actionability | The skill provides no concrete commands, code, templates, or executable guidance. It describes what should happen at an abstract level ('changelog e release notes curtas', 'plano de rollout e rollback definidos') without showing how to actually produce any of these artifacts. There are no examples of changelog format, release note structure, or rollback procedures. | 1 / 3 |
Workflow Clarity | There is no sequenced workflow for the release process. The content lists checklists and expected outputs but never defines the order of operations, validation checkpoints, or feedback loops. For a multi-step process like release management (which involves destructive/batch operations like rollout), the absence of explicit sequencing and validation steps is a significant gap. | 1 / 3 |
Progressive Disclosure | The skill references external policies and a template ('templates/release-plan.md', multiple policies), which is good progressive disclosure structure. However, the references are not clearly signaled with descriptions of what each contains, and the main content itself lacks enough substance to serve as a useful overview—it's more of a skeleton than a navigable entry point. | 2 / 3 |
Total | 6 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- felvieira/claude-skills-fv
- Commit
d87ad31
- 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.