Agent skill

Dotnet Inspect

by CommunityToolkit in CommunityToolkit/Aspire

Query .NET APIs across NuGet packages, platform libraries, and local files.

MITAuto-check passed

Install Dotnet Inspect

skills CLI
$ npx skills add CommunityToolkit/Aspire --skill dotnet-inspect -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install CommunityToolkit/Aspire dotnet-inspect --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/CommunityToolkit/Aspire.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/dotnet-inspect .claude/skills/dotnet-inspect && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
dotnet-inspect
GitHub stars
629
Used in
2 other repos
Token cost
~1.5k tokens
SKILL.md length
555 words
Files
1
Skills in repo
8
Repo updated
First seen
Licence
MIT

At a glance

Query .NET APIs across NuGet packages, platform libraries, and local files.

  • You need to answer questions about .NET library contents
  • SKILL.md covers Quick Decision Tree, When to Use This Skill, Key Patterns and Search Scope, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Dotnet Inspect is an agent skill from CommunityToolkit/Aspire. Query .NET APIs across NuGet packages, platform libraries, and local files. Search for types, list API surfaces, compare and diff versions, find extension methods and implementors. Use whenever you need to answer questions about .NET library contents.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with .NET. The repository describes itself as: A community project with additional components and extensions for Aspire. The licence is MIT.

When your agent uses it

  • You need to answer questions about .NET library contents

Example prompts

  • “/dotnet-inspect”

What it can do on your machine

Read from SKILL.md and the folder at commit 69a155d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Dotnet Inspect loads about 1.5k tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 555 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~67
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from CommunityToolkit/Aspire at commit 69a155d, republished under its MIT licence (© CommunityToolkit). 555 words, ~1,520 tokens.

Download SKILL.mdSave it as .claude/skills/dotnet-inspect/SKILL.md (or your agent's skills folder).
name
dotnet-inspect
description
Query .NET APIs across NuGet packages, platform libraries, and local files. Search for types, list API surfaces, compare and diff versions, find extension methods and implementors. Use whenever you need to answer questions about .NET library contents.

dotnet-inspect

Query .NET library APIs — the same commands work across NuGet packages, platform libraries (System., Microsoft.AspNetCore.), and local .dll/.nupkg files.

Quick Decision Tree

  • Code broken? → diff --package Foo@old..new first, then member --oneline
  • Need API surface? → member Type --package Foo --oneline (token-efficient)
  • Need signatures? → member Type --package Foo -m Method (default shows full signatures + docs)
  • Need source/IL? → member Type --package Foo -m Method -v:d (adds Source, Lowered C#, IL)
  • Need constructors? → member 'Type<T>' --package Foo -m .ctor (use <T> not <>)
  • Need all overloads? → member Type --package Foo --select (shows Name:N indices)

When to Use This Skill

  • "What types are in this package?" — type discovers types (terse), find searches by pattern
  • "What's the API surface?" — type for discovery, member for detailed inspection (docs on)
  • "What changed between versions?" — diff classifies breaking/additive changes
  • "This code uses an old API — fix it" — diff the old..new version, then member --oneline to see the new API
  • "What extends this type?" — extensions finds extension methods/properties
  • "What implements this interface?" — implements finds concrete types
  • "What does this type depend on?" — depends walks the type hierarchy upward
  • "What version/metadata does this have?" — package and library inspect metadata
  • "Show me something cool" — demo runs curated showcase queries

Key Patterns

Use --oneline as the default for scanning — it works on type, member, find, diff, and implements:

bash
dnx dotnet-inspect -y -- member JsonSerializer --package System.Text.Json --oneline  # scan members
dnx dotnet-inspect -y -- type --package System.Text.Json --oneline                   # scan types
dnx dotnet-inspect -y -- diff --package System.CommandLine@2.0.0-beta4.22272.1..2.0.3 --oneline  # triage changes

Use --shape to understand a type's hierarchy and surface at a glance:

bash
dnx dotnet-inspect -y -- type 'HashSet<T>' --platform System.Collections --shape

Use diff first when fixing broken code — --oneline for triage, then full detail on specific types:

bash
dnx dotnet-inspect -y -- diff --package System.CommandLine@2.0.0-beta4.22272.1..2.0.3 --oneline  # what changed?
dnx dotnet-inspect -y -- diff -t Command --package System.CommandLine@2.0.0-beta4.22272.1..2.0.3  # detail on Command
dnx dotnet-inspect -y -- member Command --package System.CommandLine@2.0.3 --oneline              # new API surface

Search Scope

Search commands (find, extensions, implements, depends) use scope flags:

  • (no flags) — platform frameworks + Microsoft.Extensions.AI
  • --platform — all platform frameworks
  • --extensions — curated Microsoft.Extensions.* packages
  • --aspnetcore — curated Microsoft.AspNetCore.* packages
  • --package Foo — specific NuGet package (combinable with scope flags)

type, member, library, diff accept --platform <name> as a string for a specific platform library.

Show full SKILL.md (260 more words)Show less

Command Reference

CommandPurpose
typeDiscover types — terse output, no docs, use --shape for hierarchy
memberInspect members — docs on by default, supports dotted syntax (-m Type.Member)
findSearch for types by glob pattern across any scope
diffCompare API surfaces between versions — breaking/additive classification
extensionsFind extension methods/properties for a type
implementsFind types implementing an interface or extending a base class
dependsWalk the type dependency hierarchy upward (interfaces, base classes)
packagePackage metadata, files, versions, dependencies, search for NuGet discovery
libraryLibrary metadata, symbols, references, dependencies
demoRun curated showcase queries — list, invoke, or feeling-lucky

Output Limiting

Do not pipe output through head, tail, or Select-Object. The tool has built-in line limiting that preserves headers and formatting:

bash
dnx dotnet-inspect -y -- member JsonSerializer --package System.Text.Json --oneline -10  # first 10 lines
dnx dotnet-inspect -y -- find "*Logger*" -n 5                                            # first 5 lines
dnx dotnet-inspect -y -- member JsonSerializer --package System.Text.Json -v:q -s Methods  # select specific section
  • -n N or -N — line limit, like head. Keeps headers, truncates cleanly.
  • -s Section — show only a specific section (glob-capable). Use -s alone to list available sections.
  • -v:q — quiet verbosity for compact summary output.

Key Syntax

  • Generic types need quotes: 'Option<T>', 'IEnumerable<T>'
  • Use <T> not <> for generic types — "Option<>" resolves to the abstract base, 'Option<T>' resolves to the concrete generic with constructors
  • type uses -t for type filtering, member uses -m for member filtering (not --filter)
  • Dotted syntax for member: -m JsonSerializer.Deserialize
  • Diff ranges use ..: --package System.Text.Json@9.0.0..10.0.0
  • Signatures include params and default values from metadata
  • Derived types only show their own members — query the base type too (e.g., RootCommand inherits Add() and SetAction() from Command)

Installation

Use dnx (like npx). Always use -y and -- to prevent interactive prompts:

bash
dnx dotnet-inspect -y -- <command>

Full Documentation

For comprehensive syntax, edge cases, and the flag compatibility matrix:

bash
dnx dotnet-inspect -y -- llmstxt

© CommunityToolkit, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/dotnet-inspect of CommunityToolkit/Aspire.

Open the folder on GitHubat commit 69a155d

Used in 2 other repositories

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in CommunityToolkit/Aspire, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Dotnet Inspect next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Dotnet Inspect compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Dotnet Inspect this skillCommunityToolkit/Aspire6292 repos~1.5kAutomated safety check: PassMIT
Minimax DOCXpoco-ai/poco-claw1.4k7 repos~3.9kAutomated safety check: PassMIT
Microsoft Skill CreatorMicrosoftDocs/mcp1.9k3 repos~2.1kAutomated safety check: PassCC-BY-4.0
Speckit ConstitutionWeihanLi/WeihanLi.Common24211 repos~2.1kAutomated safety check: PassApache-2.0
Copilot Session Failure Analysisdotnet/maui23k—~3.4kAutomated safety check: PassMIT
Microsoft Code ReferenceMicrosoftDocs/mcp1.9k4 repos~1.1kAutomated safety check: PassCC-BY-4.0

Similar skills

  • Minimax DOCX

    poco-ai/poco-claw

    Professional DOCX document creation, editing, and formatting using OpenXML SDK (.NET).

    1.4k GitHub starsUsed in 7 repos~3.9k tokens
    Documents & OfficeAuto-check passed
  • Microsoft Skill Creator

    MicrosoftDocs/mcp

    Official

    Create agent skills for Microsoft technologies using official documentation.

    1.9k GitHub starsUsed in 3 repos~2.1k tokens
    Agent WorkflowsAuto-check passed
  • Speckit Constitution

    WeihanLi/WeihanLi.Common

    Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.

    242 GitHub starsUsed in 11 repos~2.1k tokens
    DevelopmentAuto-check passed
  • Mines local Copilot CLI session logs for dotnet/maui to rank costly or failing runs, tag recurring failure modes, propose repo edits and emit guard evals.

    23k GitHub stars~3.4k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Microsoft Code Reference

    MicrosoftDocs/mcp

    Official

    Find working code samples, verify API signatures, and fix Microsoft SDK errors using official docs.

    1.9k GitHub starsUsed in 4 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Official

    Audits and updates os-packages.json files listing the Linux packages each .NET release needs per distro, then regenerates the Markdown from the JSON.

    22k GitHub stars~2.3k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

More from CommunityToolkit/Aspire

All 8 skills in this repo
  • Aspire Monitoring

    CommunityToolkit/Aspire

    ANALYSIS SKILL - Observe Aspire apps: logs, traces, metrics, resource state, telemetry export, browser telemetry, and the standalone dashboard.

    629 GitHub stars~3.5k tokensUpdated today
    Auto-check passed
  • Aspireify

    CommunityToolkit/Aspire

    WORKFLOW SKILL - Wire Aspire AppHosts or repair TypeScript AppHost toolchains.

    629 GitHub stars~5.3k tokensUpdated today
    Auto-check: notes
  • Aspire Deployment

    CommunityToolkit/Aspire

    WORKFLOW SKILL — Deploy Aspire apps from AppHost models to Docker Compose, Kubernetes, Azure, AWS, or preview Radius.

    629 GitHub stars~4.5k tokensUpdated today
    Auto-check: notes
  • Aspire Project V2 Migration

    CommunityToolkit/Aspire

    WORKFLOW SKILL - Safely migrates eligible Aspire 13.6+ AppHosts from legacy ProjectResource APIs to experimental DotnetProjectResource APIs after a per-resource assessment and explicit approval of…

    629 GitHub stars~3.4k tokensUpdated today
    Auto-check passed
  • Aspire Typescript Apphost

    CommunityToolkit/Aspire

    Generate a TypeScript AppHost from an existing C example AppHost, then add a TypeScriptAppHostTest-based integration test.

    629 GitHub stars~739 tokensUpdated today
    Auto-check passed
  • Aspire Upgrade

    CommunityToolkit/Aspire

    Update the Aspire version in the repository to the latest nightly build.

    629 GitHub stars~817 tokensUpdated today
    Auto-check passed

Works with

Questions about Dotnet Inspect

What does Dotnet Inspect do?

Query .NET APIs across NuGet packages, platform libraries, and local files. Dotnet Inspect is an agent skill from CommunityToolkit/Aspire.NET APIs across NuGet packages, platform libraries, and local files.

When should I use Dotnet Inspect?

Dotnet Inspect fits situations like: you need to answer questions about .NET library contents.

How do I install Dotnet Inspect in Claude Code?

Run `npx skills add CommunityToolkit/Aspire --skill dotnet-inspect -a claude-code`. Or copy the skill folder (.agents/skills/dotnet-inspect in CommunityToolkit/Aspire) into .claude/skills/dotnet-inspect in your project. Claude Code loads it when a task matches its description.

How do I install Dotnet Inspect in Codex?

Run `npx skills add CommunityToolkit/Aspire --skill dotnet-inspect -a codex`. Or copy the skill folder (.agents/skills/dotnet-inspect in CommunityToolkit/Aspire) into .agents/skills/dotnet-inspect in your project. Codex loads it when a task matches its description.

Can I use Dotnet Inspect in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add CommunityToolkit/Aspire --skill dotnet-inspect -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dotnet-inspect, .gemini/skills/dotnet-inspect, .github/skills/dotnet-inspect and .opencode/skills/dotnet-inspect in your project.

What does Dotnet Inspect need to run?

SKILL.md names no scripts, command-line tools or credentials: Dotnet Inspect is instructions for the agent only.

Does Dotnet Inspect access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Dotnet Inspect safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Dotnet Inspect use?

Dotnet Inspect is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Dotnet Inspect use?

About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Dotnet Inspect?

Skills that share tags, products or a category with Dotnet Inspect: Minimax DOCX (poco-ai/poco-claw, 1.4k stars), Microsoft Skill Creator (MicrosoftDocs/mcp, 1.9k stars), Speckit Constitution (WeihanLi/WeihanLi.Common, 242 stars) and Copilot Session Failure Analysis (dotnet/maui, 23k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Dotnet Inspect?

CommunityToolkit (a GitHub organization) maintains it in CommunityToolkit/Aspire, which has 629 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 6, 2026.

Source: CommunityToolkit/Aspire on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.