CtrlK
BlogDocsLog inGet started
Tessl Logo

flet-deprecation

Use when adding or changing deprecations for Python controls/APIs in sdk/python/packages/, including V.deprecated fields, deprecated decorators, version lifecycle, and docs admonitions/labels.

74

Quality

92%

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

100%

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

The body is a lean, highly actionable deprecation playbook with concrete code, an exact audit command, and clearly sequenced workflows that include human-approval checkpoints for destructive batch removals. Organization and cross-skill references are clean.

DimensionReasoningScore

Conciseness

Dense, Flet-specific content with no padding and no explanation of concepts Claude already knows; every section (decision order, runtime contract, patterns, pitfalls) earns its place, matching the lean/efficient anchor rather than the 'could be tightened' level 2.

3 / 3

Actionability

Provides four executable code patterns, an exact `rg` audit command with a complete regex, concrete file paths, and a copy-paste commit message format, which is fully executable rather than the pseudocode/abstract level 2.

3 / 3

Workflow Clarity

The Target Release Audit and Release Docs Updates are clearly sequenced with explicit human-approval validation gates ('ask the human for approval before editing') for batch/destructive removals, so the destructive-operation cap at 2 does not apply.

3 / 3

Progressive Disclosure

Well-organized into clearly headed sections with well-signaled one-level cross-skill references (flet-validation, docs-conventions); no bundle files exist to misroute, and the core content is appropriately kept inline.

3 / 3

Total

12

/

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.

The description is specific, complete, and clearly niche-scoped with an explicit 'Use when' trigger. Its main weakness is trigger-term quality: it leans on technical jargon over the natural phrasings a user would actually say.

Suggestions

Include natural-language trigger variants users would say (e.g., 'mark as deprecated', 'add a deprecation warning', 'remove deprecated API') alongside the technical terms.

Lead with the plain action before the scope list so the natural trigger reads first and the technical details follow it.

DimensionReasoningScore

Specificity

Lists concrete actions ('adding or changing deprecations') plus specific items (V.deprecated fields, deprecated decorators, version lifecycle, docs admonitions/labels), matching the 'multiple specific concrete actions' anchor rather than the domain-only level 2.

3 / 3

Completeness

Explicitly answers both what (deprecating Python controls/APIs and the components involved) and when, opening with an explicit 'Use when adding or changing deprecations' trigger clause, so it is not capped at 2.

3 / 3

Trigger Term Quality

The core term 'deprecation/deprecated' appears, but most of the description is technical jargon (V.deprecated, decorators, admonitions) and it omits common natural phrasings like 'mark as deprecated' or 'remove deprecated API'. It is above level 1 (which has no natural keywords) but below level 3's broad natural-term coverage.

2 / 3

Distinctiveness Conflict Risk

Narrowly scoped to deprecations in sdk/python/packages/ with a clear niche, and the body explicitly routes non-deprecation validation to flet-validation, making wrong-skill triggering unlikely.

3 / 3

Total

11

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 6 suspicious

Warning

Total

15

/

16

Passed

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.