CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

64

Quality

76%

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

73%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 dense, actionable, well-sequenced migration skill with strong validation and concrete commands. Its main weaknesses are repetitive injunctions and a long monolithic body that could benefit from splitting reference material into a bundled file.

Suggestions

De-duplicate the repeated 'Apply this to all examples in the touched folder (new, migrated, and already converted)' phrase by stating the scope once at the top of the relevant section.

Consolidate step 11's 'Confirm...' lines so validation cross-references the earlier rules rather than restating each one, reducing token cost.

Move the full pyproject.toml required-fields list into a references/ file (e.g., PYPROJECT.md) and link to it from the body to improve progressive disclosure.

DimensionReasoningScore

Conciseness

Mostly efficient and free of basic-concept padding, but it repeats injunctions ('Apply this to all examples in the touched folder (new, migrated, and already converted)') and the validation step largely restates earlier rules as 'Confirm...' lines; not a 4 due to this noticeable redundancy.

3 / 5

Actionability

Provides concrete copy-paste commands ('rg --files', 'python -m compileall', 'uv run ruff check'), exact import patterns, required pyproject fields, and entrypoint code; not a 5 because the 'Infer metadata' steps remain somewhat abstract ('choose closest practical value', 'infer from path and code').

4 / 5

Workflow Clarity

An 11-step sequence with an explicit validation step (step 11), feedback loops ('fix violations until it passes'), and a checklist; validation is present so the destructive/batch cap does not apply.

5 / 5

Progressive Disclosure

Well-organized with clear section headers and no nested references, and no bundle files exist to mis-signal; not a 5 because at ~140 lines everything is inlined where some material (e.g., the full pyproject field requirements) could be split into a reference file.

4 / 5

Total

16

/

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 specific, well-targeted description that clearly conveys both purpose and trigger conditions with minimal conflict risk. It could be improved by diversifying the 'when' clause to cover migration/normalization scenarios mentioned in the body.

DimensionReasoningScore

Specificity

Names the domain and concrete deliverables ('create Flet example projects from flat .py files with main.py and pyproject.toml metadata for Gallery/MCP indexing'), listing several specific actions; falls short of 5 because it is essentially one action with components rather than multiple distinct actions.

4 / 5

Completeness

Explicitly answers both what (create Flet example projects from flat .py files with metadata) and when ('Use when asked to create Flet example projects...'); not a 5 because the 'when' reuses the same phrasing as the 'what' rather than enumerating distinct trigger scenarios like migrate/normalize.

4 / 5

Trigger Term Quality

Includes natural terms a user would say ('create Flet example projects', 'flat .py files', 'main.py', 'pyproject.toml', 'Gallery/MCP indexing'); not a 5 because it lacks synonym/extension variations beyond '.py'.

4 / 5

Distinctiveness Conflict Risk

Highly specific niche ('Flet example projects', 'Gallery/MCP indexing', 'flat .py files') with distinct triggers and minimal overlap risk with other skills.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
flet-dev/flet
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.