CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

changelog-management

Gerenciamento obrigatório de CHANGELOG e versionamento seguindo Keep a Changelog e Semantic Versioning em todos os projetos.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/workflow/changelog/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable — real templates, real git commands, a sequenced workflow, and a checklist — but it is padded with concepts Claude already knows (SemVer mechanics, Keep a Changelog categories), duplicated templates and release procedures, and an unrelated token-security section. As a single ~250-line file it would benefit substantially from deduplication and trimming.

Suggestions

Delete the Semantic Versioning explanation/examples and the per-category definitions (Claude knows both standards; links to semver.org and keepachangelog.com suffice), cutting the body roughly in half.

Keep the CHANGELOG template in one place only and merge the duplicated release procedures ("Workflow Obrigatório" step 4 and "Releases") into a single section.

Remove the token/secret-security section (Notion `ntn_` greps, placeholder tokens) — it is unrelated to changelog management — or move it to a separate reference file if it must be kept.

DimensionReasoningScore

Conciseness

Noticeably verbose: it fully explains Semantic Versioning (MAJOR/MINOR/PATCH with worked examples) and Keep a Changelog category definitions — concepts Claude already knows — repeats the identical CHANGELOG template in both "Formato obrigatório" and "Template Inicial", duplicates the release process in "Workflow Obrigatório" and "Releases", and includes an off-topic token-security section (greps for Notion `ntn_` tokens) unrelated to changelog management. Clearly anchor 2; not 3 because the unnecessary material is substantial rather than incidental.

2 / 5

Actionability

Guidance is mostly executable: a copy-paste CHANGELOG template, concrete git commit/tag/push commands, a realistic example [Unreleased] entry, a pre-commit token check, and a checklist. Not 5 because a few steps remain vague, e.g. "Atualizar número de versão em documentação (se aplicável)".

4 / 5

Workflow Clarity

The workflow is clearly sequenced (antes de fazer mudanças → durante → antes de commitar → ao criar release) with verification checkpoints ("Verificar se todas as mudanças estão no CHANGELOG") and a closing checklist. Not 5 because there is no explicit validate→fix→re-verify feedback loop; the destructive/batch cap does not apply since changelog edits are neither destructive nor batch.

4 / 5

Progressive Disclosure

Sections are well-organized with clear headers and navigation, but ~250 lines sit in a single file with the template duplicated, the release flow stated twice, and off-topic security content inlined — material that should be trimmed or split. Fits anchor 3; not 4 given the redundancy, not 2 since structure and signposting are genuinely clear.

3 / 5

Total

13

/

20

Passed

Description

53%Weight 40%Scale 1-5

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 identifies a clear niche (CHANGELOG and versioning per Keep a Changelog and SemVer) but reads as a policy statement rather than a capability-and-trigger description. It lacks concrete action verbs and any explicit "use when" guidance, and misses natural trigger terms like "release" and "release notes" that live only in a non-standard frontmatter field.

Suggestions

Rewrite as concrete third-person actions, e.g. "Creates and updates CHANGELOG.md entries, categorizes changes (Added/Changed/Fixed/...), and prepares versioned releases following Keep a Changelog and Semantic Versioning."

Add an explicit trigger clause: "Use when the user mentions changelogs, releases, version bumps, release notes, or asks what changed in a project."

Fold the natural keywords from the `triggers` field (release, changes, updates, tags) into the description itself so trigger terms are discoverable where agents actually read them.

DimensionReasoningScore

Specificity

Names the domain precisely ("CHANGELOG e versionamento") plus the governing standards ("Keep a Changelog e Semantic Versioning"), but lists no concrete actions such as creating entries, categorizing changes, or cutting releases. Matches anchor 3 (domain + some concrete detail, not comprehensive); below anchor 4 because no specific actions are enumerated.

3 / 5

Completeness

The "what" is reasonably clear (mandatory CHANGELOG and versioning management per Keep a Changelog/SemVer), but "when" is only the scope claim "em todos os projetos" — there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Includes "CHANGELOG", "versionamento" and both standard names, but omits the natural release-family terms users would say ("release", "release notes", "version bump"), which appear only in the separate non-standard `triggers` frontmatter field. Fits anchor 3 (relevant keywords, missing common variations); not 4 because a core term for this domain is absent from the description itself.

3 / 5

Distinctiveness Conflict Risk

The CHANGELOG/versioning niche with named standards is mostly distinct and unlikely to trigger the wrong skill. Not 5 because "versionamento" and release-adjacent work overlap mildly with generic git-release or commit-message skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

fernandezbaptiste/cursor-multiagent-system

Path

skills/workflow/changelog/SKILL.md

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.