Build dotnet agent service

Skill gaelic-ghost/socket/skills/build-dotnet-agent-service

Build a local-first F# or C# Semantic Kernel agent service with explicit tools, model capability checks, evaluation fixtures, and draft-before-write promotion.From its SKILL.md

Install

npx -y skills add gaelic-ghost/socket --skill build-dotnet-agent-service

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.6 KB, as published. Nobody here has run it

Build .NET Agent Service

Use this skill when Semantic Kernel's plugin/function orchestration solves a real .NET application need. Preserve F# and C# equality: ask for the language when a new project has no established choice, and do not add C# only to host an agent.

Source Check

Semantic Kernel: https://learn.microsoft.com/en-us/semantic-kernel/overview/
.NET: https://learn.microsoft.com/dotnet/
ASP.NET Core: https://learn.microsoft.com/aspnet/core/

Workflow

Establish the deterministic baseline, typed input/output, chosen language, exact model endpoint/model, tool permissions, and no-op result.
Use Semantic Kernel only for a named plugin/function, planning, or orchestration requirement. Keep domain logic in F# modules or C# domain types rather than embedding it in prompt or endpoint code.
Start with narrow read-only functions. The host validates authorization, schemas, timeouts, and output independently of model responses.
Prove valid tool-call JSON, structured output, no-call behavior, malformed call recovery, maximum-step stopping, and grounded observations on the exact local/self-hosted server and model; HTTP compatibility alone is insufficient.
Add memory, planners, background work, or an ASP.NET endpoint only when the application requires it. Name retention, restart, and failure behavior.
Add fake-plugin tests, structured-result tests, denied-write tests, and opt-in local-model smoke tests. External writes remain draft-only until an exact auto-with-escalation approval gate is satisfied.

Validation

Run the repository's narrowest dotnet build and dotnet test commands. Separate fake-tool behavior from model-adapter smoke evidence, and report attempted versus executed side effects.

Guardrails

Do not add Semantic Kernel to a library or service that only needs one direct model request.
Do not store secrets, local endpoint credentials, prompts, or traces in source control.
Do not start a background agent, schedule, or public endpoint by default.
Do not use model output as permission to call a destructive plugin.