run-helix-tests

Submit and monitor .NET MAUI unit tests on Helix infrastructure. Supports running XAML, Resizetizer, Core, Essentials, and other unit test projects on distributed Helix queues.

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

68%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.

The content is highly actionable with concrete commands and well-signaled external scripts, but it loses points on duplicated command listings and a missing validation feedback loop for this batch operation. Tightening the redundancy and adding an explicit checkpoint would raise the weaker dimensions.

Suggestions

Collapse the duplication between the Scripts section and the Workflow section so each command appears once, with the workflow cross-referencing the script invocations.

Add an explicit validation checkpoint and feedback loop, e.g. after monitoring: "If failures: retrieve -FailedOnly logs, diagnose, then re-submit only affected queues" — this addresses the batch-operation cap on workflow_clarity.

Consider moving the test-project and queue reference tables into a separate references/ file so the SKILL.md body stays a lean overview pointing to detail.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands and reference tables without concept padding, but the Workflow section restates the same Submit/Get-HelixJobStatus/Get-HelixWorkItemLog commands already shown in the Scripts section, creating noticeable duplication. Merging these would tighten it toward anchor 4.	3 / 5
Actionability	Provides fully executable, copy-paste-ready pwsh commands with concrete flags (-Configuration, -Queue, -JobId, -Wait, -FailedOnly, -WorkItem) and covers the common submit/monitor/log cases. Specific examples span the typical workflow end-to-end.	5 / 5
Workflow Clarity	The submit → monitor → check-failures sequence is present, but submitting to distributed queues is a batch operation with no explicit validate→fix→retry checkpoint, so workflow clarity is capped at 3 per the rubric guideline. The verification step is implicit rather than a hard feedback loop.	3 / 5
Progressive Disclosure	Scripts are externalized into ./scripts/ (three real files confirmed) and clearly signaled with full paths, with one-level-deep references and well-organized sections. It does not reach anchor 5 because the compact test-project/queue tables and result URLs are inlined rather than split into reference files.	4 / 5
	Total	15 / 20 Passed

Description

66%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.

The description is specific and domain-distinctive with good trigger keywords, but it lacks an explicit "Use when..." trigger clause, which caps its completeness. Adding a concrete trigger-phrase sentence would lift the weakest dimension.

Suggestions

Add an explicit "Use when..." clause with concrete trigger phrases, e.g. "Use when the user asks to run or validate MAUI unit tests on Helix, or to debug Helix unit-test failures."

Include natural verb phrasing like "run tests on Helix" to match what users actually say and broaden trigger-term coverage toward anchor 5.

Briefly note the distinction from device tests (helix_xharness.proj) in the description to further reduce conflict risk with the sibling skill.

Dimension	Reasoning	Score
Specificity	"Submit and monitor .NET MAUI unit tests on Helix infrastructure" names two concrete actions, and the enumeration of "XAML, Resizetizer, Core, Essentials, and other unit test projects" adds concrete scope. It falls short of anchor 5 because the action set is limited to submit/monitor rather than a comprehensive list of operations.	4 / 5
Completeness	The "what" is clear (submit and monitor unit tests on Helix), but there is no "Use when..." clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guideline. The "when" is only weakly implied by the domain language.	3 / 5
Trigger Term Quality	Includes natural terms users would say ("Helix", "unit tests", ".NET MAUI") plus project-name synonyms (XAML, Resizetizer, Core, Essentials). It misses common variations like "run tests" and platform phrasing, keeping it just below anchor 5.	4 / 5
Distinctiveness Conflict Risk	The niche is clear and specific (".NET MAUI unit tests on Helix infrastructure"), and "unit test projects" distinguishes it from device tests. Minor overlap risk remains with a sibling device-test skill, so it does not reach the minimal-conflict anchor 5.	4 / 5
	Total	15 / 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-helix-tests/SKILL.md
Commit: 90afade

Reviewed: ~18 hours 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.