skills.rest
CoolCoderSuper
CoolCoderSuperCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

validate-sdk

Install and validate a .NET SDK from an Azure DevOps build.

4|1|Updated May 1, 2026
Search Tags:#validation#build#sdk#dotnet#azure-devops#temporary#isolated
One-click install
npx skills add https://github.com/CoolCoderSuper/vb-ls --skill validate-sdk-coolcodersuper
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: validate-sdk
Source: https://github.com/CoolCoderSuper/vb-ls/tree/main/roslyn/.github/skills/validate-sdk
Command: npx skills add https://github.com/CoolCoderSuper/vb-ls --skill validate-sdk-coolcodersuper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill installs and validates a .NET SDK from an Azure DevOps internal build, enabling reproducible environments for Roslyn and other .NET workloads without modifying the user's working directory.

Core Features & Use Cases

  • Install the exact SDK version from a dnceng/internal Azure DevOps build URL or buildId.
  • Validate the installation by running a small, isolated test project in a temp directory to confirm the compiler version and capabilities.
  • Use in CI validation, local experimentation, or reproducible environment setups that require a specific SDK build.

Quick Start

Install the target SDK from the specified Azure DevOps build URL or buildId and run the validation workflow.

Frequently Asked Questions about validate-sdk

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I install and validate a .NET SDK from an Azure DevOps internal build?▼

Validate a .NET SDK from an Azure DevOps build by downloading the exact version to a temporary directory using a specific buildId, then running an isolated test project to confirm compiler version and capabilities.

What is the best way to set up a reproducible .NET environment without modifying my working directory?▼

Set up a reproducible .NET environment without modifying your working directory by downloading the target SDK into a temporary, isolated directory and validating it through a small test project.

Can I use a specific buildId to install a .NET SDK for CI validation?▼

Yes, you can install a .NET SDK for CI validation by specifying a buildId or build URL from a dnceng internal Azure DevOps pipeline, which downloads and validates that exact internal build.

Does validating an internal .NET SDK build check the Roslyn compiler details?▼

Validating an internal .NET SDK build checks Roslyn compiler details by running an isolated test project in a temp directory and reporting the discovered SDK and compiler capabilities.

Why should I use a temporary directory for local .NET SDK experimentation?▼

Using a temporary directory for local .NET SDK experimentation keeps your working directory unmodified, providing an isolated environment that safely validates the installation and compiler capabilities.

Related Skills

Explore More Software Engineering Skills→
CoolCoderSuperCoolCoderSuper
4

ci-analysis

Analyze Azure DevOps and Helix CI failures for dotnet repository PRs.

Community
Advanced
aaronbassettaaronbassett

midnight-tooling:midnight-compatibility

Align Midnight compiler, runtime, and SDK versions against the support matrix.

Community
Intermediate
pluginagentmarketplacepluginagentmarketplace
1

aspnet-core-devops

Containerize ASP.NET Core apps with Docker and deploy to Azure, AWS, or GCP.

Community
Advanced
AzureAzure
15

azure-functions-setup

Verify Azure Functions development environment prerequisites and tool versions.

Official
Intermediate