dotnet-inspect

Query, compare, and explore .NET APIs from NuGet packages and local files.

1|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/Jeffreyyvdb/.dotfiles --skill dotnet-inspect-jeffreyyvdb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-inspect
Source: https://github.com/Jeffreyyvdb/.dotfiles/tree/main/.agents/skills/dotnet-inspect
Command: npx skills add https://github.com/Jeffreyyvdb/.dotfiles --skill dotnet-inspect-jeffreyyvdb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires dnx, and includes scripts (resource) components.

What problem does it solve?

This Skill helps developers quickly understand and interact with .NET APIs, saving time on API research and troubleshooting.

Core Features & Use Cases

  • API Exploration: Query .NET APIs from NuGet packages, platform libraries, and local files.
  • Version Comparison: Compare API changes between different versions.
  • Use Case: When working on a .NET project and need to find out the differences between two versions of a specific library, this Skill can help you quickly identify the changes.

Quick Start

Run the command dotnet-inspect member --oneline JsonSerializer --package System.Text.Json to get a list of all members in the JsonSerializer class from the System.Text.Json package.

Frequently Asked Questions about dotnet-inspect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I compare API changes between different versions of a .NET NuGet package?

To compare API changes across .NET library versions, you need a tool that queries NuGet packages and highlights member differences. This Skill queries those sources directly to help you quickly identify API modifications between releases.

Can I explore .NET APIs from local files and NuGet packages using a command-line interface?

Yes, you can explore .NET APIs from local files and NuGet packages using a command-line interface. This Skill provides commands like `member` to query and list API members from your specified package sources.

Do I need the .NET SDK and dnx tooling to inspect .NET APIs across libraries?

Yes, you need the .NET SDK and specific tooling like dnx to inspect .NET APIs. This Skill requires these dependencies to query and explore API structures across various platform libraries and packages.

Why should I use a dedicated CLI tool for .NET API research instead of manually browsing documentation?

Using a dedicated CLI tool for .NET API research saves time on troubleshooting by quickly querying and comparing APIs across packages. It provides a comprehensive interface to interact directly with API structures without manual browsing.