run-integration-tests

Build, pack, and run .NET MAUI integration tests locally. Validates templates, samples, and end-to-end scenarios using the local workload.

Quality

72%

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

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/run-integration-tests/SKILL.md

Quality

Content

75%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 highly actionable, well-structured skill body: every command is executable, parameters are tabulated, and troubleshooting covers realistic failure modes with recovery steps. The main costs are redundant sections (duplicated examples, repeated platform constraints) and a small path mismatch between the body and the actual bundle location.

Suggestions

Delete the 'Example Usage' section or fold its unique case (multi-category TestFilter) into the 'Scripts' section to remove verbatim command duplication.

State platform requirements once (the categories table already encodes them) instead of repeating them in the compatibility line and 'Prerequisites'.

Fix the script path references to match the bundle layout ('scripts/Run-IntegrationTests.ps1'), or move the iOS/sequential-run walkthroughs into a reference file to keep SKILL.md lean.

Dimension	Reasoning	Score
Conciseness	The body is mostly dense and useful (tables, commands, troubleshooting), but there is real redundancy: the 'Example Usage' section repeats two commands verbatim from the 'Scripts' section, and platform requirements are stated three times (compatibility frontmatter, categories table, prerequisites). It is not a 4 because the duplication is structural rather than a couple of stray sentences.	3 / 5
Actionability	Fully executable, copy-paste-ready pwsh commands throughout, a complete parameter table with defaults, concrete test names (e.g., 'RunOniOS_MauiDebug'), and exact recovery commands for locked folders and simulator errors. Specific examples cover the common cases.	5 / 5
Workflow Clarity	A clear 4-step workflow with concrete commands, an explicit provisioning verification block ('ls .dotnet/dotnet'), and a rich troubleshooting table with error-recovery feedback loops. Not a 5 because the main test-run workflow lacks an explicit validation checkpoint that build/install succeeded before running tests, relying on the script's internal behavior.	4 / 5
Progressive Disclosure	Well-sectioned with headers, tables, and a single bundle script (scripts/Run-IntegrationTests.ps1) that is referenced by path from the body, so everything is one level deep. Not a 5 because the body references the script under '.github/skills/run-integration-tests/scripts/' rather than the bundle's actual 'scripts/' location, and the iOS/sequential-run sections could live in a reference file.	4 / 5
	Total	16 / 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, third-person description with concrete actions in a well-defined niche. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness and leaves natural trigger terms underrepresented.

Suggestions

Add an explicit trigger clause, e.g.: 'Use when the user asks to run MAUI integration tests locally, test templates or samples, or validate end-to-end template scenarios.'

Include common user phrasings as trigger terms, such as 'run tests', 'test templates locally', or 'validate the MAUI build', to improve natural keyword coverage.

Mention the ability to run specific test categories (e.g., WindowsTemplates, Samples, Blazor, RunOniOS) to close the remaining specificity gap.

Dimension	Reasoning	Score
Specificity	Names the domain (.NET MAUI integration tests) and lists several concrete actions ('Build, pack, and run', 'Validates templates, samples, and end-to-end scenarios') in third person. Falls short of 5 because coverage has minor gaps (e.g., running specific test categories or filters is not mentioned).	4 / 5
Completeness	The 'what' is clear and concrete (build, pack, run, validate), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines. It is not a 2 because the 'what' is specific, not vague.	3 / 5
Trigger Term Quality	Good natural keyword coverage: '.NET MAUI integration tests', 'templates', 'samples', 'end-to-end scenarios'. A few natural terms users would say are missing, such as 'run tests', 'test templates locally', or 'MAUI tests', so it does not reach comprehensive anchor 5.	4 / 5
Distinctiveness Conflict Risk	The description occupies a clear niche (local .NET MAUI integration test validation via the local workload) with distinct triggers ('MAUI', 'integration tests', 'templates'), so conflict with other skills is minimal.	5 / 5
	Total	16 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: dotnet/maui
Path: .github/skills/run-integration-tests/SKILL.md
Commit: 7a5a5d6

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.