CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

86%

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

88%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 tight, highly actionable skill: correct-scope templates, exact commands, and a validation-looped workflow with a checklist. The only refinements are slight redundancy around the scope-split rule and annotating the References entries so readers know what each file provides.

DimensionReasoningScore

Conciseness

The body is list-driven and assumes competence (no explanation of what Flet, pytest, or goldens are), with executable snippets throughout. Minor trimming is possible — the module/function scope rule is restated across 'Scope split rule', 'Fixture choice', and the checklist — matching anchor 4 rather than the perfectly lean anchor 5.

4 / 5

Actionability

Fully executable guidance: two copy-paste-ready test templates, exact assertion patterns, and precise run/regeneration commands with flags and env vars ('uv run pytest -s -o log_cli=true ...', 'FLET_TEST_GOLDEN=1', 'FLET_TEST_GOLDEN=failed'). These cover the common cases (module-scope visual, function-scope interactive, golden regeneration), matching anchor 5.

5 / 5

Workflow Clarity

The 8-step 'Authoring workflow' is clearly sequenced with an explicit validation checkpoint ('Run target test file') and a feedback loop for error recovery (step 8: regenerate goldens only for intentional changes, then re-run without golden mode), plus a closing quality checklist — anchor 5's pattern. It does not sit at 4 because no validation gap remains for the golden-overwrite operation.

5 / 5

Progressive Disclosure

The body is well-sectioned and the References list is one level deep with no nesting, but the skill ships no bundle files (no references/, scripts/, or assets/ directories) and the reference entries are bare paths with no signal of what each file offers, leaving minor organization gaps per anchor 4.

4 / 5

Total

18

/

20

Passed

Description

78%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, highly targeted description that names concrete capabilities and an explicit 'Use when' trigger with a specific path scope. Its main room for improvement is richer trigger coverage (screenshot/regression test phrasing) and separating the 'what' from the 'when' more distinctly.

Suggestions

Add common trigger synonyms such as 'screenshot tests' or 'regression tests for control bugs' so the description matches more natural user phrasings.

State the 'what' and 'when' as distinct clauses, e.g., 'Creates and updates Flet control integration tests, including visual goldens, interaction, and regression tests. Use when the user asks for integration tests, golden/screenshot updates, or control behavior verification in sdk/python/packages/flet/integration_tests.'

DimensionReasoningScore

Specificity

The description lists several concrete capabilities — "create or update integration tests", "visual goldens", "interactive behavior tests" — anchored to a specific path. It falls short of anchor 5 because coverage has minor gaps (e.g., regression tests and control-property behavior checks from the body are absent), but exceeds anchor 3's '1-2 concrete actions'.

4 / 5

Completeness

Both 'what' (create/update integration tests, goldens, interactive behavior tests) and 'when' ("Use when asked to create or update integration tests...") are explicitly present. The 'when' clause is a single trigger condition rather than the multiple concrete trigger phrases of anchor 5, and the what/when are fused into one sentence rather than clearly separated.

4 / 5

Trigger Term Quality

Natural phrases like "integration tests", "visual goldens", "interactive behavior tests", and "Flet control" match what a user would say. A few common variations are missing (e.g., "screenshot tests", "regression tests", "UI tests"), so it fits anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The trigger is tightly scoped to "any Flet control in sdk/python/packages/flet/integration_tests", a clear niche with distinct terminology (Flet, goldens) that no generic testing skill would match, satisfying anchor 5's minimal-conflict standard.

5 / 5

Total

17

/

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

Path

.agents/skills/create-flet-control-integration-tests/SKILL.md

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.