Content
75%Weight 40%Scale 1-5Reviews 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 with executable commands, real bundled-script references, and useful troubleshooting feedback loops. Its main weakness is redundancy across the Scripts/Examples/Filtering sections and the absence of an explicit post-run validation checkpoint.
Suggestions
Consolidate the largely duplicated command lists in 'Scripts' and 'Examples' into a single section to remove redundancy and improve token efficiency.
Add an explicit post-run verification step in the Workflow (e.g., check the xUnit result summary in artifacts/log and confirm pass count before declaring success).
Move the detailed xharness invocation reference and the full category list into a separate reference file linked from SKILL.md to strengthen progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient and assumes Claude's competence (no padding about what MAUI or xharness is), but the same invocations are repeated across the 'Scripts', 'Examples', and 'Test Filtering' sections, and the 'Examples' section largely duplicates 'Scripts'; this redundant verbosity fits the 'mostly efficient but could be tightened' anchor rather than a 4. | 3 / 5 |
Actionability | It provides copy-paste-ready, fully executable pwsh/xharness commands with real parameter values verified against the bundled Run-DeviceTests.ps1 (Project, Platform, iOSVersion, TestFilter, BuildOnly, SkipXcodeVersionCheck all exist), plus concrete xharness invocation examples and troubleshooting commands, matching the 'fully executable; copy-paste ready' anchor. | 5 / 5 |
Workflow Clarity | The Workflow section gives a clear two-step sequence and the Troubleshooting/Test Filtering sections supply feedback loops (rebuild, check console output, verify category), aligning with 'clear sequence with most checkpoints present'; it is not a 5 because there is no explicit pass/fail verification checkpoint after a test run before declaring success. | 4 / 5 |
Progressive Disclosure | Structure is good with clear section headers and references to real bundle files one level deep (Run-DeviceTests.ps1, Start-Emulator.ps1, shared-utils.ps1) plus inline source paths; however most detail (full xharness invocations, filter syntax, category lists) is inlined in SKILL.md rather than split into separate reference files, so it sits at 'good structure; minor organization gaps' rather than 5. | 4 / 5 |
Total | 16 / 20 Passed |