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.

Quality

56%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/24-release-manager/SKILL.md

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 description has strong trigger term coverage and completeness with an explicit 'Use when' clause. The main weakness is that it lists topic areas rather than specific concrete actions (e.g., 'generate changelog entries' vs just 'changelog'). The Portuguese language is appropriate if this is for a Portuguese-speaking context.

Suggestions

Convert topic nouns into action verbs - instead of 'changelog, release notes', use 'generate changelogs, write release notes, manage version numbers'

Add more specific actions like 'create release branches', 'tag versions', 'draft release communications'

Dimension	Reasoning	Score
Specificity	Names the domain (release coordination) and lists several related concepts (versionamento, changelog, release notes, rollout, rollback, comunicacao interna), but these are more like topic areas than concrete actions. Missing specific verbs describing what actions are performed.	2 / 3
Completeness	Clearly answers both what (coordenar release, versionamento, changelog, etc.) and when ('Use quando a mudanca estiver pronta para empacotamento e liberacao controlada'). Has explicit 'Use when' clause with clear trigger condition.	3 / 3
Trigger Term Quality	Good coverage of natural terms users would say: 'release', 'versionamento', 'changelog', 'release notes', 'rollout', 'rollback'. These are terms developers naturally use when discussing release processes.	3 / 3
Distinctiveness Conflict Risk	Clear niche focused specifically on release coordination and deployment processes. The combination of release-specific terms (changelog, rollout, rollback, release notes) creates a distinct trigger profile unlikely to conflict with general coding 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 functions more as a role description than actionable guidance. It clearly defines scope (when to use/not use) but fails to provide concrete steps, examples, or templates for creating releases, changelogs, or rollback plans. Claude would need to infer most of the actual work from general knowledge rather than skill-specific instruction.

Suggestions

Add a concrete example of a changelog entry and release notes format that matches the project's conventions

Include a numbered workflow sequence: 1. Gather approved changes → 2. Draft changelog → 3. Create release notes → 4. Define rollout stages → 5. Document rollback procedure → 6. Communicate

Provide a minimal release plan template inline or show what templates/release-plan.md should contain

Add validation checkpoints (e.g., 'Verify all PRs in release have passing CI before proceeding')

Dimension	Reasoning	Score
Conciseness	The content is reasonably efficient but includes some redundancy between sections (Checklist Base and Evidencia de Conclusao overlap significantly). The governance references add overhead without actionable value.	2 / 3
Actionability	The skill provides no concrete examples, templates, commands, or executable guidance. It describes what should happen ('changelog e release notes curtas') without showing how to create them or what format to use.	1 / 3
Workflow Clarity	No clear sequence of steps is provided. The skill lists outputs and checklists but doesn't explain the process to achieve them. Missing validation checkpoints for release operations which are inherently risky.	1 / 3
Progressive Disclosure	References to external files (policies, templates) are present and one-level deep, but the skill itself lacks a quick-start section and the references are not clearly signaled with descriptions of what each contains.	2 / 3
	Total	6 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: felvieira/claude-skills-fv
Commit: 524725e

Reviewed: 5 days 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.