create-flet-example-projects

Use when asked to create Flet example projects from flat .py files with main.py and pyproject.toml metadata for Gallery/MCP indexing.

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/create-flet-example-projects/SKILL.md

Quality

Content

77%

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

A highly actionable, well-sequenced workflow with strong validation feedback loops; its main weaknesses are repeated clauses across steps and an all-inline structure that exceeds the simple-skill threshold for progressive disclosure.

Suggestions

De-duplicate the "apply to all examples (new, migrated, already converted)" clause into a single stated scope at the top of the Workflow section rather than repeating it per step.

Factor the pyproject.toml field schema and metadata-inference rules into a references file (e.g. references/metadata.md) and point to it from the relevant step to reduce inline bulk and improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is dense and almost entirely task-specific (no generic concepts Claude already knows), but it repeats "Apply this to all examples in the touched folder (new, migrated, and already converted)" across steps 6 and 9, and step 11 re-validates rules already stated in step 6, so it could be tightened.	2 / 3
Actionability	Concrete executable commands ("rg --files <target_dir>", "uv run ruff check", "python -m compileall"), exact import patterns, and a full pyproject field list provide copy-paste-ready guidance.	3 / 3
Workflow Clarity	Eleven sequenced steps culminate in a dedicated Validate step with explicit checkpoints (compileall, ruff, stale-path search, git status) and a feedback loop ("fix violations until it passes") for the destructive/batch file moves.	3 / 3
Progressive Disclosure	The skill is a single 147-line inline document with no bundle files (references/, scripts/, assets/ absent); it is section-organized, but large inline content like the pyproject schema and metadata-inference rules could be split out, matching the score-2 anchor of structure present but content that should be separate staying inline.	2 / 3
	Total	10 / 12 Passed

Description

75%

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 concise, well-triggered description with an explicit "Use when" clause and a clearly distinct niche, though it elaborates one action rather than enumerating several concrete capabilities.

Suggestions

Enumerate multiple concrete actions (e.g. "create, migrate, and normalize Flet example projects") to raise specificity to the score-3 anchor.

Add a couple of natural trigger variations ("migrate flat examples", "Gallery examples", "convert .py to project-per-example") to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The phrase "create Flet example projects from flat .py files with main.py and pyproject.toml metadata" names the domain and concrete inputs/outputs, but describes a single action (create) rather than multiple distinct actions, so it falls short of the score-3 anchor.	2 / 3
Completeness	It states what the skill does ("create Flet example projects from flat .py files with main.py and pyproject.toml metadata") and gives an explicit trigger ("Use when asked to create ..."), clearly answering both what and when.	3 / 3
Trigger Term Quality	"create Flet example projects" and "flat .py files" are natural terms a user might say, but coverage is limited with few common variations (e.g. no "convert", "migrate", "Gallery examples" phrasings), matching the score-2 anchor of some relevant keywords with missing variations.	2 / 3
Distinctiveness Conflict Risk	The niche is sharply scoped to Flet examples, flat .py conversion, and Gallery/MCP indexing, making it clearly distinguishable and unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 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/create-flet-example-projects/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.