CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

implement-flet-extension

Implement a new Flet extension/control that wraps a third-party Flutter package end-to-end, including dependency selection, version pinning, compatibility checks, Python/Flutter integration, docs, examples, tests, and CI updates. Use when adding any flet_* package backed by an external pub.dev package.

Quality

91%

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

85%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.

An exceptionally actionable, well-sequenced workflow skill whose guidance is concrete down to exact commands, file paths, and code patterns, with real validation feedback loops. Its main structural weakness is that it is a monolithic single file: several sizeable sections are reference-grade material that should be split into bundled files with clear pointers.

Suggestions

Split the detailed 'Example Tests and Docs Images' procedure into a bundle file (e.g. references/test-images.md) and keep only the light/opaque-background rule plus a pointer in SKILL.md.

Move the sub-control documentation conventions into a reference file or lean harder on the existing pointer to .agents/skills/docs-conventions/SKILL.md instead of restating the rules inline.

Trim guidance Claude already follows by default, such as 'Avoid single-use local variables' and 'Keep alias short but readable', to tighten token use.

DimensionReasoningScore

Conciseness

Nearly every line carries non-obvious, repo-specific rules (import bans, registration file paths, default-value matching, golden-image procedure) with no padding of basic concepts. A few lines state knowledge Claude already has ('Avoid single-use local variables', 'Keep alias short but readable'), keeping it just below the 'every token earns its place' anchor.

4 / 5

Actionability

Guidance is copy-paste ready: exact file paths and edits ('client/pubspec.yaml: add flet_<ext>: path: ...'), exact commands ('FLET_TEST_GOLDEN=1 uv run pytest -s packages/flet/integration_tests/examples/extensions/<name>'), and exact code patterns ('parseEnum(MyEnum.values, widget.control.getString("attr"), MyEnum.defaultVal)!'). The common cases across dependency gating, implementation, integration, docs, tests, and CI are all covered concretely.

5 / 5

Workflow Clarity

The body is a clearly phased pipeline (dependency gate → classification → API mapping → Python/Flutter implementation → integration checklist → docs/examples/tests → validation) with explicit validation steps and a feedback loop ('fix the test or example, regenerate, then re-run without FLET_TEST_GOLDEN to confirm the comparisons pass'). Literal checklists ('Integration Checklist') and guardrails around temporary CI narrowing match the top anchor.

5 / 5

Progressive Disclosure

Section headers and in-file navigation are good, but the ~145-line body inlines detailed reference material — docs-page/sub-control conventions and the multi-step golden-image generation procedure — that belongs in one-level-deep bundle files. No bundle files (references/, scripts/, assets/) exist, and the only pointer out is to a different skill ('.agents/skills/docs-conventions/SKILL.md'), so content that should be separate is inline.

3 / 5

Total

17

/

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: third-person, dense with concrete actions, and pairing a clear capability statement with an explicit 'Use when' trigger clause. The only weakness is slightly incomplete synonym coverage of how users might phrase the request.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'dependency selection, version pinning, compatibility checks, Python/Flutter integration, docs, examples, tests, and CI updates' — giving comprehensive coverage of the task in third-person voice. It exceeds the 'several specific actions; minor gaps' anchor because nothing material is missing from the action list.

5 / 5

Completeness

It explicitly answers 'what' ('Implement a new Flet extension/control that wraps a third-party Flutter package end-to-end, including...') and 'when' ('Use when adding any flet_* package backed by an external pub.dev package') with concrete trigger phrases. Both halves are explicit, matching the top anchor rather than the 'when could be more specific' level below.

5 / 5

Trigger Term Quality

Natural trigger terms like 'flet_* package', 'external pub.dev package', 'third-party Flutter package', and 'Flet extension/control' cover the phrases a user would say. It falls short of comprehensive synonym coverage (e.g., 'wrap a Flutter package for Flet' or 'add a Flet control') but well above the 'some relevant keywords, missing common variations' anchor.

4 / 5

Distinctiveness Conflict Risk

The niche is unambiguous — Flet extensions backed by external pub.dev packages — with distinct triggers ('flet_* package', 'pub.dev package') that no generic skill would match. Conflict risk with other skills is minimal, matching the 'clear niche with distinct triggers' anchor.

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

Path

.agents/skills/implement-flet-extension/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.