prepare-flet-release

Use when asked to prepare new Flet release by bumping versions and author release notes.

Quality

88%

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

93%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 body is lean, highly actionable, and well-structured, providing copy-paste-ready commands and concrete file paths throughout. The main gap is workflow_clarity: the multi-file, batch-style release edits have a pre-edit scan checkpoint but no post-edit verification feedback loop.

Suggestions

Add a post-edit verification step (e.g. re-run the Unreleased scan to confirm no Unreleased sections remain and all new sections are correctly sorted) to close the validation feedback loop.

Include an explicit validation/check step after setting the version in pubspec.yaml (e.g. confirm pubspec.lock reflects the new version) to strengthen checkpoints for the batch file edits.

Dimension	Reasoning	Score
Conciseness	The body is lean and action-oriented with no padding: it never explains what Flet is or how git/pub works, and every step earns its place. This matches the top anchor of assuming Claude's competence with every token pulling weight.	5 / 5
Actionability	Guidance is fully executable: concrete file paths (packages/flet/pubspec.yaml, website/docs/release/release-notes.md), a copy-paste-ready check command (rg -n ...), and exact branch naming (prepare-release-{new_version}). It covers the common cases specifically rather than abstractly.	5 / 5
Workflow Clarity	Steps are clearly sequenced and include a real validation checkpoint (scanning all changelogs for Unreleased sections via an explicit command). It falls short of 5 because there is no error-recovery feedback loop after the edits (e.g. re-scan to confirm no Unreleased sections remain), only a single pre-edit scan.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections (Inputs, Related Skills, Steps) with well-signaled one-level-deep references to sibling skills via relative links. Per the rubric's simple-skill guidance, well-organized content with no need for external bundle files can score 5 even without bundle files.	5 / 5
	Total	19 / 20 Passed

Description

82%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 is concise, uses third person, and clearly pairs a concrete 'what' with an explicit 'when' trigger. Trigger-term coverage is good but could include a few more natural synonyms. Specificity is the main weak point: it surfaces only two of the release-prep actions.

Suggestions

Broaden the 'what' to mention more concrete release-prep actions, e.g. 'bumping versions, authoring changelog and release notes, and updating breaking-change docs'.

Add a few natural trigger synonyms such as 'cut a Flet release' or 'publish a Flet release' to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ("prepare new Flet release") and two concrete actions ("bumping versions" and "author release notes"), matching the anchor that lists 1-2 concrete actions but is not comprehensive. It does not enumerate the broader set of release-prep actions (changelog, milestones, breaking-change docs), so it is not a 4.	3 / 5
Completeness	It explicitly answers both what ("prepare new Flet release by bumping versions and author release notes") and when ("Use when asked to prepare new Flet release") with a concrete trigger phrase. The 'when' is explicit and specific rather than weakly implied, matching the top anchor.	5 / 5
Trigger Term Quality	"Use when asked to prepare new Flet release" is a natural phrase users would actually say, with good keywords ("Flet release", "bumping versions", "release notes"). A few natural synonyms (e.g. "cut a release", "publish", version numbers) are missing, so it falls short of a 5.	4 / 5
Distinctiveness Conflict Risk	"Flet release" is a clear niche with distinct triggers and minimal conflict risk; it is unlikely to fire for unrelated skills. The trigger is product- and task-specific, matching the top anchor.	5 / 5
	Total	17 / 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: 4 suspicious	Warning

	Total	15 / 16 Passed

Repository: flet-dev/flet
Path: .agents/skills/prepare-flet-release/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.