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.
61
52%
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
82%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 covers a clear domain (release coordination) with an explicit 'Use when' trigger clause, which is a strength. However, it lists topics rather than concrete actions—it says it 'coordinates' these things but doesn't specify what concrete steps it performs. The trigger terms are natural and varied, giving good keyword coverage for skill selection.
Suggestions
Replace the topic list with specific concrete actions, e.g., 'Gera changelogs a partir de commits, cria tags de versão, redige release notes, coordena rollout/rollback e comunica mudanças internamente.'
Add boundary clarification to reduce overlap, e.g., 'Não cobre CI/CD pipeline configuration ou git branching strategies.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (release management) and lists several related concepts (versionamento, changelog, release notes, rollout, rollback, comunicacao interna), but these read more like a topic list than concrete actions. It doesn't specify what actions are performed (e.g., 'generates changelogs', 'creates release tags', 'drafts release notes'). | 2 / 3 |
Completeness | Explicitly 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'). The 'Use quando...' clause is present and provides a clear trigger condition. | 3 / 3 |
Trigger Term Quality | Includes a good range of natural keywords users would say: 'release', 'versionamento', 'changelog', 'release notes', 'rollout', 'rollback', 'comunicacao interna', 'empacotamento', 'liberacao'. These are terms a user would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | The release management niche is reasonably distinct, but terms like 'changelog' and 'versionamento' could overlap with skills focused on git workflows, CI/CD pipelines, or documentation generation. The scope is broad enough that it might conflict with more specialized skills in adjacent areas. | 2 / 3 |
Total | 10 / 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 more like a role description or process charter than actionable guidance. It tells Claude what a Release Manager does but never shows how to do it—no changelog format examples, no release note templates, no rollback procedure steps, no concrete commands. The multiple sections (Entradas, Saidas, Checklist, Evidencia) are largely redundant, restating the same deliverables in slightly different framings.
Suggestions
Add a concrete workflow sequence with numbered steps: e.g., 1. Gather approved changes, 2. Generate changelog in specific format, 3. Draft release notes, 4. Define rollback trigger criteria, 5. Validate with checklist, 6. Communicate via specified channels.
Include at least one concrete example of a changelog entry and release note format so Claude knows exactly what output to produce.
Add a rollback procedure with explicit validation checkpoints and decision criteria (e.g., 'If error rate exceeds X% within Y minutes, execute rollback by...').
Consolidate the redundant sections (Saidas Esperadas, Checklist Base, Evidencia de Conclusao) into a single actionable checklist to reduce repetition.
| 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. The content lists inputs, outputs, and checklists but never defines the order of operations, validation checkpoints, or feedback loops. For a release process involving potentially destructive operations (rollout/rollback), the absence of any step-by-step sequence with validation is a significant gap. | 1 / 3 |
Progressive Disclosure | References to external files exist (GLOBAL.md, various policies, templates/release-plan.md) which is good, but the references are not clearly signaled with descriptions of what each contains. The main content itself is thin enough that it doesn't need splitting, but it also doesn't provide enough substance to serve as a useful overview. | 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
e9f6648
- 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.