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.

74

Quality

93%

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

90%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 body is an efficient, highly actionable workflow with concrete commands, exact paths, and an explicit pre-handoff verification checklist. Its only shortfalls are a missing error-recovery loop after verification and no use of reference files to offload detail.

DimensionReasoningScore

Conciseness

The body is lean with zero concept explanations or padding; every line is Flet-specific guidance (e.g., "Promote 5-8 most substantial features", "Wrap control/service/type names in backticks"), so every token earns its place.

5 / 5

Actionability

Commands are copy-paste ready and complete: `pip install 'flet[all]' --upgrade`, the full `uv sync --upgrade-package flet ...` block, and a "Useful command patterns" section with concrete rg/sed/mkdir/cp invocations covering the common cases.

5 / 5

Workflow Clarity

Seven clearly numbered steps end in an explicit "Verify before handoff" checklist (image paths exist, links resolve, other-changes mirror the changelog), but there is no feedback loop instructing what to do when a check fails.

4 / 5

Progressive Disclosure

Sections are well organized (Inputs, Style targets, Workflow, Commands, Checklist) with no bundle files, and the inline content is appropriate for a self-contained ~100-line skill; however, the screenshot-sourcing and upgrade-instruction sections are borderline candidates for a small external reference file.

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: it names the domain, concrete actions, and deliverable components, and pairs them with an explicit, naturally phrased trigger clause. The only weakness is slightly thin synonym coverage for how users might phrase the request.

DimensionReasoningScore

Specificity

"Create or update a Flet release announcement blog post from changelog notes, matching existing /blog style" plus a comprehensive inventory of artifacts (feature sections, screenshots, code samples, pip and uv/pyproject.toml upgrade instructions, "other changes" summary) lists multiple concrete actions with no coverage gap.

5 / 5

Completeness

Explicitly answers both "what" (create/update a Flet release announcement blog post from changelog notes matching /blog style) 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

"draft, plan, or revise", "Flet X.Y.Z release announcement", and "Flet" are natural phrases users would say, but a few common variants (e.g., "release notes", "write up the release") are missing.

4 / 5

Distinctiveness Conflict Risk

"Flet" + "release announcement" + "/blog style" carves a clear niche with distinct triggers, so overlap with generic blogging or changelog skills is 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.

Validation — 16 / 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.