Skill Introduction

Overview

How to build, run and verify the .NET sample projects in the Agent Framework repository. Use this when a user wants to verify that the samples still function as expected.

Core value

Turns reusable Development know-how into an installable skill, helping users complete github, community, agent-framework, agentic-ai work faster.

Target users

Developers, testers, and maintainers who handle Development tasks in Focus Code.
Teams that already trust workflows or content from microsoft.
Users who want standardized prompts, steps, or conventions instead of repeating setup work.

Best practices

Read the skill content first to confirm required inputs, expected outputs, and dependencies.
Try it on a small task before relying on it for critical work.
Add project-specific constraints such as coding style, target platform, test expectations, and delivery format.
For external sources, verify the source link, version, and recent maintenance activity.

Best use cases

Tasks related to github, community, agent-framework, agentic-ai that need a reusable execution flow.
Converting a community repo, team convention, or personal workflow into day-to-day assistance.
Starting from a proven skill instead of writing prompts or procedures from scratch.

Limits and boundaries

Results depend on the quality of the original skill content and may need human correction.
It does not replace code review, tests, security review, or professional judgment.
External tools, APIs, account permissions, and local dependencies still need separate setup.

Differentiation

Structured around Development, making it easier to discover and reuse than loose prompt snippets.
Marked as GitHub, which helps users judge trust and maintenance expectations.
Keeps the original source link available for repository, documentation, or discussion follow-up.
Tagged with github, community, agent-framework, agentic-ai, so it can be filtered by concrete task intent.

Install and use

Install

Copy Install Command

focus install verify-dotnet-samples-eac922

View source

Detail Preview

SKILL.md

Primary filemarkdown3 KB

name: verify-dotnet-samples description: How to build, run and verify the .NET sample projects in the Agent Framework repository. Use this when a user wants to verify that the samples still function as expected.

Verifying .NET Sample Projects

Sample Pre-requisites

We should only support verifying samples that:

Use environment variables for configuration.
Have no complex setup requirements, e.g., where multiple applications need to be run together, or where we need to launch a browser, etc.

Always report to the user which samples were run and which were not, and why.

Verifying a sample

Samples should be verified to ensure that they actually work as intended and that their output matches what is expected. For each sample that is run, output should be produced that shows the result and explains the reasoning about what output was expected, what was produced, and why it didn't match what the sample was expected to produce.

Steps to verify a sample:

Read the code for the sample
Check what environment variables are required for the sample
Check if each environment variable has been set
If there are any missing, give the user a list of missing environment variables to set and terminate
Summarize what the expected output of the sample should be
Run the sample
Show the user any output from the sample run as it gets produced, so that they can see the run progress
Check the output of the run against expectations
After running all requested samples, produce output for each sample that was verified:
If expectations were matched, output the following:
```
[Sample Name] Succeeded
```

If expectations were not matched, output the following:

[Sample Name] Failed
Actual Output:
[What the sample produced]
Expected Output:
[Explanation of what was expected and why the actual output didn't match expectations]

Environment Variables

Most samples use environment variables to configure settings.

var endpoint = Environment.GetEnvironmentVariable("AZURE_OPENAI_ENDPOINT") ?? throw new InvalidOperationException("AZURE_OPENAI_ENDPOINT is not set.");
var deploymentName = Environment.GetEnvironmentVariable("AZURE_OPENAI_DEPLOYMENT_NAME") ?? "gpt-4o-mini";

To run a sample, the environment variables should be set first. Before running a sample, check whether each environment variable in the sample has a value and then give the user a list of environment variables to set.

You can provide the user some examples of how to set the variables like this:

export AZURE_OPENAI_ENDPOINT="https://my-openai-instance.openai.azure.com/"
export AZURE_OPENAI_DEPLOYMENT_NAME="gpt-4o-mini"

To check if a variable has a value use e.g.:

echo $AZURE_OPENAI_ENDPOINT

How to Run a Sample (General Pattern)

cd dotnet/samples/<category>/<sample-dir>
dotnet run

For multi-targeted projects (e.g., Durable console apps), specify the framework:

dotnet run --framework net10.0

verify dotnet samples