[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"org-dotnet":3,"repo-skills-v-0-3-0":190},{"org":4,"repos":59},{"slug":5,"name":6,"logoUrl":7,"githubOrg":5,"website":8,"skillCount":9,"repoCount":10,"topRepos":11,"topTags":27,"lastUpdatedAt":58},"dotnet",".NET (Microsoft)","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fdotnet.png","https:\u002F\u002Fdotnet.microsoft.com",144,6,[12,15,18,21,24],{"name":13,"skillCount":14},"dotnet\u002Fskills",96,{"name":16,"skillCount":17},"dotnet\u002Fmaui-labs",32,{"name":19,"skillCount":20},"dotnet\u002Farcade-skills",12,{"name":22,"skillCount":23},"dotnet\u002Fdocs-tools",2,{"name":25,"skillCount":26},"dotnet\u002Fdev-proxy",1,[28,31,34,37,40,43,46,49,52,55],{"slug":29,"name":30},"net",".NET",{"slug":32,"name":33},"maui","MAUI",{"slug":35,"name":36},"engineering","Engineering",{"slug":38,"name":39},"debugging","Debugging",{"slug":41,"name":42},"mobile","Mobile",{"slug":44,"name":45},"testing","Testing",{"slug":47,"name":48},"code-analysis","Code Analysis",{"slug":50,"name":51},"performance","Performance",{"slug":53,"name":54},"migration","Migration",{"slug":56,"name":57},"blazor","Blazor","2026-08-01T06:06:00.975068",[60,76,106,125,144,174],{"name":61,"fullName":13,"repoUrl":62,"skillCount":14,"stars":63,"forks":64,"description":65,"topics":66,"topTags":68,"topTagCount":75,"lastUpdatedAt":58},"skills","https:\u002F\u002Fgithub.com\u002Fdotnet\u002Fskills",4576,332,"Repository for skills to assist AI coding agents with .NET and C#",[67],"agent-skills",[69,70,71,72,73,74],{"slug":29,"name":30},{"slug":35,"name":36},{"slug":44,"name":45},{"slug":38,"name":39},{"slug":47,"name":48},{"slug":53,"name":54},57,{"name":77,"fullName":16,"repoUrl":78,"skillCount":17,"stars":79,"forks":80,"description":81,"topics":82,"topTags":93,"topTagCount":104,"lastUpdatedAt":105},"maui-labs","https:\u002F\u002Fgithub.com\u002Fdotnet\u002Fmaui-labs",190,21,"Experimental and pre-release tools for .NET MAUI",[83,84,85,5,86,87,32,88,89,41,90,91,92],"ai","android","desktop","ios","maccatalyst","mcp","microsoft","multi-platform","user-interface","winui",[94,95,96,97,98,101],{"slug":32,"name":33},{"slug":41,"name":42},{"slug":29,"name":30},{"slug":38,"name":39},{"slug":99,"name":100},"api-development","API Development",{"slug":102,"name":103},"csharp","C#",44,"2026-07-12T08:22:56.616564",{"name":107,"fullName":19,"repoUrl":108,"skillCount":20,"stars":20,"forks":109,"description":110,"topics":111,"topTags":112,"topTagCount":123,"lastUpdatedAt":124},"arcade-skills","https:\u002F\u002Fgithub.com\u002Fdotnet\u002Farcade-skills",18,"Reuseable AI skills, plugins, agents for use in the dotnet product repos, such as dotnet\u002Fruntime",[],[113,114,117,118,119,122],{"slug":29,"name":30},{"slug":115,"name":116},"ci-cd","CI\u002FCD",{"slug":38,"name":39},{"slug":35,"name":36},{"slug":120,"name":121},"cli","CLI",{"slug":47,"name":48},15,"2026-07-12T08:23:11.212231",{"name":126,"fullName":22,"repoUrl":127,"skillCount":23,"stars":128,"forks":129,"description":130,"topics":131,"topTags":132,"topTagCount":142,"lastUpdatedAt":143},"docs-tools","https:\u002F\u002Fgithub.com\u002Fdotnet\u002Fdocs-tools",25,40,"This repo contains GitHub Actions and other tools that are designed to be invoked on DocFx repositories.",[],[133,136,139],{"slug":134,"name":135},"documentation","Documentation",{"slug":137,"name":138},"technical-writing","Technical Writing",{"slug":140,"name":141},"operations","Operations",3,"2026-07-12T08:22:00.701757",{"name":145,"fullName":25,"repoUrl":146,"skillCount":26,"stars":147,"forks":148,"description":149,"topics":150,"topTags":165,"topTagCount":172,"lastUpdatedAt":173},"dev-proxy","https:\u002F\u002Fgithub.com\u002Fdotnet\u002Fdev-proxy",801,86,"Simulate API failures, throttling, and chaos — all from your command line.",[151,152,145,153,154,155,156,157,158,159,160,161,162,163,164],"api-testing","chaos-engineering","developer-tools","development","devtools","hacktoberfest","http","microsoft-365","microsoft-graph","mock-server","openapi","proxy","resilience","rest",[166,167,168,171],{"slug":99,"name":100},{"slug":38,"name":39},{"slug":169,"name":170},"observability","Observability",{"slug":44,"name":45},4,"2026-07-12T08:21:24.806721",{"name":175,"fullName":176,"repoUrl":177,"skillCount":26,"stars":178,"forks":179,"description":180,"topics":181,"topTags":185,"topTagCount":142,"lastUpdatedAt":189},"msbuild","dotnet\u002Fmsbuild","https:\u002F\u002Fgithub.com\u002Fdotnet\u002Fmsbuild",5535,1436,"The Microsoft Build Engine (MSBuild) is the build platform for .NET and Visual Studio.",[182,156,183,89,175,184],"build","help-wanted","visual-studio",[186,187,188],{"slug":29,"name":30},{"slug":35,"name":36},{"slug":50,"name":51},"2026-07-22T05:37:33.965588",{"items":191,"total":20},[192,207,218,231,242,256,266,276,289,300,311,321],{"slug":193,"name":193,"fn":194,"description":195,"org":196,"tags":197,"stars":20,"repoUrl":108,"updatedAt":124},"binskim-analysis","investigate BinSkim SDL security findings","Investigate 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 required\". DO NOT USE FOR: running BinSkim locally (use binskim-scan), source code analysis (use CodeQL), or credential scanning (use CredScan).\n",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[198,200,203,204],{"name":30,"slug":29,"type":199},"tag",{"name":201,"slug":202,"type":199},"Audit","audit",{"name":48,"slug":47,"type":199},{"name":205,"slug":206,"type":199},"Security","security",{"slug":208,"name":208,"fn":209,"description":210,"org":211,"tags":212,"stars":20,"repoUrl":108,"updatedAt":217},"binskim-scan","run BinSkim binary security analysis","Run 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 scanning (use CredScan), or general build\u002Ftest failures (use ci-analysis).\n",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[213,214,215,216],{"name":30,"slug":29,"type":199},{"name":121,"slug":120,"type":199},{"name":48,"slug":47,"type":199},{"name":205,"slug":206,"type":199},"2026-07-12T08:23:09.911458",{"slug":219,"name":219,"fn":220,"description":221,"org":222,"tags":223,"stars":20,"repoUrl":108,"updatedAt":230},"ci-analysis","analyze .NET CI build and test status","Analyze 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 from one repo to another, reviewing code changes for correctness or style.\n",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[224,225,228,229],{"name":30,"slug":29,"type":199},{"name":226,"slug":227,"type":199},"Azure","azure",{"name":116,"slug":115,"type":199},{"name":39,"slug":38,"type":199},"2026-07-12T08:21:49.360882",{"slug":232,"name":232,"fn":233,"description":234,"org":235,"tags":236,"stars":20,"repoUrl":108,"updatedAt":241},"ci-crash-dump","debug CI crash dumps","Download 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.\n",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[237,238,239,240],{"name":30,"slug":29,"type":199},{"name":116,"slug":115,"type":199},{"name":39,"slug":38,"type":199},{"name":45,"slug":44,"type":199},"2026-07-12T08:21:56.945844",{"slug":243,"name":243,"fn":244,"description":245,"org":246,"tags":247,"stars":20,"repoUrl":108,"updatedAt":255},"flow-analysis","analyze VMR codeflow health","Analyze 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\u002Fdotnet\". DO NOT USE FOR: CI build failures (use ci-analysis skill), code review (use code-review skill), general PR investigation without codeflow context, tracing whether a specific commit\u002FPR has reached another repo (use flow-tracing skill). INVOKES: maestro and GitHub MCP tools, flow-health.cs script.\n",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[248,249,250,253],{"name":116,"slug":115,"type":199},{"name":36,"slug":35,"type":199},{"name":251,"slug":252,"type":199},"GitHub","github",{"name":254,"slug":88,"type":199},"MCP","2026-07-12T08:21:53.151866",{"slug":257,"name":257,"fn":258,"description":259,"org":260,"tags":261,"stars":20,"repoUrl":108,"updatedAt":265},"flow-tracing","trace .NET dependency flow in VMR","Trace dependency flow across .NET repos through the VMR pipeline. USE FOR: checking if a PR\u002Fcommit 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 health or staleness (use flow-analysis skill), CI build failures (use ci-analysis skill). INVOKES: maestro and GitHub MCP tools, Get-SdkVersionTrace.ps1 script.\n",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[262],{"name":263,"slug":264,"type":199},"Data Pipeline","data-pipeline","2026-07-12T08:21:55.689056",{"slug":267,"name":267,"fn":268,"description":269,"org":270,"tags":271,"stars":20,"repoUrl":108,"updatedAt":275},"helix-investigation","investigate Helix test failures","Deep-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 failing helix runs\", \"what are the most common failures\". DO NOT USE FOR: high-level CI status checks (use ci-analysis), codeflow PRs (use flow-analysis). INVOKES: Helix and AzDO MCP tools, curl, gh CLI.\n",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[272,273,274],{"name":39,"slug":38,"type":199},{"name":36,"slug":35,"type":199},{"name":45,"slug":44,"type":199},"2026-07-12T08:21:46.445586",{"slug":277,"name":277,"fn":278,"description":279,"org":280,"tags":281,"stars":20,"repoUrl":108,"updatedAt":288},"known-issue-history","analyze historical build error failure rates","Analyze 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\".\n",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[282,283,286,287],{"name":30,"slug":29,"type":199},{"name":284,"slug":285,"type":199},"Analytics","analytics",{"name":48,"slug":47,"type":199},{"name":39,"slug":38,"type":199},"2026-07-12T08:21:48.106854",{"slug":290,"name":290,"fn":291,"description":292,"org":293,"tags":294,"stars":20,"repoUrl":108,"updatedAt":299},"maestro-cli","query Maestro dependency flow data","Query Maestro\u002FBAR 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 skills when MCP server is loaded). INVOKES: bash (mstro CLI commands with --json output).\n",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[295,296,297,298],{"name":30,"slug":29,"type":199},{"name":116,"slug":115,"type":199},{"name":121,"slug":120,"type":199},{"name":36,"slug":35,"type":199},"2026-07-12T08:21:44.740467",{"slug":301,"name":301,"fn":302,"description":303,"org":304,"tags":305,"stars":20,"repoUrl":108,"updatedAt":310},"pipeline-investigation","investigate Azure DevOps pipeline failures","Investigate 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\u002Ftrend analysis. DO NOT USE FOR: Helix test failures (use helix-investigation), CI status overview (use ci-analysis), codeflow PRs (use flow-analysis). INVOKES: AzDO, Helix, and binlog MCP tools, az CLI for internal auth, gh CLI.\n",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[306,307,308,309],{"name":30,"slug":29,"type":199},{"name":116,"slug":115,"type":199},{"name":39,"slug":38,"type":199},{"name":36,"slug":35,"type":199},"2026-07-12T08:21:58.244188",{"slug":312,"name":312,"fn":313,"description":314,"org":315,"tags":316,"stars":20,"repoUrl":108,"updatedAt":320},"subscription-history","retrieve Maestro subscription history","Tell 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\u002Fnot 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\u002Fbranch search. DO NOT USE FOR: checking current subscription staleness\u002Fhealth (use flow-analysis or maestro-cli), tracing whether a commit reached a repo (use flow-tracing), CI build failures (use ci-analysis). INVOKES: shell (darc get-subscription-history).\n",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[317,318,319],{"name":30,"slug":29,"type":199},{"name":121,"slug":120,"type":199},{"name":36,"slug":35,"type":199},"2026-07-12T08:21:51.892007",{"slug":322,"name":322,"fn":323,"description":324,"org":325,"tags":326,"stars":20,"repoUrl":108,"updatedAt":332},"test-arcade","build and test Arcade SDK locally","Build 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 a repo against local arcade\". DO NOT USE FOR: CI analysis, Helix test investigation, codeflow\u002Fdependency-flow issues, or production Arcade SDK publishing.\n",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[327,328,331],{"name":30,"slug":29,"type":199},{"name":329,"slug":330,"type":199},"Deployment","deployment",{"name":45,"slug":44,"type":199},"2026-07-12T08:21:54.388318"]