CtrlK
BlogDocsLog inGet started
Tessl Logo

flet-release-announcement

Create or update a Flet release announcement blog post from changelog notes, matching existing /blog style. Use when asked to draft, plan, or revise posts like "Flet X.Y.Z release announcement" with major feature sections, screenshots, code samples, upgrade instructions (pip and uv/pyproject.toml), and a compact "other changes" summary.

69

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 skill body with concrete commands, a sequenced workflow, and an explicit verification step. Minor room to tighten a few obvious-instruction bullets and make image-sourcing error handling more explicit.

Suggestions

Trim guidance Claude already follows (e.g. 'Avoid excessive emoji and unnecessary bold formatting') to push conciseness toward the top anchor.

Add an explicit error-recovery loop in the screenshot step (e.g. 'if no golden image exists, search examples/media, then note the gap') rather than only flagging the gap.

Consider moving the 'Useful command patterns' block into a scripts/ or references/ file so the SKILL.md body stays a lean overview, improving progressive disclosure for this 90-line skill.

DimensionReasoningScore

Conciseness

Mostly lean and directive ('Ground facts in changelog', 'Do not invent claims, platforms, or options') with no concept explanations, but a few bullets like 'Avoid excessive emoji and unnecessary bold formatting' state things Claude already knows and could be trimmed.

4 / 5

Actionability

Provides concrete, executable guidance — copy-paste 'pip install "flet[all]" --upgrade' and 'uv sync --upgrade' commands plus specific rg/sed/mkdir/cp patterns and real paths — but step 5's feature-section template ('What it is', 'What problem it solves') is structural rather than executable, leaving a minor gap.

4 / 5

Workflow Clarity

A clear 7-step sequence culminating in 'Verify before handoff' with an explicit validation checklist (image paths exist, links resolve, other-changes mirror changelog); error-recovery feedback loops are only implicit ('If an image is unavailable, explicitly note the gap'), keeping it just below the top anchor.

4 / 5

Progressive Disclosure

Well-organized into clear sections (Inputs, Style targets, Workflow, Command patterns, Output checklist) in a self-contained file with no nested references; at ~90 lines it slightly exceeds the under-50-line simple-skill threshold, so it sits at good-structure rather than the top anchor.

4 / 5

Total

16

/

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, specific description that clearly states what the skill does and when to use it, with concrete trigger phrasing and low conflict risk. The only minor gap is slight synonym coverage in the trigger terms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and components — 'Create or update a Flet release announcement blog post from changelog notes' plus 'major feature sections, screenshots, code samples, upgrade instructions (pip and uv/pyproject.toml), and a compact "other changes" summary' — giving comprehensive coverage of what the skill produces.

5 / 5

Completeness

Explicitly answers both 'what' (create/update a Flet release blog post from changelog notes with named sections) and 'when' ('Use when asked to draft, plan, or revise posts like "Flet X.Y.Z release announcement"') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural trigger coverage with 'draft, plan, or revise posts like "Flet X.Y.Z release announcement"', but a few common variations (e.g. 'release notes', 'release blog post') are absent, so it falls just short of the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Flet release announcements on the /blog) with distinct triggers ('Flet X.Y.Z release announcement'), making conflict with other skills minimal.

5 / 5

Total

19

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
flet-dev/flet
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.