How do I install the Prefer Dotnet Inspect skill?

Run npx skillmds@latest add richlander/prefer-dotnet-inspect 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 Prefer Dotnet Inspect 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 Prefer Dotnet Inspect?

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 Prefer Dotnet Inspect free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Prefer Dotnet Inspect?

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

Prefer Dotnet Inspect by richlander

Name: Prefer Dotnet Inspect
Author: richlander

Prefer Dotnet Inspect

How to fetch a NuGet package's own authoritative docs with the dotnet-inspect CLI before writing or editing code against it. Use whenever a task requires calling or implementing against a NuGet package's API — especially a package you are not fully confident about. The key rule: run `dotnet-inspect package <id>@<version> --readme`, which returns the package's best shipped doc, and prefer it over guessing or relying on training memory. This is a discovery directive only; it contains no package-specific API content.

richlander Updated Sep 21, 2026

File contents

Finding package guidance: fetch it with dotnet-inspect

When you must use a NuGet package's API and want authoritative, version-specific guidance, fetch the package's own shipped docs with the dotnet-inspect CLI instead of guessing or relying on possibly-stale training memory.

dotnet-inspect is a global .NET tool already on your PATH. It reads the package (from the restored NuGet cache or the feed) and prints its documentation. It does HTTP itself; you do not need a web tool.

Workflow when you must use a package whose API you are unsure of:

Identify the package id and the exact version from the project (PackageReference / Directory.Packages.props) — e.g. Markout 0.13.6. Always pass the referenced version so you read the docs for the version the project actually uses.
Fetch the package's best doc:
```
dotnet-inspect package <id>@<version> --readme
```
--readme returns the single best shipped doc, preferring a short, agent-targeted one over README.md (long, human-oriented) over PACKAGE.md. Follow it directly — it is written for the version you are on.

This keeps you on the package's intended, current API for the exact version referenced, and avoids reconstructing it from training memory or mining a long README.

Frequently asked questions