CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

microsoft-maui-controls-upgrade-to-11

Upgrade a .NET MAUI Controls application to .NET MAUI 11, including SDK/workload and package alignment, version-specific handler customization, and behavior-preserving validation.

Quality

85%

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

92%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 instruction-only skill body: dense, non-redundant upgrade guidance with a clear phased workflow, explicit verification steps, and clean one-level reference structure. The only gap is the absence of exact build/restore command lines, which keeps actionability just below fully executable.

DimensionReasoningScore

Conciseness

The body is lean and directive throughout — no basic-concept explanations (nothing explains what MAUI or handlers are), and every sentence carries upgrade-specific guidance such as 'Check `dotnet --info` and `dotnet workload list`' and 'a recognized suffixed TFM is not inherently an error'. Anti-drift check against anchor 4: there are no instances of over-explanation that could be trimmed, so the anchor-5 fit holds.

5 / 5

Actionability

Concrete, executable guidance dominates: named files to read ('`global.json`, project files, `Directory.Build.props`, `Directory.Packages.props`'), concrete commands ('dotnet --info', 'dotnet workload list'), and specific behavioral test steps ('open a route, perform its actions, navigate back using both app chrome and system navigation'). Falls short of anchor 5 because exact build/restore command lines per platform are absent, leaving minor gaps in copy-paste-ready coverage.

4 / 5

Workflow Clarity

Clear four-phase sequence (establish source/target → reconcile packages → review native customization → verify the delivered application) with explicit validation checkpoints: baseline build first ('Establish a working MAUI 10 build and runnable baseline'), verify against the exact package ('Verify the evaluated project and fresh restore graph'), and 'Restore and build Debug and Release for every claimed platform'. Error-recovery guidance is present ('report missing prerequisites', 'Classify SDK/Xcode mismatch... as infrastructure'), matching the anchor-5 example's validate-and-report structure rather than the minor-gaps anchor 4.

5 / 5

Progressive Disclosure

The 91-line body is an overview with four well-signaled, one-level-deep references ([upgrade checklist], [mobile runtime property reference], [UIKit scene lifecycle reference], [Android Shell reference]), each linked at its point of relevance with a summary of what it contains; all four files exist in references/ and contain no nested references. This matches anchor 5 (clear overview, appropriately split, easy navigation) and is clearly above anchor 4.

5 / 5

Total

19

/

20

Passed

Description

70%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, distinctive description that clearly states what the skill does within a well-defined niche, weakened only by the absence of an explicit 'Use when...' trigger clause and a few natural synonyms like 'migrate'. Third-person voice is used correctly and no fluff or over-claims are present.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to upgrade or migrate a .NET MAUI Controls application to MAUI 11 / .NET 11', to raise completeness above the cap of 3.

Include natural synonyms such as 'migrate'/'migration' and '.NET 11 upgrade' alongside 'upgrade' to broaden trigger-term coverage toward anchor 5.

DimensionReasoningScore

Specificity

States the core action ('Upgrade a .NET MAUI Controls application to .NET MAUI 11') and lists several specific capability areas ('SDK/workload and package alignment, version-specific handler customization, and behavior-preserving validation'). Not anchor 5 because the areas are noun phrases rather than multiple fully spelled-out concrete actions, but clearly above anchor 3's '1-2 concrete actions'.

4 / 5

Completeness

The 'what' is clear and concrete (upgrade a MAUI Controls app to MAUI 11 with the listed sub-areas), but there is no 'Use when...' clause or equivalent explicit trigger guidance in the description — the trigger sentence exists only in the body. Per the judging guideline this caps completeness at 3; it is not 4 because 'when' is entirely absent rather than merely implicit-but-present.

3 / 5

Trigger Term Quality

Good natural keyword coverage for the niche: 'upgrade', '.NET MAUI', 'MAUI 11', 'Controls', 'SDK', 'workload', 'package' — phrases a user with this need would naturally say. A few natural terms are missing (e.g., 'migrate'/'migration', '.NET 11'), so it sits at anchor 4 rather than the comprehensive-synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche with distinct triggers: '.NET MAUI Controls application' + '.NET MAUI 11' + version-specific terms ('handler customization', 'SDK/workload') make confusion with other skills very unlikely. Matches anchor 5 and is clearly above the minor-overlap anchor 4.

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

dotnet/maui

Path

src/Controls/src/NuGet/skills/microsoft-maui-controls-upgrade-to-11/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.