flet-release-announcement

Drafts Flet release announcement blog posts from changelog notes with screenshots and upgrade instructions.

16.6k|685|Updated Mar 24, 2022
One-click install
npx skills add https://github.com/flet-dev/flet --skill flet-release-announcement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flet-release-announcement
Source: https://github.com/flet-dev/flet/tree/main/website/.agents/skills/flet-release-announcement
Command: npx skills add https://github.com/flet-dev/flet --skill flet-release-announcement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing a Flet release announcement blog post requires manually reconciling changelog entries, matching the established /blog style, sourcing screenshots, and formatting upgrade instructions, which is repetitive and error-prone.

Core Features & Use Cases

  • Changelog-grounded drafting: Extracts the exact release section from CHANGELOG.md and promotes 5-8 major features into dedicated sections while keeping minor items in a compact "Other changes" list.
  • Style matching: Reads 2-3 recent release posts in /blog to reuse frontmatter, structure, tone, and conventions like {} and linked issue references.
  • Asset sourcing: Locates screenshots from integration test golden images or example media and copies them into static/img/blog/flet-<version>/.
  • Use Case: When Flet 0.81.0 ships, ask the assistant to draft the release announcement; it reads the changelog, selects major features, embeds code samples and screenshots, and includes both pip and uv upgrade commands.

Quick Start

Draft a Flet 0.81.0 release announcement blog post from the changelog in this repository.

Frequently Asked Questions about flet-release-announcement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a Flet release announcement blog post?

Provide the release version and changelog source, then the workflow reads recent /blog posts for style, extracts the exact release section from CHANGELOG.md, and drafts major feature sections with code samples, screenshots, and upgrade instructions.

How are major features selected from the changelog?

The 5-8 most substantial changelog items are promoted to dedicated sections with explanations, code samples, and screenshots. Less substantial or niche items are kept as compact bullets in an "Other changes and bug fixes" section.

Where do the screenshots in the release post come from?

Screenshots are sourced from existing integration test golden images under sdk/python/packages/flet/integration_tests or example media folders, then copied into static/img/blog/flet-<version>/ in the website repository.

What upgrade instructions are included in the announcement?

Every post includes both a pip flow (pip install 'flet[all]' --upgrade) and a uv flow with pyproject.toml, including per-package upgrades for flet, flet-cli, flet-desktop, and flet-web, plus a note about flet-desktop-light on Linux.

What are the limitations of this release drafting workflow?

It only covers Flet release announcement posts matching the existing /blog conventions and cannot invent claims, platforms, or options not present in the changelog. If a screenshot is unavailable, the gap must be explicitly noted rather than fabricated.