CtrlK
BlogDocsLog inGet started
Tessl Logo

write-xaml-tests

Creates XAML unit tests for GitHub issues in the Controls.Xaml.UnitTests project. Tests XAML parsing, compilation (XamlC), and source generation. Use when testing XAML-specific behavior, not UI interactions.

80

Quality

100%

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.

A tight, actionable skill body: concrete build/test commands, an explicit verification workflow, and clean one-level-deep reference to the conventions file. No verbosity or redundant concept explanations.

DimensionReasoningScore

Conciseness

Lean body with no concept explanations Claude already knows (no 'what is XAML' preamble); every section (When to Use, Required Input, Workflow, Output) earns its place.

3 / 3

Actionability

Provides fully executable commands ('dotnet build ... -c Debug --no-restore -v q', 'dotnet test ... --filter ... --no-build') with specific paths and a copy-paste output template.

3 / 3

Workflow Clarity

Four clearly sequenced steps with explicit verification checkpoints (Step 3 'Verify Tests Compile and Run', Step 4 'Verify Test Behavior' with expected PASS/FAIL outcomes); the task is test creation, not destructive/batch work, so the feedback-loop cap does not apply.

3 / 3

Progressive Disclosure

No bundle files exist; the body is a well-organized overview that points one level deep to the authoritative conventions file (`.github/instructions/xaml-unittests.instructions.md`), clearly signaled in Step 1 and the References section.

3 / 3

Total

12

/

12

Passed

Description

100%

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, well-targeted description that names concrete capabilities, supplies an explicit 'Use when' trigger, and cleanly distinguishes itself from UI-testing skills. No fluff, third-person voice, and within a reasonable length.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Tests XAML parsing, compilation (XamlC), and source generation') rather than vague language, matching the score-3 anchor.

3 / 3

Completeness

Explicitly states both what it does ('Creates XAML unit tests... Tests XAML parsing, compilation (XamlC), and source generation') and when to use it via an explicit 'Use when testing XAML-specific behavior, not UI interactions' clause.

3 / 3

Trigger Term Quality

Covers natural domain terms a user would say ('XAML unit tests', 'XamlC', 'source generation', 'UI interactions') with good variation; not merely generic jargon.

3 / 3

Distinctiveness Conflict Risk

Clear niche (XAML unit tests in a specific project) with an explicit contrast against UI-interaction testing, making conflict with sibling skills unlikely.

3 / 3

Total

12

/

12

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
dotnet/maui
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.