Refresh catalog upstreams and add F# skills

Closes #688
Closes #696
Closes #704
Closes #705
Closes #706
Closes #709
Closes #714
Closes #716
Closes #717
Closes #718
Closes #719
Closes #720
Closes #721
Closes #722
Closes #723
Closes #724
Closes #725
Closes #726
Closes #727
Closes #728
Closes #729
Closes #730

Author: KSemenenko

.github/upstream-watch-state.json

@@ -54,6 +54,20 @@
         "project-setup"
       ]
     },
+    {
+      "id": "fsharp-overview-docs",
+      "source": "https://learn.microsoft.com/dotnet/fsharp/what-is-fsharp",
+      "skills": [
+        "fsharp"
+      ]
+    },
+    {
+      "id": "fsharp-interactive-docs",
+      "source": "https://learn.microsoft.com/dotnet/fsharp/tools/fsharp-interactive/",
+      "skills": [
+        "fsi"
+      ]
+    },
     {
       "id": "aspnetcore-overview-docs",
       "source": "https://learn.microsoft.com/aspnet/core/overview?view=aspnetcore-10.0",

.github/upstream-watch.platform.json

@@ -75,7 +75,7 @@ Update this file when the user gives:
 Treat explicit frustration, swearing, sarcasm, repeated rejection, or "don't do this again" as strong signals that a durable rule should likely be captured here.
 
 - Waza is a repository CI quality-check dependency for evaluating catalog skill quality. Do not add Waza as a catalog skill, package, tool entry, install bundle, or public catalog surface.
-- When Waza CI finds catalog skill-quality warnings, the workflow should create or update a GitHub issue with the concrete findings instead of relying only on workflow logs.
+- When Waza CI finds repo-owned catalog skill-quality warnings, the workflow should create or update a GitHub issue with the concrete findings instead of relying only on workflow logs. Imported upstream warnings should stay visible in the report artifact but should not create or keep a repo issue by themselves.
 
 - The repo is moving away from the repo-authored `dotnet-*` skill-id namespace. Prefer clean canonical skill ids without the `dotnet-` prefix for repo-authored skills, and when renaming public skill ids, do a clean cutover instead of keeping backward-compatible legacy aliases unless the user explicitly asks for a compatibility bridge.
 

AGENTS.md

@@ -291,7 +291,7 @@ When you refresh vendored upstream content locally, use `bash scripts/sync_exter
 
 <!-- BEGIN GENERATED CATALOG -->
 
-This catalog currently contains **159** skills.
+This catalog currently contains **162** skills.
 
 ### .NET Foundations
 
@@ -300,11 +300,14 @@ This catalog currently contains **159** skills.
 | [`csharp-scripts`](catalog/Platform/Official-DotNet/skills/csharp-scripts/) | `0.1.0` | Run single-file C# programs as scripts (file-based apps) for quick experimentation, prototyping, and concept testing. Use when the user wants to write and execute a small C# program without creating a full project. |
 | [`dotnet`](catalog/Platform/DotNet/skills/dotnet/) | `1.0.2` | Primary router skill for broad .NET work. Classify the repo by app model and cross-cutting concern first, then switch to the narrowest matching .NET skill instead of staying at a generic layer. USE FOR: general .NET requests without a narrower framework; C# implementation, debugging, review, or refactoring; routing to framework and tooling skills. DO NOT USE FOR: unrelated stacks; tasks already covered by a narrower .NET skill. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made. |
 | [`dotnet-pinvoke`](catalog/Platform/Official-DotNet/skills/dotnet-pinvoke/) | `0.1.0` | Correctly call native (C/C++) libraries from .NET using P/Invoke and LibraryImport. Covers function signatures, string marshalling, memory lifetime, SafeHandle, and cross-platform patterns. USE FOR: writing new P/Invoke or LibraryImport declarations, reviewing or debugging existing native interop code, wrapping a C or C++ library for use in .NET, diagnosing crashes, memory leaks, or corruption at the managed/native boundary. DO NOT USE FOR: COM interop, C++/CLI mixed-mode assemblies, or pure managed code with no native dependencies. |
+| [`fsharp`](catalog/Tools/FSharp/skills/fsharp/) | `1.0.0` | Write, review, or modernize F# code in .NET repositories with functional-first design, algebraic data types, pattern matching, pipelines, async workflows, project ordering, and C# interop. USE FOR: F# .fs/.fsproj code; discriminated unions, records, options, results, pattern matching, computation expressions, or functional domain modeling; strongly typed AI-generated .NET code. DO NOT USE FOR: C# language modernization; FSI-only exploratory scripts with no project changes. INVOKES: inspect .fsproj file order and SDK settings, edit F# source and project files, and run dotnet build/test or dotnet fsi validation commands when changes are made. |
+| [`fsi`](catalog/Tools/FSharp/skills/fsi/) | `1.0.0` | Use F# Interactive (`dotnet fsi`) for .NET exploration, scriptable experiments, package-backed .fsx workflows, quick data transforms, and reproducible command-line probes. USE FOR: .fsx scripts, F# REPL work, #r nuget references, #load composition, interactive type exploration, and small strongly typed experiments before moving code into a project. DO NOT USE FOR: production application code that needs compiled project structure; C# scripting; long-lived automation better expressed as a normal CLI, test, or build target. INVOKES: run dotnet fsi, edit .fsx scripts, load project or source files, and validate snippets against the target SDK. |
 | [`managedcode-communication`](catalog/Libraries/ManagedCode-Communication/skills/managedcode-communication/) | `1.0.0` | Use ManagedCode.Communication when a .NET application needs explicit result objects, structured errors, and predictable service or API boundaries instead of exception-driven control flow. USE FOR: integrating ManagedCode.Communication into services or APIs; replacing exception-driven result handling with explicit results; reviewing service boundaries that return. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made. |
 | [`managedcode-mimetypes`](catalog/Libraries/ManagedCode-MimeTypes/skills/managedcode-mimetypes/) | `1.0.0` | Use ManagedCode.MimeTypes when a .NET application needs consistent MIME type detection, extension mapping, and content-type decisions for uploads, downloads, or HTTP responses. USE FOR: integrating ManagedCode.MimeTypes into upload or download flows; mapping file extensions to content types in APIs or background processing; reviewing content-type. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made. |
 | [`microsoft-extensions`](catalog/Libraries/Microsoft-Extensions/skills/microsoft-extensions/) | `1.0.0` | Use the Microsoft.Extensions stack correctly across Generic Host, dependency injection, configuration, logging, options, HttpClientFactory, and other shared infrastructure patterns. USE FOR: wiring dependency injection, configuration, logging, or options; introducing Generic Host patterns into non-web .NET apps; cleaning up service registration, typed HTTP. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made. |
 | [`modern-csharp`](catalog/Tools/Modern-CSharp/skills/modern-csharp/) | `1.0.0` | Write modern, version-aware C# for .NET repositories while staying compatible with the repo's target framework and language-version policy. USE FOR: modern idiomatic C# code; language-version compatibility decisions; upgrading or reviewing C# feature usage across versions. DO NOT USE FOR: non-C# .NET languages such as F# or VB; analyzer-only or formatter-only setup with no language feature choice. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made. |
 | [`project-setup`](catalog/Platform/Project-Setup/skills/project-setup/) | `1.0.0` | Create or reorganize .NET solutions with clean project boundaries, repeatable SDK settings, and a maintainable baseline for libraries, apps, tests, CI, and local development. USE FOR: creating a new .NET solution or restructuring an existing one; setting up Directory.Build.props, shared package management, or repo-wide defaults; defining project. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made. |
+| [`system-text-json-net11`](catalog/Platform/Official-DotNet-Dotnet11/skills/system-text-json-net11/) | `0.1.0` | Provides guidance on new System.Text.Json APIs introduced in .NET 11. It covers typed JsonTypeInfo access via GetTypeInfo<T> and TryGetTypeInfo<T> on JsonSerializerOptions, and the new JsonNamingPolicy.PascalCase static property. Use when serializing or deserializing JSON in .NET 11 applications and needing typed metadata access or PascalCase property naming. |
 
 ### .NET Quality
 
@@ -395,7 +398,7 @@ This catalog currently contains **159** skills.
 
 | Skill | Version | Description |
 |-------|---------|-------------|
-| [`aspire`](catalog/Frameworks/Aspire/skills/aspire/) | `1.3.3` | Build, upgrade, and operate .NET Aspire 13.2.x application hosts with current CLI, AppHost, ServiceDefaults, integrations, dashboard, testing, and Azure deployment patterns for distributed apps. USE FOR: Aspire.AppHost.Sdk, Aspire.Hosting.*, DistributedApplication.CreateBuilder, WithReference, WaitFor, AddProject, AddRedis, AddPostgres, aspire run, aspire init, aspire. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made. |
+| [`aspire`](catalog/Frameworks/Aspire/skills/aspire/) | `1.3.3` | Build, upgrade, and operate .NET Aspire 13.3.x application hosts with current CLI, AppHost, ServiceDefaults, integrations, dashboard, testing, and Azure deployment patterns for distributed apps. USE FOR: Aspire.AppHost.Sdk, Aspire.Hosting.*, DistributedApplication.CreateBuilder, WithReference, WaitFor, AddProject, AddRedis, AddPostgres, aspire run, aspire init, aspire. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made. |
 
 ### Azure Functions
 

README.md

@@ -1,7 +1,7 @@
 ---
 name: aspire
-description: "Build, upgrade, and operate .NET Aspire 13.2.x application hosts with current CLI, AppHost, ServiceDefaults, integrations, dashboard, testing, and Azure deployment patterns for distributed apps. USE FOR: Aspire.AppHost.Sdk, Aspire.Hosting.*, DistributedApplication.CreateBuilder, WithReference, WaitFor, AddProject, AddRedis, AddPostgres, aspire run, aspire init, aspire. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made."
-compatibility: "Best for current Aspire 13.2.x tooling on .NET 10; use version-aware upgrade guidance for older 8.x or 9.x Aspire solutions."
+description: "Build, upgrade, and operate .NET Aspire 13.3.x application hosts with current CLI, AppHost, ServiceDefaults, integrations, dashboard, testing, and Azure deployment patterns for distributed apps. USE FOR: Aspire.AppHost.Sdk, Aspire.Hosting.*, DistributedApplication.CreateBuilder, WithReference, WaitFor, AddProject, AddRedis, AddPostgres, aspire run, aspire init, aspire. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made."
+compatibility: "Best for current Aspire 13.3.x tooling on .NET 10; use version-aware upgrade guidance for older 8.x or 9.x Aspire solutions."
 ---
 
 # .NET Aspire
@@ -20,7 +20,7 @@ compatibility: "Best for current Aspire 13.2.x tooling on .NET 10; use version-a
 
 1. Classify the task first: new AppHost creation, existing-solution enlistment, integration wiring, testing and observability, deployment, or version upgrade.
 2. Prefer the current Aspire toolchain. For greenfield or modernized work, use the Aspire CLI and current AppHost SDK instead of writing new guidance around the deprecated legacy workload.
-3. Treat 13.2.x releases as servicing and feature updates for the current CLI-first app model, not a topology rewrite. Keep the Aspire CLI, `Aspire.AppHost.Sdk`, and closely coupled hosting or testing packages on the same line, then rerun the AppHost and deployment checks after `aspire update`.
+3. Treat 13.3.x releases as servicing and feature updates for the current CLI-first app model, not a topology rewrite. Keep the Aspire CLI, `Aspire.AppHost.Sdk`, and closely coupled hosting or testing packages on the same line, then rerun the AppHost and deployment checks after `aspire update`.
 4. Keep the AppHost code-first and topology-focused. Model services, resources, dependencies, endpoints, lifetimes, and parameters there; keep business logic out.
 5. Keep `ServiceDefaults` narrow. It exists for telemetry, health checks, resilience, and service discovery, not shared domain models or general utility code.
 6. Prefer official first-party Aspire integrations when they cover the requirement. Use `CommunityToolkit/Aspire` only when the capability gap is real: unsupported language hosts, extra dev infrastructure, or extension packages the official project does not provide.
@@ -67,13 +67,13 @@ flowchart LR
 ## Official Sources
 
 - [Aspire docs home](https://aspire.dev/docs/)
-- [What's new in Aspire 13.2](https://aspire.dev/whats-new/aspire-13-2/)
+- [What's new in Aspire 13.3](https://aspire.dev/whats-new/aspire-13-3/)
 - [AppHost](https://aspire.dev/get-started/app-host/)
 - [Service defaults](https://aspire.dev/fundamentals/service-defaults/)
 - [Integrations overview](https://aspire.dev/integrations/overview/)
 - [Build your first app](https://aspire.dev/get-started/first-app/)
 - [Aspire CLI reference](https://aspire.dev/reference/cli/commands/aspire/)
-- [Upgrade Aspire](https://learn.microsoft.com/en-us/dotnet/aspire/get-started/upgrade-to-aspire-13)
+- [Aspire 13.3 release](https://github.com/microsoft/aspire/releases/tag/v13.3.0)
 - [Testing overview](https://aspire.dev/testing/overview/)
 - [microsoft/aspire](https://github.com/microsoft/aspire)
 - [CommunityToolkit/Aspire](https://github.com/CommunityToolkit/Aspire)

catalog/Frameworks/Aspire/skills/aspire/SKILL.md

@@ -35,7 +35,7 @@ Use this reference when the user needs an example-first entry point instead of c
 ## Streams, Observers, And Real-Time
 
 - [Chat Room sample](https://learn.microsoft.com/samples/dotnet/samples/orleans-chat-room-sample)
-- [Streaming pub/sub with Azure Event Hubs](https://learn.microsoft.com/samples/dotnet/samples/orleans-streaming-pubsub-with-azure-event-hub)
+- [Streaming pub/sub with Azure Event Hubs](https://learn.microsoft.com/samples/dotnet/samples/orleans-streaming-samples/)
 - [Chirper social sample](https://learn.microsoft.com/samples/dotnet/samples/orleans-chirper-social-media-sample-app)
 - [GPS Tracker with SignalR](https://learn.microsoft.com/samples/dotnet/samples/orleans-gps-device-tracker-sample)
 

catalog/Frameworks/Orleans/skills/orleans/references/examples.md

@@ -195,7 +195,7 @@ This skill keeps a live-link map for Orleans instead of a mirrored local docs sn
 - [Blazor WebAssembly sample](https://learn.microsoft.com/samples/dotnet/samples/orleans-aspnet-core-blazor-wasm-sample)
 - [Stocks sample](https://learn.microsoft.com/samples/dotnet/samples/orleans-stocks-sample-app)
 - [Transport Layer Security sample](https://learn.microsoft.com/samples/dotnet/samples/orleans-transport-layer-security-tls)
-- [Streaming with Azure Event Hubs](https://learn.microsoft.com/samples/dotnet/samples/orleans-streaming-pubsub-with-azure-event-hub)
+- [Streaming with Azure Event Hubs](https://learn.microsoft.com/samples/dotnet/samples/orleans-streaming-samples/)
 
 ## GitHub Source Entry Points
 

catalog/Frameworks/Orleans/skills/orleans/references/official-docs-index.md

@@ -58,7 +58,7 @@ After identifying the task type, select the right library layer. These libraries
    - Agentic loops that iterate until a goal is met
    - Multi-agent collaboration with handoff protocols
    - Graph-based or durable workflows
-   
+
    Do **not** implement these patterns by hand with `IChatClient` — the Agent Framework provides iteration limits, observability, and tool dispatch that are error-prone to reimplement.
 
 4. **Add Copilot SDK only when building Copilot extensions.** Use `GitHub.Copilot.SDK` when the goal is to build a custom agent or tool that runs inside the GitHub Copilot platform (CLI, IDE, or Copilot Chat). This is not a general-purpose LLM orchestration library — it is specifically for Copilot extensibility.

catalog/Platform/Official-DotNet-AI/skills/technology-selection/SKILL.md

@@ -0,0 +1,9 @@
+{
+  "name": "dotnet11",
+  "title": "Official .NET skills: dotnet11",
+  "description": "Skills for .NET 11 APIs and language features.",
+  "links": {
+    "repository": "https://github.com/dotnet/skills",
+    "docs": "https://github.com/dotnet/skills/tree/main/plugins/dotnet11"
+  }
+}