Why should you care?

For AgentVerse on .NET, SK is a practical way to keep prompts and tools organized instead of scattered HttpClient calls.

See it live — copy this example

Use .NET 8+. Run Semantic Kernel samples in a console or Web API. Keep API keys in user secrets or environment variables — never in source.

// dotnet add package Microsoft.SemanticKernel
using Microsoft.SemanticKernel;

var builder = Kernel.CreateBuilder();
// next lessons: add chat completion + plugins
var kernel = builder.Build();
Console.WriteLine($"Plugins: {kernel.Plugins.Count}");

What happened?

• CreateBuilder configures the kernel.
• Build() creates the runtime object.
• Plugins hold your tools.

Practice next

1. Create a console app.
2. Add Microsoft.SemanticKernel.
3. Build an empty kernel and print plugin count.
4. Add logging to the builder.
5. Create a second project for Web API later.

Remember

SK = kernel + prompts + plugins. Start empty, then add chat + tools. Keep config outside code.

SK as the spine

All AgentVerse skills register as plugins on one kernel per request.

Outcome: Clear place to attach tools.