write-changelog-entry

Use when asked to add, revise, or review a changelog or release-notes entry in this repo. Inspect the existing changelog section style and the relevant PR, issue, and commit context first, then write a focused entry in the correct release section without overstating docs, tests, or chores unless they are the primary user-facing change.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

88%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.

A well-crafted instruction skill: a concrete numbered workflow with a final verification checklist, exact file paths, section headings, attribution formats, and copy-paste-ready example entries for both root and Flutter-package changelogs. Weaknesses are minor — some redundancy between the 'Target file selection', 'Root vs Flutter package changelog', and 'Repo-specific guidance' sections, and a monolithic single file where a reference split could reduce context load.

Suggestions

Merge the overlapping extension-package guidance in 'Target file selection' and 'Repo-specific guidance' into one place to remove redundancy.

Consolidate 'Target file selection' and 'Root vs Flutter package changelog' into a single audience/file-selection section, or move the detailed audience rules to a reference file to shorten SKILL.md.

Dimension	Reasoning	Score
Conciseness	The body is lean and imperative with no padding about concepts Claude already knows, but there is mild redundancy: extension-package guidance appears in both 'Target file selection' ('Do not surface internal Flutter implementation changes unless they materially change the Python-facing feature') and 'Repo-specific guidance' ('prefer Python-facing API... over Flutter implementation details'), and the audience rules are split across two overlapping sections. This matches the 'efficient; minor instances that could be trimmed' anchor rather than 'every token earns its place'.	4 / 5
Actionability	For an instruction-only skill the guidance is fully actionable: exact file paths ('/CHANGELOG.md', 'packages/flet/CHANGELOG.md', 'sdk/python/packages/<package>/CHANGELOG.md'), the exact bucket headings to use, near copy-paste-ready example entries ('Add `scrollable` to `NavigationRail` for overflowed destinations ([#1923](...)) by @login.'), and exact attribution formats ('by @user1, @user2.'). Specific examples cover the common cases.	5 / 5
Workflow Clarity	A clear 5-step numbered workflow (inspect target section, inspect PR/issue/commit context, extract the primary change, write the entries, add links and attribution) is closed by an explicit 'Checks' verification checklist before finishing. Sequence and checkpoints are explicit, and this is neither a destructive nor batch operation, so no cap applies.	5 / 5
Progressive Disclosure	No bundle files exist and the skill is a single self-contained SKILL.md with well-labeled sections, so there is nothing buried or nested. However, at ~125 lines it exceeds the simple-skill threshold and repo-specific material (root-vs-Flutter-package audience rules, attribution conventions) could be split into a reference file, matching the 'good structure; minor organization gaps' anchor.	4 / 5
	Total	18 / 20 Passed

Description

92%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.

A strong description: third-person imperative voice, explicit 'Use when' triggers covering add/revise/review, both key synonyms (changelog, release-notes), and a concrete statement of the workflow (inspect context, then write a focused entry in the correct release section). Only minor upside from adding a few more natural trigger variations like 'update the changelog' or 'CHANGELOG.md'.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions covering the whole task ('add, revise, or review a changelog or release-notes entry', 'Inspect the existing changelog section style and the relevant PR, issue, and commit context first, then write a focused entry in the correct release section'), with no coverage gap relative to what the skill actually does.	5 / 5
Completeness	It explicitly answers both when ('Use when asked to add, revise, or review a changelog or release-notes entry in this repo') and what ('Inspect the existing changelog section style and the relevant PR, issue, and commit context first, then write a focused entry in the correct release section') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good keyword coverage including the key synonyms 'changelog' and 'release-notes' plus natural verb triggers ('add, revise, or review') and 'PR, issue, and commit'. A few natural phrasings users might say are missing, such as 'update the changelog' or 'CHANGELOG.md', keeping it below the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	A clear niche — writing changelog entries in this repo — with distinct trigger terms ('changelog', 'release-notes entry') and minimal overlap risk with any other skill.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 8 suspicious	Warning

	Total	15 / 16 Passed

Repository: flet-dev/flet
Path: .agents/skills/write-changelog-entry/SKILL.md
Commit: 9748de3

Reviewed: 4 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.