create-flet-control-integration-tests

Use when asked to create or update integration tests for any Flet control in sdk/python/packages/flet/integration_tests, including visual goldens and interactive behavior tests.

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 body is a tight, actionable integration-test authoring guide with executable commands, code templates, and a validated workflow including a golden-regeneration feedback loop. Main weaknesses are placeholder-laden templates and the absence of bundle files, leaving all content inline.

Suggestions

Tighten the "When to use" section so it does not restate the frontmatter description, and shorten the fixture blurbs to just the scope/loop_scope facts.

Add a fully concrete worked example (e.g. a real test_visible_button test) alongside the parameterized templates so at least one path is copy-paste-runnable without renaming placeholders.

Consider moving the assertion-pattern snippets or templates into a reference file under references/ to give the skill genuine one-level-deep progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly lean with no basic-concept padding, but the "When to use" section partly restates the frontmatter description and fixture blurbs ("best for stable visual tests and bulk screenshot tests") could be trimmed, placing it at score 4 rather than the fully tight score 5.	4 / 5
Actionability	Provides executable run commands and concrete assertion patterns, but the minimal templates still use placeholders (test_<behavior>, test_<control>) that keep them just short of copy-paste-ready, matching score 4 over 5.	4 / 5
Workflow Clarity	The 8-step Authoring workflow includes explicit validation (run the target file) and a feedback loop (regenerate goldens with FLET_TEST_GOLDEN=1 and re-run if visuals changed), plus a Quality checklist, hitting the score-5 anchor of clear sequence with validation and error-recovery loops.	5 / 5
Progressive Disclosure	Well-organized sections with clearly signaled one-level-deep repo references, but no bundle files exist and all content is inline in SKILL.md, so it lands at score 4 (good structure, minor organization gaps) rather than the content-split-across-files score 5.	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.

A strong description: it explicitly states what the skill does and when to use it, with concrete trigger phrasing and a tightly scoped niche that minimizes conflict risk. Trigger-term coverage is good but could add common synonyms (e.g. golden screenshots, regression tests) for full comprehensiveness.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions — "create or update integration tests", "visual goldens", "interactive behavior tests" — with only minor coverage gaps, fitting the score-4 anchor better than the narrower 1-2 actions of score 3.	4 / 5
Completeness	Explicitly answers both: the trigger "Use when asked to create or update integration tests for any Flet control" and the concrete "what" (visual goldens, interactive behavior tests), matching the score-5 anchor of clear what-and-when with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural keyword coverage ("integration tests", "Flet control", "visual goldens", "interactive behavior tests") a user would say, but missing common synonyms like "golden screenshots", "screenshot tests", or "regression tests" that would warrant a 5.	4 / 5
Distinctiveness Conflict Risk	Pinned to a specific path (sdk/python/packages/flet/integration_tests) and a Flet-control niche with distinct triggers, giving minimal conflict risk with other skills as the score-5 anchor describes.	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/create-flet-control-integration-tests/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.