frb-write-changelog

Update flutter_rust_bridge CHANGELOG.md for a new release by collecting merged PRs since the previous version tag, mapping them to the target release section, and formatting entries to match the existing changelog style. Use when writing or refreshing a release section in CHANGELOG.md.

Quality

90%

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 thorough, highly actionable changelog-writing workflow with strong validation feedback loops and executable commands. Its main weakness is conciseness: the stable-release ordering and edge-case rules are dense enough that some content could be externalized.

Suggestions

Move the lengthy stable-release grouping and ordering rules (Step 5) into a referenced reference file (e.g. STABLE_RELEASE_FORMAT.md), keeping only the core rule and a pointer in SKILL.md to improve both conciseness and progressive_disclosure.

Confirm the referenced verify_changelog.py is shipped with the skill bundle (e.g. under scripts/) so the one-level reference resolves; if it lives only in the repo at .claude/skills/..., document that dependency explicitly.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — no padding explaining git/GitHub/CI concepts — but the dense stable-release ordering and edge-case rules (Step 5) run long and could be trimmed or externalized for a 5.	4 / 5
Actionability	Provides fully executable commands throughout — 'git tag --sort=-creatordate \| head -n 20', 'gh pr list --state merged --limit 200 --json ...', and the complete verifier invocation with all flags — copy-paste ready and covering the common cases.	5 / 5
Workflow Clarity	Ten clearly sequenced steps with explicit validation checkpoints and feedback loops (verify_changelog.py, re-verify after human edits, --set-exit-if-changed drift gate) for a batch/release operation, satisfying the destructive/batch validation requirement.	5 / 5
Progressive Disclosure	Well-organized numbered sections with a one-level reference to the verifier script and no nested references; the detailed formatting rules are inlined rather than split into a separate reference file, leaving minor organization room.	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 highly specific, well-structured description that concretely states what the skill does and when to use it, with minimal conflict risk. The only minor gap is slightly narrow trigger-term coverage.

Suggestions

Add a couple of natural synonyms to the trigger clause, e.g. 'Use when writing or refreshing a release section, release notes, or version history in CHANGELOG.md', so users who phrase the need differently still match.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'collecting merged PRs since the previous version tag, mapping them to the target release section, and formatting entries to match the existing changelog style' — with comprehensive coverage of the skill's behavior.	5 / 5
Completeness	Clearly answers both: the 'what' (collect PRs, map to section, format to style) and an explicit 'Use when...' trigger clause naming the concrete scenario.	5 / 5
Trigger Term Quality	The trigger 'Use when writing or refreshing a release section in CHANGELOG.md' is natural and specific, but coverage lacks common synonyms/variations a user might say (e.g., 'release notes', 'version history', 'what changed'), so it is just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	Tightly scoped to flutter_rust_bridge CHANGELOG releases with distinct triggers, making conflict with other skills minimal.	5 / 5
	Total	19 / 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: fzyzcjy/flutter_rust_bridge
Path: .claude/skills/frb-write-changelog/SKILL.md
Commit: 8f2ab1b

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