CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

update-change-log

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

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

70%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 a highly actionable, well-sequenced workflow with concrete commands, templates, validation checkpoints, and HITL feedback loops. Its main weakness is verbosity: editorial rules are duplicated across multiple sections and a long lessons-learned log is inlined in a single monolithic file with no reference files.

Suggestions

Deduplicate editorial rules: value-before-mechanism and anti-AI-slop constraints appear in 'Goal', 'Core principle', 'Writing Constraints', and 'Mechanical-writing test'; state each rule once in a single section.

Move the 'Lessons learned' log to a separate reference file (or trim it to durable rules) so the SKILL.md body stays lean and scannable.

Generalize or move time-sensitive examples (model names like 'Gemini 4 Argon', contributor handles, specific week dates) out of the main body or into a lessons reference.

DimensionReasoningScore

Conciseness

Editorial rules are restated across sections (value-before-mechanism appears in 'Mechanical-writing test', 'Order', and 'Length'; anti-AI-slop rules appear in both 'Goal' and 'Writing Constraints'), and a 30+-entry 'Lessons learned' log inlines time-sensitive history ("Gemini 4 Argon", "GPT-6 has no Terra", contributor names like "Serghei Hmeli"), which the rubric penalizes. Not 3 because the duplication and append-only log constitute several padded sections rather than isolated slips; not 1 because nothing explains generic concepts Claude already knows.

2 / 5

Actionability

Fully executable guidance throughout: a copy-paste git window-diff command with path exclusion (`git diff $(git rev-list -1 --before='<Mon> 00:00' main)..` with `':!plugins/'`), a ready-to-use weekly entry template, grep-based duplicate-week checks, and a worked Slack deep-link slug example with channel ID. These cover the common cases concretely.

5 / 5

Workflow Clarity

Steps 0-5 are explicitly sequenced with validation checkpoints ("Verify window: author-date count == committer-date count", "grep all `### Week` headings and check for duplicates", "Re-read as a cold reader") and feedback loops ("EXPLICIT approval only", "stay on that topic until it is closed"). Matches the top anchor's sequence-plus-validation-plus-recovery pattern.

5 / 5

Progressive Disclosure

A single ~250-line file with no bundle files: section structure is genuinely present and organized (numbered operating rules, clear headers), but content that belongs in a separate reference (the lessons-learned log, the style guide) is inlined. Not 2 because the structure is well-developed rather than minimal; not 4 because the monolithic file leaves clear split opportunities unexploited.

3 / 5

Total

15

/

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 states a single clear action for a well-defined artifact (weekly CHANGELOG.md synchronization), making it reasonably distinct, but it omits any when-to-use trigger guidance and lists only one capability. It would score substantially higher with an explicit 'Use when...' clause and broader action coverage.

Suggestions

Add a 'Use when...' clause with concrete triggers, e.g., 'Use when asked to update or sync the changelog, summarize the week's changes, or prepare release notes'.

List the concrete actions performed, e.g., 'Diff the week's git history, draft weekly changelog entries from a template, and suggest a Slack announcement message'.

Include natural synonyms users would say (changelog, release notes, weekly summary, git changes) to broaden trigger term coverage.

DimensionReasoningScore

Specificity

"synchronize CHANGELOG.md with changes made last week (mon - sun)" names the domain and one concrete action, but no further actions (analysis, drafting, Slack posting) are listed. Matches anchor 3; not 4 because coverage is a single action rather than several specific ones.

3 / 5

Completeness

The "what" is clear (synchronize CHANGELOG.md with last week's changes) but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guideline. Not 4 because "when" is entirely absent, not merely imprecise.

3 / 5

Trigger Term Quality

"CHANGELOG.md", "changes", and "last week" are keywords a user would naturally say, but common variations and synonyms ("update the changelog", "release notes", "weekly summary") are missing. Not 2 because the terms present are specific and natural, not generic filler.

3 / 5

Distinctiveness Conflict Risk

The weekly-window changelog synchronization for a named artifact carves a mostly distinct niche with only minor overlap risk against adjacent release-notes or commit-message skills. Not 5 because no explicit trigger phrasing fully disambiguates it from those adjacent documentation skills.

4 / 5

Total

13

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

griddynamics/rosetta

Path

.claude/skills/update-change-log/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.