How do I install the Build Dotnet Agent Service skill?

Run npx skillmds@latest add gaelic-ghost/build-dotnet-agent-service in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Build Dotnet Agent Service safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Build Dotnet Agent Service?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Build Dotnet Agent Service free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Build Dotnet Agent Service?

gaelic-ghost (@gaelic-ghost) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Build Dotnet Agent Service by gaelic-ghost

Name: Build Dotnet Agent Service
Author: gaelic-ghost

File contents

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.

---name: build-dotnet-agent-servicedescription: Build a local-first F# or C# Semantic Kernel agent service with explicit tools, model capability checks, evaluation fixtures, and draft-before-write promotion.license: Apache-2.0---# Build .NET Agent ServiceUse this skill when Semantic Kernel's plugin/function orchestration solves areal .NET application need. Preserve F# and C# equality: ask for the languagewhen a new project has no established choice, and do not add C# only to host anagent.## 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/>## Workflow1. Establish the deterministic baseline, typed input/output, chosen language, exact model endpoint/model, tool permissions, and no-op result.2. 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.3. Start with narrow read-only functions. The host validates authorization, schemas, timeouts, and output independently of model responses.4. 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.5. Add memory, planners, background work, or an ASP.NET endpoint only when the application requires it. Name retention, restart, and failure behavior.6. 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.## ValidationRun the repository's narrowest `dotnet build` and `dotnet test` commands.Separate fake-tool behavior from model-adapter smoke evidence, and reportattempted 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.

Frequently asked questions

Build Dotnet Agent Service