All Agent Skills
41,263 results
- Searching AEM DocumentationAdobeOfficialSearches the aem.live documentation for information on AEM Edge Delivery Services features. Use this skill when you need more information about a feature, want guidance on how to implement a feature, and using existing tools you have to search the web isn't turning up relevant results.
- Testing BlocksAdobeOfficialGuide for testing code changes in AEM Edge Delivery projects including blocks, scripts, and styles. Use this skill after making code changes and before opening a pull request to validate functionality. Covers unit testing for utilities and logic, browser testing with Playwright/Puppeteer, linting, performance validation, and guidance on which tests to maintain vs use as throwaway validation.
- Using the Block Collection and Block PartyAdobeOfficialThe Block Collection and Block Party are repositories for existing AEM blocks, build tools, code snippets, integration patterns, plugins, and more. Use this skill anytime you are developing something and want to find a reference to use as a starting point.
- Analyzing Cross Host Route OwnershipMicrosoftOfficialDetermines which URLs a partly migrated app is still served by the old .NET Framework host and which the new ASP.NET Core host already answers, by reading both projects and the YARP route table. Use when planning the next wave of a side-by-side migration, before deleting or moving a Framework route, or when deciding whether a route has finished migrating.
- Aspire IntegrationMicrosoftOfficialAdds Aspire orchestration to an existing repository for inner-loop development and optional Azure deployment readiness. Use when asked to "aspirerify a project", "add Aspire to a solution", "integrate Aspire", "set up an AppHost", "add aspire init", or "orchestrate services with Aspire".
- Aspire Version UpgradeMicrosoftOfficialUpgrade existing Aspire projects to a newer Aspire version. Also handles TFM upgrades — preferred when the solution contains Aspire projects, since the Aspire version drives the required TFM. Triggers for "upgrade Aspire", "update Aspire version", "move to latest Aspire", or any .NET upgrade request on a solution with Aspire artifacts.
- Azure Functions UpgradeMicrosoftOfficialUpgrade Azure Functions project from in-process model to isolated worker model. Use when user wants to migrate Azure Functions from in-proc to isolated, upgrade Functions hosting model, or modernize Azure Functions projects.
- Azure MigrateMicrosoftOfficialMigrates applications to Azure cloud services by starting an app modernization migration session. Use when user wants to migrate to Azure, start Azure migration, get help migrating an application to Azure, see Azure migration options, or start app modernization for Azure. Triggers for "migrate to Azure", "Azure migration", "move to Azure", "cloud migration", and "app modernization" requests.
- Building ProjectsMicrosoftOfficialBuild tool selection and orchestration for .NET projects during modernization upgrades. Use this skill whenever the agent modifies code files, project files, packages, or configuration and needs to validate the build — which is virtually every upgrade task.
- Building Winforms ApplicationsMicrosoftOfficialStructures WinForms applications with Designer-compatible patterns, proper code organization, and build/runtime compatibility. Use when creating or maintaining WinForms projects, working with Form or UserControl classes, organizing InitializeComponent vs application logic, implementing Application.Run patterns, handling Program.cs and ApplicationConfiguration, managing Application.SetHighDpiMode…
- Converting To CpmMicrosoftOfficialConverts .NET projects and solutions to NuGet Central Package Management (CPM) with Directory.Packages.props. Use when the user wants to centralize, convert, align, or sync NuGet package versions across multiple projects, resolve version conflicts or mismatches, or get versions consistent across a solution or repository. Also triggers when packages are out of sync or drifting across projects.
- Converting To Sdk StyleMicrosoftOfficialConverts legacy non-SDK-style .NET project files (.csproj, .vbproj, .fsproj) to modern SDK-style format while preserving target frameworks, dependencies, and build behavior. Use when converting old-format .NET projects, migrating from packages.config to PackageReference, or modernizing project files.
- Creating SkillsMicrosoftOfficialCreate, validate, and iteratively improve agent skills that follow Anthropic's best practices. Use this skill whenever someone wants to create a new skill, improve an existing skill, write a SKILL.md, set up a skill directory structure, or needs guidance on skill authoring patterns.
- Creating Winforms Custom ControlsMicrosoftOfficialCreates custom controls and UserControls for modern WinForms (.NET 6+). Use when deriving from Control, UserControl, Button, TextBox, or other base controls, implementing custom rendering with OnPaint overrides, creating composite controls with child control composition, adding custom properties with [Browsable], [Category], or [DefaultValue] attributes for Designer support, implementing…
- Dashboard CanvasMicrosoftOfficialMechanics for opening the Upgrade Dashboard canvas panel — the exact canvasId and instanceId to send, when extensionId is required, how to handle registration errors, and the open_dashboard fallback. Load only on hosts that expose an open_canvas tool and list the Upgrade Dashboard canvas.
- Dotnet Arm64 MigrationMicrosoftOfficialMigrate one or more .NET projects to run on ARM64 (Apple Silicon, Windows on ARM, Linux/Alpine arm64, cloud arm64 like AWS Graviton / Azure Ampere). Use when the user wants to add arm64 support, target ARM64, build/publish for an arm64 runtime identifier (win-arm64, linux-arm64, linux-musl-arm64, osx-arm64), fix x86/x64 assumptions, resolve missing arm64 native NuGet assets, guard x86 hardware…
- Dotnet Framework Version UpgradeMicrosoftOfficialUpgrade .NET Framework projects to .NET Framework 4.8.1 (net481), staying on full .NET Framework without migrating to modern .NET (net8.0+). Use when user explicitly asks to upgrade to .NET Framework 4.8.1, upgrade to the latest .NET Framework version, or stay on full/Windows .NET Framework. Preserves legacy vs SDK-style project format unless the user explicitly requests SDK-style conversion.
- Dotnet Version UpgradeMicrosoftOfficialUpgrade .NET projects to newer .NET versions, including guidance on current release status, support lifecycle (LTS/STS), and recommended upgrade targets.
- Fixing Windows Only ModulesMicrosoftOfficialHandle Windows PowerShell-only modules (ActiveDirectory, ServerManager, Hyper-V, FailoverClusters, BitLocker, NetSecurity, Dism, Storage, ScheduledTasks, WebAdministration) that are not natively available in PowerShell 7.x, using Import-Module -UseWindowsPowerShell (the WinPS compatibility layer) or implicit remoting.
- Generating Upgrade Test BaselineMicrosoftOfficialGenerates behavior-locking tests before a .NET upgrade using the external dotnet-test plugin. Use when executing a generate-test-baseline task for projects with upgrade compatibility risks.
- Handling Removed SnapinsMicrosoftOfficialHandle PowerShell snap-ins (Add-PSSnapin / Get-PSSnapin / Remove-PSSnapin) that do not exist in PowerShell 7.x. Provides the decision tree between module replacement, implicit remoting into a Windows PowerShell endpoint, and the Windows PowerShell compatibility layer. Use during the powershell-51-to-7-upgrade scenario for the PSSnapin blocker bucket.
- Integrating Autofac With DotnetMicrosoftOfficialMigrates Autofac dependency injection configuration from ASP.NET Framework to ASP.NET Core's hosting model while keeping Autofac as the DI container. Use when upgrading projects that use Autofac, migrating Global.asax.cs or Startup.cs DI setup to Program.cs, or integrating AutofacServiceProviderFactory with the generic host.
- Jsts Framework MigrationMicrosoftOfficialMigrate a JavaScript or TypeScript project from one framework to another while preserving behavior, integrations, build workflows, and validation. Covers application-framework migrations (for example Gatsby to Astro, Create React App to Vite) and tooling/test-framework migrations (for example Karma/Jasmine to Vitest).
- Managing Blazor Server AuthenticationMicrosoftOfficialManages authentication in Blazor Server applications with ASP.NET Core Identity. Solves critical Blazor Server auth issues: HttpContext NULL errors during WebSocket circuits, cookie auth operations failing silently in component handlers, login/logout not working in interactive mode, SignInManager returning null, cascading auth state parameter errors.