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.

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

88%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 well-structured, actionable skill body with executable patterns and a genuinely gated release-audit workflow. The main gap is the absence of bundle/reference files, leaving detailed patterns inlined in SKILL.md.

Suggestions

Consider extracting the four deprecation code patterns into a references/ file (e.g. patterns.md) and summarizing them inline to improve progressive disclosure.

Tighten 'reason vs docs_reason' and 'Common Pitfalls' where guidance overlaps with the Authoring Rules to lift conciseness.

Add a short pointer at the top to the Source Of Truth files so the runtime contract is discoverable before the detailed patterns.

Dimension	Reasoning	Score
Conciseness	The body is dense and Flet-specific with no padding of concepts Claude already knows; below 5 because a few sections (e.g. 'reason vs docs_reason' and 'Common Pitfalls') overlap slightly and could be tightened.	4 / 5
Actionability	Copy-paste-ready code patterns for field/method/class/property deprecations, exact file paths, a runnable ripgrep command, build commands, and a commit-message format cover the common cases fully.	5 / 5
Workflow Clarity	The 'Target Release Audit' section sequences scan -> summarize -> human approval -> decide -> edit -> summarize diff -> approval -> grouped commit, with explicit validation/approval checkpoints for destructive batch removals.	5 / 5
Progressive Disclosure	Content is organized into clear headed sections with one-level cross-skill links ([flet-validation], [docs-conventions]) and no nested references; below 5 because no bundle files exist and the code patterns are inlined rather than split out.	4 / 5
	Total	18 / 20 Passed

Description

87%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 precise, well-scoped description that answers both what and when with concrete enumerated surfaces and an explicit trigger clause. Minor synonym/variation breadth keeps trigger-term quality just below the top anchor.

Dimension	Reasoning	Score
Specificity	Concrete verbs 'adding or changing' are paired with enumerated targets ('V.deprecated fields, deprecated decorators, version lifecycle, and docs admonitions/labels'); below 5 because only two verbs drive the actions, above 3 due to multiple specific enumerated items.	4 / 5
Completeness	Explicit 'Use when adding or changing deprecations...' trigger plus a clear 'what' (deprecations across V.deprecated fields, decorators, version lifecycle, docs) answer both what and when with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural terms like 'deprecations', 'Python controls/APIs', and 'docs admonitions/labels' map to what a user would say; below 5 because it lacks synonym breadth and common variations.	4 / 5
Distinctiveness Conflict Risk	Scoped to deprecations in 'sdk/python/packages/' for Python controls/APIs is a clear niche with distinct triggers and minimal conflict risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 6 suspicious	Warning

	Total	15 / 16 Passed

Repository: flet-dev/flet
Path: .agents/skills/flet-deprecation/SKILL.md
Commit: 8f74fe9

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