CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

80%

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

Fix and improve this skill with Tessl

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

Quality

Content

77%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 strong operational skill: highly prescriptive, sequenced, with explicit validation and feedback loops for a batch migration task. The main gap is structural — all detail lives inline in SKILL.md with no progressive disclosure, and there is minor rule duplication between the workflow steps and the validation checklist.

Suggestions

Move the pyproject.toml required-fields and metadata-inference rules (steps 3–4) into a reference file such as references/pyproject-metadata.md, leaving a short summary plus a clearly signaled link in SKILL.md.

Remove the duplicated "apply to all examples in the touched folder" bullets in step 6 and deduplicate the step 11 checklist against the workflow steps, keeping only genuinely new checks.

Add a complete example pyproject.toml (inline or in the reference file) showing all required fields filled in for one converted example, so the output format is copy-paste verifiable.

DimensionReasoningScore

Conciseness

The body is dense, prescriptive, and assumes Claude's competence (no explanations of Flet or packaging concepts), with concrete commands like `rg --files <target_dir>` and `uv run ruff check`. Minor trimmable duplication exists — the bullet "Apply this to all examples in the touched folder (new, migrated, and already converted)" appears twice in step 6, and step 11's checklist restates rules from steps 6, 8, and 9 — which keeps it at anchor 4 rather than anchor 5.

4 / 5

Actionability

Mostly executable guidance: exact commands (`python -m compileall`, `uv run ruff check`), a concrete import pattern (`import examples.controls.foo.bar.main as bar`), an explicit entrypoint snippet (`if __name__ == "__main__": ft.run(main)`), and field-by-field pyproject.toml requirements. A full copy-paste `pyproject.toml` example/template is the missing piece that would reach anchor 5's 'copy-paste ready' coverage of common cases.

4 / 5

Workflow Clarity

The 11-step workflow is clearly sequenced (inspect → convert → pyproject → metadata → deps → mobile-safety → controls → M3 cleanup → entrypoint → references → validate) and ends in an explicit validation stage with commands and a fix-loop ("Run `uv run ruff check` ... and fix violations until it passes") plus a confirmation checklist — matching anchor 5's explicit validation steps and feedback loops for a batch operation. It clearly exceeds anchor 4, which tolerates missing checkpoints.

5 / 5

Progressive Disclosure

Sections are well organized (When to use, Goal, Workflow, Code style, Command checklist, Output expectations), but the 147-line body is fully inline with no bundle files at all; the field-by-field pyproject.toml/metadata specification (steps 3–4) and the validation checklist are candidates for a one-level-deep reference file. This matches anchor 3 ('content that should be separate is inline') rather than anchor 4, since the over-50-line guideline applies and nothing is split out.

3 / 5

Total

16

/

20

Passed

Description

73%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 concise, niche-specific description with an explicit trigger clause and concrete artifact names. Its main limitations are the single-action framing (create) that under-represents the skill's migrate/normalize capabilities and the lack of trigger synonyms.

DimensionReasoningScore

Specificity

The description names the domain and concrete artifacts ("create Flet example projects from flat .py files with main.py and pyproject.toml metadata for Gallery/MCP indexing") but describes a single action with specifics rather than several distinct actions, and omits migration/normalization/validation covered in the body. This matches anchor 3 ('names domain and 1-2 concrete actions, but not comprehensive') and falls short of anchor 4, which expects several listed actions.

3 / 5

Completeness

Both parts are present: the "what" ("create Flet example projects ... with main.py and pyproject.toml metadata") and an explicit "Use when asked to ..." trigger clause. The "when" is a single clause without trigger variations or synonyms, which keeps it at anchor 4 rather than anchor 5's 'concrete trigger phrases' with multiple phrasings.

4 / 5

Trigger Term Quality

Good natural keyword coverage: "Flet example projects", "flat .py files", "main.py", "pyproject.toml", "Gallery/MCP" are terms a user working in this repo would say. It misses natural variations like "migrate", "convert", or "normalize" that the body itself lists as triggers, so it is not anchor 5.

4 / 5

Distinctiveness Conflict Risk

The description occupies a clear niche with distinct triggers — "Flet example projects", "flat .py files", "pyproject.toml", "Gallery/MCP indexing" — that no generic skill would claim, matching the anchor 5 example of a clear niche with minimal conflict risk. It is clearly above anchor 4, which still allows minor overlap with closely related skills.

5 / 5

Total

16

/

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-example-projects/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.