- History HygieneRecord final outcomes to history.md, not intermediate requests or reversed decisionsdotnet/maui-labs179
- History HygieneRecord final outcomes to history.md, not intermediate requests or reversed decisionsdotnet/maui-labs179
- HumanizerTone enforcement patterns for external-facing community responsesdotnet/maui-labs179
- HumanizerTone enforcement patterns for external-facing community responsesdotnet/maui-labs179
- Init ModeTeam initialization flow (Phase 1 proposal + Phase 2 creation)dotnet/maui-labs179
- Init ModeTeam initialization flow (Phase 1 proposal + Phase 2 creation)dotnet/maui-labs179
- Ios Slim BindingsCreate and update slim/native platform interop bindings for iOS in .NET MAUI and .NET for iOS projects. Guides through creating Swift/Objective-C wrappers, configuring Xcode projects, generating C# API definitions, and integrating native iOS libraries using the Native Library Interop (NLI) approach. USE FOR: iOS bindings, xcframework integration, Swift interop, Objective Sharpie, bridging native iOS SDKs to .NET. DO NOT USE FOR: Android bindings (use android-slim-bindings), general MAUI app devedotnet/maui-labs179
- Maui Ai DebuggingLegacy end-to-end workflow for building, deploying, inspecting, and debugging .NET MAUI and MAUI Blazor Hybrid apps with `maui devflow`. USE FOR: older clients that still request `maui-ai-debugging`, app launch, visual tree inspection, screenshots, Blazor WebView CDP debugging, simulator/emulator management, and build-deploy-inspect-fix loops. DO NOT USE FOR: new DevFlow setup when `maui-devflow-onboard` or `maui-devflow-debug` are available, generic desktop automation, AppleScript macros, or hodotnet/maui-labs179
- Maui Devflow DebugRun build, deploy, inspect, and fix loops for .NET MAUI apps that already have MAUI DevFlow integrated. USE FOR: launching MAUI apps, selecting devices or emulators, waiting for or recovering agent connections, broker/port/adb connectivity issues, visual tree inspection, screenshots, UI interaction, Blazor WebView CDP debugging, reading DevFlow logs, and iterative app debugging. DO NOT USE FOR: first-time DevFlow package setup (use maui-devflow-onboard), or generic desktop automation unrelated tdotnet/maui-labs179
- Maui Devflow OnboardAdd MAUI DevFlow to a .NET MAUI project with agent package references, MauiProgram.cs registration, Blazor WebView support, GTK variants, Central Package Management guidance, and verification commands. USE FOR: first-time DevFlow setup, reviewing what files to edit, choosing DevFlow packages, or continuing after `maui devflow init` installs skills. DO NOT USE FOR: troubleshooting an already-integrated app that cannot connect, iterative app debugging, UI inspection, or generic MAUI build failuresdotnet/maui-labs179
- Maui Devflow Session ReviewReview previous AI sessions that used MAUI DevFlow to identify opt-in product feedback, friction, repeated attempts, failed advertised features, and workarounds. USE FOR: MAUI DevFlow session review, stuck maui devflow debugging sessions, reviewing CLI/MCP behavior for friction, markdown feedback reports, filing dotnet/maui-labs GitHub issues. DO NOT USE FOR: fixing discovered bugs, adding DevFlow to apps (use maui-devflow-onboard), iterative app debugging (use maui-devflow-debug), or generic medotnet/maui-labs179
- Maui Platform BackendGuide .NET MAUI backend implementation for new platforms (GTK, AppKit, Avalonia, TUI, etc.) in the dotnet/maui-labs repository. USE FOR: creating a new MAUI backend, implementing a control handler, adding Essentials services, setting up build targets, scaffolding project structure, debugging handler rendering with DevFlow. DO NOT USE FOR: building or running existing MAUI apps (use maui-devflow-debug skill), DevFlow CLI/MCP tool development (see AGENTS.md). INVOKES: GitHub MCP tools for referencdotnet/maui-labs179
- Project ConventionsCore conventions and patterns for this codebasedotnet/maui-labs179
- Project ConventionsCore conventions and patterns for this codebasedotnet/maui-labs179
- Release ProcessStep-by-step release checklist for Squad — prevents v0.8.22-style disastersdotnet/maui-labs179
- Release ProcessStep-by-step release checklist for Squad — prevents v0.8.22-style disastersdotnet/maui-labs179
- ReskillTeam-wide charter and history optimization through skill extractiondotnet/maui-labs179
- ReskillTeam-wide charter and history optimization through skill extractiondotnet/maui-labs179
- Reviewer ProtocolReviewer rejection workflow and strict lockout semanticsdotnet/maui-labs179
- Reviewer ProtocolReviewer rejection workflow and strict lockout semanticsdotnet/maui-labs179
- Secret HandlingNever read .env files or write secrets to .squad/ committed filesdotnet/maui-labs179
- Secret HandlingNever read .env files or write secrets to .squad/ committed filesdotnet/maui-labs179
- Session RecoveryFind and resume interrupted Copilot CLI sessions using session_store queriesdotnet/maui-labs179
- Session RecoveryFind and resume interrupted Copilot CLI sessions using session_store queriesdotnet/maui-labs179
- Squad ConventionsCore conventions and patterns used in the Squad codebasedotnet/maui-labs179
- Squad ConventionsCore conventions and patterns used in the Squad codebasedotnet/maui-labs179
- Test DisciplineUpdate tests when changing APIs — no exceptionsdotnet/maui-labs179
- Test DisciplineUpdate tests when changing APIs — no exceptionsdotnet/maui-labs179
- Verification ProtocolMandatory end-to-end verification for .NET MAUI and Comet app tasks. Enforces dependency ownership — broken tools and missing config are YOUR problem to fix, not blockers to report. USE FOR: any task touching UI, pages, navigation, services, or app behavior. Triggers: after code changes, before marking todos done, when reporting task results, when a tool fails. DO NOT USE FOR: documentation-only changes, squad config edits, or build system changes that don't affect the running app.dotnet/maui-labs179
- Windows CompatibilityCross-platform path handling and command patternsdotnet/maui-labs179
- Windows CompatibilityCross-platform path handling and command patternsdotnet/maui-labs179
- Investigating PipelineDiagnoses a single Azure Pipelines build. Shows the build timeline tree with stages, jobs, and task results, and retrieves task logs for debugging failures. Use when a user provides a build ID or Azure DevOps build URL and wants to understand what failed and why.dotnet/docker-tools177
- Investigating Pull RequestInspect GitHub pull request status, read review comments, and diagnose PR validation failures. Use when the user wants to check the status of a pull request or diagnose PR validation failures.dotnet/docker-tools177
- Triaging PipelinesTriage recent Azure Pipelines runs and failures.dotnet/docker-tools177
- Triaging Pull RequestsTriage open pull requests into actionable categories.dotnet/docker-tools177
- Add Darc CommandAdd a new command (verb) to the DARC CLI. Use when asked to "add a darc command", "create a new darc verb", "add a darc operation", or extend the darc tool with a new subcommand.dotnet/arcade-services83
- Setup Dev EnvironmentSet up an arcade-services local development environment from zero by following docs/DevGuide.md. Use when asked to "set up my dev environment", "bootstrap local development", "get me running locally", or "configure the repo for local dev". Runs the automatable steps, verifies prerequisites, and flags the human-gated ones.dotnet/arcade-services83
- Cleanup Unreferenced PackagesIntelligently removes unreferenced packages from source-build-assets (SBA). Accounts for pending-uptake packages, dependency graphs, and flow timing between SBA and the VMR.dotnet/source-build-assets53
- Android Tools ReviewerReview pull requests for dotnet/android-tools using lessons from past code reviews. Trigger when the user says "review this" with a GitHub PR URL, asks to review a PR, or wants code review feedback. Fetches the diff, checks it against established rules (netstandard2.0, async, security, error handling, patterns, performance), and posts a batched 🤖-prefixed review via gh CLI.dotnet/android-tools40
- Redirect ArticleDeletes a markdown article and creates a redirect entry pointing to a different article. Use when consolidating articles, renaming or moving content, removing outdated documentation, or reorganizing the docs structure while preserving existing URLs.dotnet/docs-tools25
- Sort RedirectsSorts redirect entries in Open Publishing redirection JSON files alphabetically by path. Use after adding redirects or when the file becomes unsorted.dotnet/docs-tools25
- Binlog Failure AnalysisAnalyze a failed Azure DevOps PR build by reusing the binlog that build already produced — instead of rebuilding locally. Use when an `azure-pipelines` check on a GitHub PR transitions to `failure` and you need a structured root-cause analysis posted back as a PR review. Downloads `PostBuildLogs_*` / `Logs_Build_*` from the AzDO build artifacts, invokes the `binlog` MCP server (Microsoft.AITools.BinlogMcp) for build overview / errors / warnings (with deeper diagnostic capabilities — root-cause rdotnet/arcade-skills12
- Binskim AnalysisInvestigate BinSkim SDL findings from official pipelines — understand Guardian filtering, compare raw vs merged SARIF, decode portal results, and determine fix ownership. Use when asked about SDL scan results, portal findings, Guardian filtering, rule meanings, or discrepancies between local and official results. Also use when asked "why does the portal show X", "what's filtered", "explain Guardian", "investigate SDL findings", "portal BA2008", "binskim failures in pipeline", or "what rules are dotnet/arcade-skills12
- Binskim ScanRun BinSkim binary security analysis locally against a dotnet repository. Use when asked to scan binaries, check BinSkim compliance, verify a fix for a rule violation, or run a local SDL scan. Also use when asked "run binskim", "binary security scan", "scan binaries", "check binskim", "verify my fix", "repro BA2008 locally", or "verify BA2008 fix". DO NOT USE FOR: investigating official pipeline results or portal findings (use binskim-analysis), source code analysis (use CodeQL), credential scandotnet/arcade-skills12
- Ci AnalysisAnalyze CI build and test status from Azure DevOps and Helix for dotnet repository PRs. Use when checking CI status, investigating failures, determining if a PR is ready to merge, or given URLs containing dev.azure.com or helix.dot.net. Also use when asked "why is CI red", "test failures", "retry CI", "rerun tests", "is CI green", "build failed", "checks failing", or "flaky tests". DO NOT USE FOR: investigating stale codeflow PRs or dependency update health, tracing whether a commit has flowed fdotnet/arcade-skills12
- Ci Crash DumpDownload and debug crash dumps from CI test failures in dotnet repositories. Use when a CI test crashed (not just failed), when the user wants to debug a crash dump from a PR or build, or when asked "debug dump", "download dump", "crash dump from CI", "test crashed", "analyze crash in PR", or "why did the test crash". DO NOT USE FOR: test failures that are not crashes (use ci-analysis), build failures, performance analysis, or analyzing dumps you already have locally.dotnet/arcade-skills12
- Flow AnalysisAnalyze VMR codeflow health using maestro MCP tools and GitHub MCP tools. USE FOR: investigating stale codeflow PRs, checking if fixes have flowed through the VMR pipeline, debugging dependency update issues, checking overall flow status for a repo, diagnosing why backflow PRs are missing or blocked, subscription health, build freshness, URLs containing dotnet-maestro or "Source code updates from dotnet/dotnet". DO NOT USE FOR: CI build failures (use ci-analysis skill), code review (use code-revdotnet/arcade-skills12
- Flow TracingTrace dependency flow across .NET repos through the VMR pipeline. USE FOR: checking if a PR/commit from repo A has reached repo B, finding what runtime SHA is in an SDK build, tracing dependency versions through the VMR, checking if a commit is included in an SDK build, decoding SDK version strings, "has my fix reached runtime", "did roslyn#80873 flow to runtime", "what SHA is in SDK version X", cross-repo dependency tracing, mapping SDK versions to VMR commits. DO NOT USE FOR: codeflow PR healtdotnet/arcade-skills12
- Helix InvestigationDeep-dive investigation of Helix test failures starting from AzDO build legs. USE FOR: investigating recurring Helix test failures, downloading and analyzing Helix console logs, comparing passing vs failing runs, identifying machine-specific issues, XHarness timeout analysis, Android emulator DEVICE_NOT_FOUND errors, bulk failure aggregation across legs, "why does this test fail on some machines", "top 5 failing tests in the last 2 days", "download helix logs for build X", "compare passing and fdotnet/arcade-skills12
- Known Issue HistoryAnalyze historical failure rates for Known Build Error issues by mining the edit history of issue bodies. Use when asked "when did this last fail", "failure history", "failure rate", "is this issue still active", "flaky test history", "known issue activity", or "most active known issues".dotnet/arcade-skills12
- Maestro CliQuery Maestro/BAR dependency flow data using the mstro CLI tool via bash. USE FOR: subscription health checks, build flow tracing, codeflow status, channel discovery, triggering subscription updates — when MCP tools aren't loaded or when scripting with JSON output and jq. Also use when investigating "is this subscription stale", "what's the latest build", "check backflow status". DO NOT USE FOR: tasks where maestro MCP tools are already available in context (prefer flow-analysis or flow-tracing dotnet/arcade-skills12
- Pipeline InvestigationInvestigate AzDO pipeline failures beyond Helix — build errors, infra tooling crashes, validation test flakiness, artifact cascade failures. USE FOR: "why did the unified-build fail", "what's breaking the pipeline", "how often does this failure occur", "drill into build task logs", "1ES scan failures", "SourcelinkTests flaky", "NetAnalyzers build error", analyzing AzDO build timelines and task logs, failure frequency/trend analysis. DO NOT USE FOR: Helix test failures (use helix-investigation), dotnet/arcade-skills12
- Subscription HistoryTell the history of a Maestro subscription using the darc CLI's get-subscription-history command. USE FOR: "what happened the last times this subscription ran", "show the trigger history for a subscription", "why did this subscription fail/not update", "did this subscription open a PR recently", inspecting subscription trigger outcomes (Updated, NoUpdate, NotUpdatable, Failure, UserError, HasConflict, Rescheduled), filtering outcomes by build id, date range, outcome type or free-text repo/branchdotnet/arcade-skills12
- Test ArcadeBuild the Arcade SDK from source, configure a local NuGet feed with the artifacts, and validate the build by running a test repository against the locally-built packages. Use when testing local Arcade changes against a consuming repo, validating Arcade SDK changes before merging, or verifying that a repo can build with a new Arcade version. Use when asked "test arcade", "build and test arcade", "validate arcade changes", "try arcade locally", "test arcade SDK", "build arcade packages", or "run adotnet/arcade-skills12