Dotnet Tooling logo

Dotnet Tooling

Organization
novotnyllc
dotnet-tooling

Manages .NET SDK installation (dotnet-install, workloads), project setup (.slnx, Directory.Build.props, CPM), MSBuild authoring, build optimization, performance (Span, ArrayPool, stackalloc), profiling (dotnet-counters, dotnet-trace), Native AOT/trimming, GC tuning, CLI apps (System.CommandLine, Spectre.Console, Terminal.Gui), ILSpy decompilation, VS Code debug config (launch.json, coreclr, remote), C# LSP (csharp-ls, OmniSharp), and version detection/upgrade. Spans 34 topic areas. Do not use for UI implementation or API security design.

Overview

Publishernovotnyllc
Repositorydotnet-artisan
Skill namedotnet-tooling
Stars
235
Forks
14
Bundled files
36
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 36 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by novotnyllc on GitHub. Read the source before you install it.

Installation

Install the Dotnet Tooling AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/novotnyllc/dotnet-artisan/tree/main/plugins/dotnet-artisan/skills/dotnet-tooling
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/novotnyllc/dotnet-artisan.git /tmp/dotnet-artisan
mkdir -p .claude/skills
cp -r /tmp/dotnet-artisan/plugins/dotnet-artisan/skills/dotnet-tooling .claude/skills/dotnet-tooling
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Dotnet Tooling in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Dotnet Tooling on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Dotnet Tooling is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

dotnet-tooling

Overview

.NET project setup, build systems, performance, CLI apps, and developer tooling. This consolidated skill spans 34 topic areas. Load the appropriate companion file from references/ based on the routing table below.

Routing Table

TopicKeywordsDescriptionCompanion File
Project structuresolution, .slnx, CPM, analyzers.slnx, Directory.Build.props, CPM, analyzersreferences/project-structure.md
Scaffold projectdotnet new, CPM, SourceLink, editorconfigdotnet new with CPM, analyzers, editorconfig, SourceLinkreferences/scaffold-project.md
Csproj readingPropertyGroup, ItemGroup, CPM, propsSDK-style .csproj, PropertyGroup, ItemGroup, CPMreferences/csproj-reading.md
MSBuild authoringtargets, props, conditions, Directory.BuildTargets, props, conditions, Directory.Build patternsreferences/msbuild-authoring.md
MSBuild tasksITask, ToolTask, inline tasks, UsingTaskITask, ToolTask, IIncrementalTask, inline tasksreferences/msbuild-tasks.md
Build analysisMSBuild output, NuGet errors, analyzer warningsMSBuild output, NuGet errors, analyzer warningsreferences/build-analysis.md
Build optimizationslow builds, binary logs, parallel, restoreSlow builds, binary logs, parallel, restorereferences/build-optimization.md
Artifacts outputUseArtifactsOutput, ArtifactsPath, CI/DockerUseArtifactsOutput, ArtifactsPath, CI/Docker impactreferences/artifacts-output.md
Multi-targetingmultiple TFMs, polyfills, conditional compilationMultiple TFMs, PolySharp, conditional compilationreferences/multi-targeting.md
Performance patternsSpan, ArrayPool, ref struct, sealed, stackallocSpan, ArrayPool, ref struct, sealed, stackallocreferences/performance-patterns.md
Profilingdotnet-counters, dotnet-trace, flame graphsdotnet-counters, dotnet-trace, dotnet-dump, flame graphsreferences/profiling.md
Native AOTPublishAot, ILLink, P/Invoke, size optimizationPublishAot, ILLink descriptors, P/Invoke, size optimizationreferences/native-aot.md
AOT architecturesource gen, AOT-safe DI, serializationSource gen over reflection, AOT-safe DI, factoriesreferences/aot-architecture.md
Trimmingannotations, ILLink, IL2xxx warnings, IsTrimmableAnnotations, ILLink, IL2xxx warnings, IsTrimmablereferences/trimming.md
GC/memoryGC modes, LOH/POH, Span/Memory, ArrayPoolGC modes, LOH/POH, Gen0/1/2, Span/Memory, ArrayPoolreferences/gc-memory.md
CLI architecturecommand/handler/service, clig.dev, exit codesCommand/handler/service, clig.dev, exit codesreferences/cli-architecture.md
System.CommandLineRootCommand, Option, SetAction, parsingSystem.CommandLine 2.0, RootCommand, Optionreferences/system-commandline.md
Spectre.Consoletables, trees, progress, prompts, live displaysTables, trees, progress, prompts, live displaysreferences/spectre-console.md
Terminal.Guiviews, layout, menus, dialogs, bindings, themesTerminal.Gui v2, views, layout, menus, dialogsreferences/terminal-gui.md
CLI distributionAOT vs framework-dependent, RID matrix, Homebrew, winget, Scoop, dotnet toolDistribution strategy, single-file publish, per-platform packagingreferences/cli-distribution.md
CLI release pipelineGHA build matrix, artifact staging, checksumsGHA build matrix, artifact staging, checksumsreferences/cli-release-pipeline.md
Documentation strategyStarlight, Docusaurus, DocFX decision treeStarlight, Docusaurus, DocFX decision treereferences/documentation-strategy.md
Tool managementglobal, local, manifests, restore, pinningGlobal/local tools, manifests, restore, pinningreferences/tool-management.md
Version detectionTFM/SDK from .csproj, global.jsonTFM/SDK from .csproj, global.json, Directory.Buildreferences/version-detection.md
Version upgradeLTS-to-LTS, staged, preview, upgrade pathsLTS-to-LTS, staged through STS, preview pathsreferences/version-upgrade.md
Solution navigationentry points, .sln/.slnx, dependency graphsEntry points, .sln/.slnx, dependency graphsreferences/solution-navigation.md
Project analysissolution layout, build config analysisSolution layout, build config, .csproj analysisreferences/project-analysis.md
Modernizeoutdated TFMs, deprecated packages, patternsOutdated TFMs, deprecated packages, superseded patternsreferences/modernize.md
Add analyzersnullable, trimming, AOT compat, severity configNullable, trimming, AOT compat analyzers, severityreferences/add-analyzers.md
SDK installationinstall .NET, dotnet-install, workloads, missing SDK.NET SDK install script, workloads, env vars, side-by-sidereferences/dotnet-sdk-install.md
ILSpy decompileilspycmd, decompile, assembly, disassemble, ILILSpy/ilspycmd decompilation, type listing, IL viewreferences/ilspy-decompile.md
Mermaid diagramsarchitecture, sequence, class, ER, flowchartsArchitecture, sequence, class, deployment, ER diagramsreferences/mermaid-diagrams.md
VS Code debugginglaunch.json, tasks.json, coreclr, attach, debugVS Code launch/attach configs, tasks, multi-project, hot reloadreferences/vscode-debug.md
C# LSPlanguage server, csharp-ls, OmniSharp, go to definitionC# LSP servers, code navigation, agent usage patternsreferences/csharp-lsp.md

Scope

  • Solution structure and project scaffolding
  • MSBuild authoring and build optimization
  • Performance patterns and profiling
  • Native AOT, trimming, and GC tuning
  • CLI app development (System.CommandLine, Spectre.Console, Terminal.Gui)
  • Documentation generation (DocFX)
  • Tool management and version detection/upgrade
  • Solution navigation and project analysis
  • Code modernization and analyzer configuration
  • Mermaid diagram generation
  • VS Code debug configuration (launch.json, tasks.json, coreclr)
  • C# LSP servers (csharp-ls, OmniSharp) for agent code navigation

Out of scope

  • Crash dump analysis, hang/deadlock triage, live debugger attach -> dotnet-debugging
  • Web API patterns -> dotnet-api
  • Test authoring -> dotnet-testing
  • CI/CD pipelines -> dotnet-devops
  • C# language patterns -> dotnet-csharp
  • UI framework development -> dotnet-ui

Scripts

  • scripts/scan-dotnet-targets.py -- Scan repository for .NET TFM and SDK version signals

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Dotnet Tooling AI skill do?

Manages .NET SDK installation (dotnet-install, workloads), project setup (.slnx, Directory.Build.props, CPM), MSBuild authoring, build optimization, performance (Span, ArrayPool, stackalloc), profiling (dotnet-counters, dotnet-trace), Native AOT/trimming, GC tuning, CLI apps (System.CommandLine, Spectre.Console, Terminal.Gui), ILSpy decompilation, VS Code debug config (launch.json, coreclr, remote), C# LSP (csharp-ls, OmniSharp), and version detection/upgrade. Spans 34 topic areas. Do not use for UI implementation or API security design.

Why use Dotnet Tooling on TypingMind?

Because you install it once and use it with any model. Dotnet Tooling is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Dotnet Tooling in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/novotnyllc/dotnet-artisan/tree/main/plugins/dotnet-artisan/skills/dotnet-tooling. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Dotnet Tooling?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Dotnet Tooling?

As many as you like. As long as a model supports skills, you can use Dotnet Tooling with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Dotnet Tooling AI skill free?

Yes. It is published on GitHub by novotnyllc under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇