update-flet-control-doc-gifs

Create or update Flet control screenshots and GIFs that are generated from integration tests and shown in docs. Use when working on `sdk/python/packages/flet/integration_tests/examples`, refreshing static or interactive golden screenshots, or replacing old example media images or GIFs with generated test assets.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

81%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 content is a well-structured, actionable workflow with concrete Flet-specific APIs and a verification checklist supplying the validation feedback loop the rubric rewards. Minor conciseness and code-completeness gaps keep it just below the top anchor.

Suggestions

Add one small complete assert_screenshot/create_gif code snippet showing the canonical call signature and arguments so the common case is copy-paste ready.

Tighten the longer bullets in the Workflow and Docs Update Rules sections by dropping explanatory clauses that restate what the API already implies.

Consider promoting the referenced example test files (e.g. test_alert_dialog.py) into a short "See also" callout under Workflow step 1 so the reference is signaled at the point of use, not only listed at the end.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Flet competence (uses API names like assert_screenshot, pump_and_settle without explanation), with only minor over-explanation in a few bullets that could be trimmed.	4 / 5
Actionability	Concrete API calls, exact repo paths, and naming examples make the guidance executable, though no single complete copy-paste code block is provided for the common case.	4 / 5
Workflow Clarity	A clear 7-step sequence is paired with an explicit "Verification Checklist" that acts as a validation feedback loop for the media-replacement and golden-file operations.	5 / 5
Progressive Disclosure	Sections (Workflow, Naming, Docs Update Rules, Verification Checklist, References) are well-organized with navigable example-file references, but the references are repo paths rather than separately bundled docs to drill into.	4 / 5
	Total	17 / 20 Passed

Description

87%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 specific, third-person, and answers both what and when with concrete trigger paths. It is well-scoped to a narrow Flet workflow with minimal conflict risk.

Dimension	Reasoning	Score
Specificity	"Create or update Flet control screenshots and GIFs that are generated from integration tests and shown in docs" names several specific concrete actions (create, update, generate-from-tests), with only minor coverage gaps.	4 / 5
Completeness	It clearly states what the skill does and follows with an explicit "Use when..." clause listing concrete trigger paths and conditions, satisfying both what and when.	5 / 5
Trigger Term Quality	Natural terms like "screenshots", "GIFs", "golden screenshots", and "example media images" are present with synonyms (static/interactive), though a few common variations are missing.	4 / 5
Distinctiveness Conflict Risk	The Flet-control doc media niche with integration-test-specific triggers is clearly distinct and unlikely to fire for unrelated skills.	5 / 5
	Total	18 / 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: flet-dev/flet
Path: .agents/skills/update-flet-control-doc-gifs/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.