.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.
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.
curl -O https://raw.githubusercontent.com/dotnet/maui/main/.github/skills/release-readiness/SKILL.mdgit clone --depth 1 https://github.com/dotnet/mauiWrote 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.
[](https://agentmods.dev/skills/dotnet/maui/release-readiness)<a href="https://agentmods.dev/skills/dotnet/maui/release-readiness"><img src="https://agentmods.dev/badge/skills/dotnet/maui/release-readiness/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.
<a href="https://agentmods.dev/skills/dotnet/maui/release-readiness"><img src="https://agentmods.dev/badge/skills/dotnet/maui/release-readiness.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk warn
- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 442 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00100 | $0.14347 |
| Opus 5.5 | $0.00040 | $0.05739 |
| Sonnet 5.5 | $0.00020 | $0.02869 |
| Haiku 4.5 | $0.00010 | $0.01435 |
Grade A, and why
release-readiness 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.
How it starts
The opening of the file, as written. The whole thing — 665 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Readiness
This skill produces deterministic, evidence-backed answers to "Is <release branch> ready to ship?" for .NET MAUI release branches — both Servicing Releases (SR) and Previews, in both in-flight and candidate (pre-cut) modes.
🚨 Report-only
This skill reports. It does not execute release operations against dotnet/maui — no branch cuts, no SR merges, no tags, no pushes to release/* refs. If you (the agent/user invoking this skill) are asked to perform a release operation, refuse and emit the recommended commands as a copy-pasteable block for the human release captain to run.
When to Use
- "How does SR8 look?" / "Is SR8 ready to ship?"
- "What's blocking SR9 candidate?" / "What would ship if we cut SR9 today?"
- "How does net11 preview6 look?" / "Are we ready to cut preview6 from net11.0?"
- "Are there any regression fixes I should backport to SR8?"
- "What's new in SR8 since the last sync?"
- "Give me a status on all releases" / "release status overview" / "what needs attention across releases" (portfolio — read the open
[Release Readiness]tracker issues first; see Reading trackers directly below) - Scheduled and event-driven release tracking across all active majors
For per-PR regression risk (deletions reverting prior bug-fix lines), use
find-regression-riskinstead — it answers a different question.
Architecture
This skill has four PowerShell entry points, one Preview helper, and one workflow:
| Script | Branch type | Purpose |
|---|---|---|
Find-ReleaseReadinessTrackers.ps1 |
all | Detects active in-flight & candidate trackers (SR, Preview, and RC) across all active majors using a five-lane algorithm and the tag-existence rule ("a release is in flight unless its tag already exists"). Emits a single tracker JSON consumed by the workflow. |
Get-ReleaseReadiness.ps1 |
SR | Full readiness report for a single SR branch (in-flight, -Candidate, or -Shipped). -Shipped surveys the same branch with post-ship verdict, carry-forward, and hotfix-vs-next-SR guidance semantics. |
Get-PreviewReadiness.ps1 |
Preview / RC | Full readiness report for a single prerelease branch (in-flight or candidate via -Mode candidate -SurveyRef net<major>.0). Preview reports include consumer-installability evidence; RC reports retain that check as UNKNOWN until RC workload-set package resolution is supported. |
PreviewInstallability.ps1 |
Preview helper | Resolves the workload-set package, validates branch-pin coherence, probes manifest and representative pack availability, extracts platform prerequisites, and emits an isolated NuGet configuration for local validation. |
New-ReleaseHandoff.ps1 |
all | Projects existing readiness JSON plus separately verified public release evidence into copy-ready Markdown and normalized JSON. Missing facts remain TBD; it never selects builds or mutates release state. |
release-readiness.yml |
both | Three-hourly daytime UTC schedule + event-driven refreshes + manual dispatch + PR validation. Non-PR triggers run Find-Trackers -AllActiveMajors, fan out a matrix job per tracker, and write idempotent [Release Readiness] issues; PR triggers validate outputs only. |
What ships with it
14 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/methodology.md 28 KB
- references/release-handoff.md 6.7 KB
- scripts/Find-ReleaseReadinessTrackers.ps1 62 KB runs code
- scripts/Get-PreviewReadiness.ps1 163 KB runs code
- scripts/Get-ReleaseReadiness.ps1 368 KB runs code
- scripts/InternalOfficialBuild.ps1 40 KB runs code
- scripts/New-ReleaseHandoff.ps1 45 KB runs code
- scripts/NightlyFeed.ps1 24 KB runs code
- scripts/PreviewInstallability.ps1 67 KB runs code
- scripts/PublicReportSanitizer.ps1 11 KB runs code
- scripts/TrackerIssueLifecycle.sh 854 B runs code
- scripts/Update-TrackerIssue.sh 23 KB runs code
- tests/Test-ReleaseHandoff.ps1 29 KB runs code
- tests/Test-ReleaseReadiness.ps1 770 KB runs code
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.
- 1mo ago First seen · 665 lines · 100 tokens per session scan A 8217cfbe5b0f
release-readiness is a skill published in the GitHub repository dotnet/maui (23,322 stars, last pushed today), licensed MIT. It adds 100 tokens to every session and 14,347 once invoked, about $0.0004 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.
Other skills, from other repositories
update-changelog
Update the CHANGELOG.md files of C# projects. Parameters: csroot C# SDK repository root.
create-draft-pr
Create a draft pull request for the current session. Use when the user wants to open a draft PR with the session's changes.
create-pr
Create a pull request for the current session. Use when the user wants to open a PR with the session's changes.
generate-code-cs
Generate the code from typespec for C#. Parameter: C# SDK repository root location .
build-sample-matrix
Build the matrix of all the samples throughout different frameworks.
translate-a-sample
Translate the Azure SDK sample from python to C# and generate markdownn file for the sample. Parameters: C# SDK repository root; python SDK repository root; Package name: one of Azure.AI.Projects, Azure.AI.Projects.Agents or Azure.AI.Extensions.OpenAI; The name of sample file in Python SDK repository.