dotnet-inspect — Claude Code skill: inspect .NET packages and APIs
A skill that pulls evidence about .NET packages, libraries and APIs instead of guessing: what ships inside, which dependencies, how versions differ.
npx skills add richlander/dotnet-inspect --skill dotnet-inspect -a claude-codeWhat dotnet-inspect does
The skill drives the dotnet-inspect CLI, invoked as dnx dotnet-inspect -y -- <command>. The -y flag skips the confirmation prompt, and -- hands the remaining arguments to the tool. From there you pick a query space: package, type, member, find, diff, library.
Platform lookups lean on installed packs when the version you ask for is present; otherwise a package-backed source fills in. On a non-conventional install, check <root>/packs and set DOTNET_ROOT for the process rather than through PATH — skip that and platform searches miss the version you meant.
A router handles vague requests: hand it a bare target and let it pick the route. explain <task-text> similarity-searches installed capabilities, and demo list surfaces ready-made scenarios. For version work, diff --package [email protected] --breaking flags breaking changes, while diff --history traces how an API evolved.
What it helps with
- pin down an exact package ID from a partial name
- list public and hidden members of a type
- compare two package versions for breaking changes
- trace how a method changed across releases
- check licenses and SourceLink mappings inside a package
Example prompts for the agent
- Find the Microsoft.Extensions.AI.Abstractions package and list the types it contains
- Compare the API of package Foo between versions 1.0 and 2.0 and show breaking changes
- Walk me through building a literal query using
explain literal
How to install dotnet-inspect
1Skills CLI (Vercel)
npx skills add richlander/dotnet-inspect --skill dotnet-inspect -a claude-code2Manually: put the files in place
~/.claude/skills/dotnet-inspect/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/dotnet-inspect/
1Skills CLI (Vercel)
npx skills add richlander/dotnet-inspect --skill dotnet-inspect -a codex2Manually: put the files in place
.agents/skills/dotnet-inspect/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add richlander/dotnet-inspect --skill dotnet-inspect -a cursor2Manually: put the files in place
.cursor/skills/dotnet-inspect/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install richlander/dotnet-inspect dotnet-inspect2Manually: put the files in place
.github/skills/dotnet-inspect/SKILL.md1Skills CLI (Vercel)
npx skills add richlander/dotnet-inspect --skill dotnet-inspect -a gemini-cli2Platform CLI
gemini skills install https://github.com/richlander/dotnet-inspect --path skills/dotnet-inspectManually: put the files in place
.devin/skills/dotnet-inspect/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add richlander/dotnet-inspect --skill dotnet-inspect -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about dotnet-inspect
How do I install dotnet-inspect in Claude Code?
Run npx skills add richlander/dotnet-inspect --skill dotnet-inspect -a claude-code. The skill lands at ~/.claude/skills/dotnet-inspect/SKILL.md.
What does dotnet-inspect do?
It gathers evidence about .NET packages, libraries, APIs, dependencies and version changes. Sources include local libraries, packages from configured feeds and platform assemblies.
What does the skill need to run?
The tool itself runs through dnx dotnet-inspect. On a non-conventional .NET install, check <root>/packs and set DOTNET_ROOT for the process.
