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

88%

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

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable, concise, and well-sequenced content with concrete edits and validation steps for a complex multi-step task. The only gap is progressive disclosure: the skill is a single large file with no referenced bundle materials, keeping some reference-style detail inline.

Suggestions

Move the lengthy Integration Checklist and Docs/Examples/Tests detail into a reference file (e.g. references/integration-checklist.md) and link to it from SKILL.md to improve progressive disclosure.

Extract the default-value-mapping table into a small reference or keep only the principle inline with a pointer to the full per-type examples.

Consider a references/ template (e.g. a pyproject.toml snippet file) so repeated copy-paste edits live one level deep rather than inline.

Dimension	Reasoning	Score
Conciseness	Lean, dense guidance that assumes competence — concrete file paths, exact YAML/CI edits, and accessor signatures with no padded conceptual explanation.	3 / 3
Actionability	Provides copy-paste-ready specifics: exact dependency lines, main.dart import/registration snippets, parseEnum call signatures, and default-value matching examples across types.	3 / 3
Workflow Clarity	Sequenced phases (dependency gate -> classification -> API mapping -> integration checklist) with a final Validation section and explicit checkpoints like "Only proceed when validation passes"-style guards and PR-removal reminders.	3 / 3
Progressive Disclosure	Well-organized into clear sections, but it is a single ~100-line monolithic SKILL.md with no bundle files and no split-out references, so the dense integration checklist and docs guidance live inline rather than in separate files.	2 / 3
	Total	11 / 12 Passed

Description

85%

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, third-person description that conveys a precise end-to-end scope and an explicit 'Use when' trigger with low conflict risk. Trigger-term naturalness is its only minor weakness, leaning technical over conversational.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions ("dependency selection, version pinning, compatibility checks, Python/Flutter integration, docs, examples, tests, and CI updates") rather than vague language.	3 / 3
Completeness	Clearly answers both what (wrap a third-party Flutter package end-to-end) and when ("Use when adding any flet_* package backed by an external pub.dev package").	3 / 3
Trigger Term Quality	Includes relevant terms like "Flet extension/control", "third-party Flutter package", and "flet_* package", but natural user phrasings like "pub.dev package" or generic "add a Flet control" are thin; mostly technical jargon.	2 / 3
Distinctiveness Conflict Risk	Targets a clear niche (Flet extensions backed by external pub.dev packages) with a distinct trigger unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 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/implement-flet-extension/SKILL.md
Commit: db0df8e

Reviewed: 4 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.