maui: Skill for Claude Code

.github/skills/write-ui-tests/SKILL.md

write-ui-tests is a skill for Claude Code, Codex from dotnet/maui. It costs 48 tokens per session (2,882 once invoked), scanned A, original, MIT.

A testing workflow for creating user-interface tests that reproduce a GitHub issue in .NET MAUI, a framework for building apps across platforms.

In plain words
What is it for?
Use it to add missing tests, check that an issue has a working reproduction, and improve tests that do not adequately cover the problem.
Why use it?
It prevents a test from being declared useful when it passes without detecting the reported bug.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

This is dotnet/maui's own configuration. It tells Claude Code and Codex how to work on maui itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything maui configures →

About the project

.NET MAUI is a C# and XAML framework for building native mobile and desktop applications from one shared codebase. Developers use it to create apps for Android, iOS, iPadOS, macOS, and Windows. The catalogue entries provide skills, instructions, and agents for working with .NET MAUI.

dotnet/maui · 23,322 stars · on GitHub · dot.net

Reuse

Borrowing it

Nothing to install: this file belongs to dotnet/maui. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/dotnet/maui/main/.github/skills/write-ui-tests/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/dotnet/maui

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for write-ui-tests

README.md
[![agentmods](https://agentmods.dev/badge/skills/dotnet/maui/write-ui-tests/github.svg)](https://agentmods.dev/skills/dotnet/maui/write-ui-tests)
Your own site
<a href="https://agentmods.dev/skills/dotnet/maui/write-ui-tests"><img src="https://agentmods.dev/badge/skills/dotnet/maui/write-ui-tests/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for write-ui-tests

Your own site · 80×15
<a href="https://agentmods.dev/skills/dotnet/maui/write-ui-tests"><img src="https://agentmods.dev/badge/skills/dotnet/maui/write-ui-tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,882 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Snyk warn 7 Sept 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00048 $0.02882
Opus 5.5 $0.00019 $0.01153
Sonnet 5.5 $0.00010 $0.00576
Haiku 4.5 $0.00005 $0.00288

Measured 1mo ago against content hash 5ecf3539acb1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

write-ui-tests scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.github/skills/write-ui-tests/SKILL.md · 326 lines

How it starts

The opening of the file, as written. The whole thing — 326 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Write UI Tests Skill

Creates UI tests that reproduce a GitHub issue, following .NET MAUI conventions. Verifies the tests actually fail before completing.

🛑 BLOCKING REQUIREMENT

YOU CANNOT COMPLETE THIS SKILL UNTIL TESTS FAIL.

A test that passes does NOT prove it catches the bug. You MUST:

  1. Run tests and observe them FAIL
  2. If tests pass, iterate on test code until they fail
  3. Never report "done" with passing tests

If tests keep passing after 3 iterations:

  • STOP and ask user: "Tests are passing but they should fail to prove they catch the bug. The test scenario may not correctly reproduce the issue. Should I try a different approach?"

Common mistakes that lead to passing tests:

  • Test scenario doesn't match issue reproduction steps
  • Checking wrong element or property
  • Bug only manifests on specific platform (try different platform)
  • Bug requires specific timing or async behavior not captured
  • Issue description is incomplete - may need to ask user for clarification

When to Use

  • ✅ PR has no tests and needs them
  • ✅ Issue needs a reproduction test before fixing
  • ✅ Existing tests don't adequately cover the bug

Required Input

Before invoking, ensure you have:

  • Issue number (e.g., 33331)
  • Issue description or reproduction steps
  • Platforms affected (iOS, Android, Windows, MacCatalyst)

Platform selection guidance:

  • Start with the platform mentioned in the issue (often in title or labels)
  • If issue says "iOS" or has platform/iOS label → test on iOS first
  • If issue says "Android" or has platform/Android label → test on Android first
  • If issue affects "All" platforms → start with Android (faster emulator boot)
  • If test passes on one platform, try another before concluding test is wrong

Workflow

Step 1: Read the UI Test Guidelines

cat .github/instructions/uitests.instructions.md

This contains the authoritative conventions for:

  • File naming (IssueXXXXX.cs for C#-only, or IssueXXXXX.xaml/.xaml.cs for XAML)
  • File locations (TestCases.HostApp/Issues/, TestCases.Shared.Tests/Tests/Issues/)
  • Required attributes ([Issue()], [Category()])
  • Test patterns and assertions

Read the full file on GitHub · 326 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 326 lines · 48 tokens per session scan A 5ecf3539acb1

Subscribe to this mod's changes

write-ui-tests is a skill published in the GitHub repository dotnet/maui (23,322 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 2,882 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.