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

84%

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

81%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-structured, actionable changelog-writing skill with a clear workflow and verification checklist. The main weakness is repetition of the same anti-overstatement and audience-scoping rules across multiple sections, which inflates length without adding guidance.

Suggestions

Consolidate the repeated 'do not surface internal Flutter/Dart implementation changes' and 'do not mention docs/examples unless primary' rules into a single canonical statement referenced from the other sections.

Consider moving the 'Good patterns' example entries and per-audience phrasing rules into a references file to bring the body closer to a lean overview.

Trim near-duplicate bullets in 'Target file selection' and 'Root vs Flutter package changelog' that restate the same audience-split guidance.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of basic-concept padding, but several rules repeat across sections (e.g. 'do not surface internal Flutter changes' in Target file selection, Root vs Flutter, and Repo-specific guidance; 'do not mention docs/examples' stated twice), so it could be tightened.	3 / 5
Actionability	Highly actionable instruction-only guidance: exact section buckets, attribution format 'by @login.', link ordering (issue before PR), and concrete copy-paste-ready entry examples in Good patterns cover the common cases.	5 / 5
Workflow Clarity	Clear numbered 5-step workflow with substeps plus a dedicated 'Checks' verification checklist at the end; the writing task needs no error-recovery loop, so the explicit checklist satisfies the validation checkpoint bar.	5 / 5
Progressive Disclosure	Single well-organized SKILL.md with clear section headers and no nested references; at ~125 lines it exceeds the under-50-line simple-skill exception, and a few dense guidance blocks could arguably live in a reference file, so it stops just short of 5.	4 / 5
	Total	17 / 20 Passed

Description

87%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, third-person description with an explicit 'Use when' trigger and concrete actions that clearly distinguish it from sibling skills. Minor keyword synonyms and edge-case actions are the only gaps.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — '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' — with only minor coverage gaps (does not enumerate audience-tailoring nuance).	4 / 5
Completeness	Explicitly answers both what (write a focused entry in the correct release section) and when ('Use when asked to add, revise, or review a changelog or release-notes entry in this repo') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural keyword coverage with 'changelog', 'release-notes entry', 'add, revise, or review'; a few synonyms users might say (e.g. 'What's New', 'release highlights') are missing.	4 / 5
Distinctiveness Conflict Risk	Clear niche scoped to changelog/release-notes entries in this repo with distinct triggers; minimal conflict risk with other skills.	5 / 5
	Total	18 / 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: 8f74fe9

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