How do I install the Csharp Dotnet Engineering Profile skill?

Run npx skillmds@latest add jovanipink/csharp-dotnet-engineering-profile 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 Csharp Dotnet Engineering Profile 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 Csharp Dotnet Engineering Profile?

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 Csharp Dotnet Engineering Profile free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Csharp Dotnet Engineering Profile?

JovaniPink (@jovanipink) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Csharp Dotnet Engineering Profile by jovanipink

Name: Csharp Dotnet Engineering Profile
Author: JovaniPink

Csharp Dotnet Engineering Profile

Apply focused C# and .NET engineering judgment after repository gate discovery. Use for .NET applications, libraries, ASP.NET Core, Entity Framework Core, async behavior, tests, packages, compatibility, and builds; defer exact commands to repository evidence.

JovaniPink e0a9e45 3 files · 3.9 KB Updated Sep 17, 2026

File contents

C# and .NET Engineering Profile

Use this profile only after repository discovery identifies the stack. Read focused checks when .NET-specific gates or hazards determine the result.

Workflow

Discover solution and project files, global.json, central package configuration, NuGet settings, lockfiles, target frameworks, runtime identifiers, and repository scripts.
Follow repository-defined commands and pinned SDK or tool versions before suggesting defaults.
Review material hazards, especially sync-over-async, lost cancellation, async void, disposal and lifetime errors, nullable-reference gaps, dependency-injection scope mismatches, deferred LINQ behavior, and unsafe serialization.
When data access is present, review Entity Framework tracking, query shape, client evaluation, concurrency, transactions, provider behavior, and migration authority.
Select proportionate gates from repository formatting, analyzers, compilation, tests, package validation, builds, and dependency review.
Review compatibility across target frameworks, SDK selection, package graphs, public APIs, trimming or native AOT, operating systems, and database providers.
Report every missing tool, skipped command, unsupported platform, or unavailable environment as incomplete rather than passing.

Boundaries

Do not invent one universal dotnet command or replace repository policy with generic preferences.
Do not restore from an unapproved feed, install tools, update packages, apply a database migration, publish, deploy, or mutate shared state merely to run a gate.
Separate static review, executed checks, build evidence, migration evidence, provider state, and live behavior.

Output

Return Discovery, Hazards, Commands selected, Results, Compatibility, Missing evidence, and Next safe gate.

---name: csharp-dotnet-engineering-profiledescription: Apply focused C# and .NET engineering judgment after repository gate discovery. Use for .NET applications, libraries, ASP.NET Core, Entity Framework Core, async behavior, tests, packages, compatibility, and builds; defer exact commands to repository evidence.license: MIT---# C# and .NET Engineering ProfileUse this profile only after repository discovery identifies the stack. Read [focused checks](references/checks.md) when .NET-specific gates or hazards determine the result.## Workflow1. Discover solution and project files, `global.json`, central package configuration, NuGet settings, lockfiles, target frameworks, runtime identifiers, and repository scripts.2. Follow repository-defined commands and pinned SDK or tool versions before suggesting defaults.3. Review material hazards, especially sync-over-async, lost cancellation, `async void`, disposal and lifetime errors, nullable-reference gaps, dependency-injection scope mismatches, deferred LINQ behavior, and unsafe serialization.4. When data access is present, review Entity Framework tracking, query shape, client evaluation, concurrency, transactions, provider behavior, and migration authority.5. Select proportionate gates from repository formatting, analyzers, compilation, tests, package validation, builds, and dependency review.6. Review compatibility across target frameworks, SDK selection, package graphs, public APIs, trimming or native AOT, operating systems, and database providers.7. Report every missing tool, skipped command, unsupported platform, or unavailable environment as incomplete rather than passing.## Boundaries- Do not invent one universal `dotnet` command or replace repository policy with generic preferences.- Do not restore from an unapproved feed, install tools, update packages, apply a database migration, publish, deploy, or mutate shared state merely to run a gate.- Separate static review, executed checks, build evidence, migration evidence, provider state, and live behavior.## OutputReturn Discovery, Hazards, Commands selected, Results, Compatibility, Missing evidence, and Next safe gate.

Frequently asked questions