update-change-log

To synchronize CHANGELOG.md with changes made last week (mon - sun)

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/update-change-log/SKILL.md

Quality

Content

63%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 skill delivers a well-sequenced, actionable CHANGELOG-sync workflow with real commands, templates, and validation gates. Its main weakness is conciseness and structure: large editorial style-guide sections are inlined where extraction to a reference file would slim the body.

Suggestions

Move Voice & Tone and Writing Constraints (banned-word lists, mechanical-writing test, review tests) into a references/STYLE.md file and link to it from the body to cut tokens.

Tighten the editorial ban-lists into a compact checklist; remove guidance Claude already applies by default (e.g., 'no filler', 'bullet over paragraph').

Pre-fill the weekly and Slack templates with a worked example (real dates and slug) so they are copy-paste ready rather than placeholder-only.

Dimension	Reasoning	Score
Conciseness	The workflow body is mostly efficient with concrete commands, but extended editorial sections (banned-word/AI-speak lists, 'One good joke per few documents', the mechanical-writing and review-tests sub-sections) restate style principles Claude already knows and could be tightened or extracted.	3 / 5
Actionability	It gives executable guidance — a copy-paste whole-week git diff command, weekly and Slack templates with a real deep-link slug example, and a concrete channel ID — with only minor gaps (e.g., the template placeholders [DD.MM] are not pre-filled).	4 / 5
Workflow Clarity	The 0-5 operating sequence is clearly ordered with explicit checkpoints (verify the diff window via author/committer-date counts, explicit HITL approval before applying, duplicate-heading grep), fitting the 'clear sequence with most checkpoints present' anchor just below the fully validated 5.	4 / 5
Progressive Disclosure	No bundle files exist and the ~190-line body is a single monolithic doc; sections are well-headed, but reusable editorial material (Voice & Tone, Writing Constraints) that could live in a reference file is inlined, matching the 'some structure but could be better organized' anchor.	3 / 5
	Total	14 / 20 Passed

Description

48%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 names a specific, distinguishable domain and timeframe but offers only one generic action and omits any explicit 'Use when' trigger guidance. Adding concrete operations and a trigger clause would lift the completeness and specificity anchors.

Suggestions

List 2-3 concrete actions (e.g., 'diff last week's git changes, draft weekly CHANGELOG entries, propose Slack announcement') instead of the single verb 'synchronize'.

Add an explicit 'Use when...' clause naming natural triggers (e.g., 'Use when updating CHANGELOG.md for last week's shipped work or drafting the weekly release note').

Include natural synonyms a user would say ('changelog', 'release notes', 'weekly update') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('CHANGELOG.md', 'changes made last week') but the only action is the generic 'synchronize', with no enumeration of concrete operations, matching the 'names the domain but actions are minimal or generic' anchor rather than the multi-action anchor at 3.	2 / 5
Completeness	It states a clear 'what' (synchronize CHANGELOG.md with last week's changes) but provides no 'when'/'Use when...' trigger clause, so per the missing-trigger-guidance cap it cannot exceed 3.	3 / 5
Trigger Term Quality	It surfaces relevant keywords ('CHANGELOG.md', 'changes', 'last week', 'mon - sun') but misses natural synonyms and phrasings a user would actually say ('update the changelog', 'changelog entry', 'release notes'), fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The CHANGELOG.md niche is mostly distinct with minimal conflict risk, but the broad verb 'synchronize ... changes' leaves minor overlap with general git/doc-maintenance skills, placing it just below the fully distinct anchor at 5.	4 / 5
	Total	12 / 20 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: griddynamics/rosetta
Path: .claude/skills/update-change-log/SKILL.md
Commit: 044d86c

Reviewed: 21 hours 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.