ramprasadre56/multiagentframework/verify-dotnet-samples
Claude Code and agent skill by ramprasadre56/multiagentframework
- community
Checking that the SKILL.md file is still in the repository.
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.
Install
npx vskill@latest install ramprasadre56/multiagentframework/verify-dotnet-samplesSKILL.md
The same SKILL.md was published earlier as microsoft/agent-framework/verify-dotnet-samples.
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:
``text [Sample Name] Succeeded ``
- If expectations were not matched, output the following:
``text [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.
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:
To check if a variable has a value use e.g.:
How to Run a Sample (General Pattern)
For multi-targeted projects (e.g., Durable console apps), specify the framework:
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingdotnet/.github/skills/verify-dotnet-samples/SKILL.md
Popularity
- 7-day trend score
- 0
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/ramprasadre56/multiagentframework/verify-dotnet-samples)