dotnet-inspect

An interactive tool for inspecting .NET code and metadata.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/vip32/TaskFlow --skill dotnet-inspect-vip32
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-inspect
Source: https://github.com/vip32/TaskFlow/tree/main/.agents/skills/dotnet-inspect
Command: npx skills add https://github.com/vip32/TaskFlow --skill dotnet-inspect-vip32

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers understand the structure, APIs, and contents of .NET assemblies and NuGet packages, streamlining debugging and development.

Core Features & Use Cases

  • API Discovery: Examine types, members, and hierarchy within .NET assemblies.
  • Package Exploration: View metadata, files, and versions of NuGet packages.
  • API Comparison: Track changes between different versions of a package's API surface.
  • Use Case: When integrating a new NuGet package, use this Skill to quickly understand its public API and available types without needing to compile or run code.

Quick Start

Use the dotnet-inspect skill to understand the API shape of the JsonSerializer type within 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 inspect a .NET assembly to see its public API surface?

You inspect .NET assemblies to examine type structures, members, and hierarchy. This allows you to explore package details and understand the public API surface without needing to compile or run your code.

What is the best way to compare API versions of a NuGet package?

Comparing NuGet package API versions helps track changes between different releases. You can inspect the package contents to audit assembly properties and compare the exposed API surfaces across versions.

Do I need the .NET SDK to explore NuGet package contents?

Yes, exploring NuGet package contents requires the .NET SDK. The process uses dnx for execution to facilitate .NET development by enabling exploration of package details, files, and versions.

Can I audit .NET assembly properties like SourceLink and determinism?

You can audit .NET assembly properties like SourceLink and determinism by inspecting the assembly. This helps verify package contents and understand compilation attributes during integration.

How do I view types within a NuGet package before integrating it?

View types within a NuGet package by inspecting its assemblies to understand the API shape. This enables quick exploration of available types and package metadata before you integrate it into your project.