skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
richlander/dotnet-inspect420 installs

dotnet-inspect-decompiler

Read .NET method and type implementations as authored-first source, decompiled C#, annotated source or IL; interpret reconstruction fidelity and locate exact code coordinates. Use --offline to prohibit network acquisition.

How do I install this agent skill?

npx skills add https://github.com/richlander/dotnet-inspect --skill dotnet-inspect-decompiler
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    This skill provides capabilities for decompiling and inspecting .NET assemblies using the dnx utility. It includes functionality for network-based symbol and package acquisition. While functionally sound for developers, the skill presents a surface for indirect prompt injection as it processes and displays untrusted binary data from assemblies without sanitization or boundary markers.

  • Socketpass

    No alerts

  • Snykwarn

    Risk: MEDIUM · 1 issue

What does this agent skill do?

dotnet-inspect: Read .NET Method Implementations as C# and IL

Use this skill to understand implementation from the assembly you have. Run dnx dotnet-inspect -y -- <command>. Package/PDB acquisition can use the network; --offline forbids it. Decompilation itself is local.

Choose the evidence for the question

dnx dotnet-inspect -y -- type JsonSerializer \
  --package System.Text.Json -S Source
dnx dotnet-inspect -y -- member JsonSerializer \
  --platform System.Text.Json Serialize:1 \
  -S "Decompiled Source,Annotated Source,IL" --offline
ViewWhat it establishes
SignatureAPI declaration, not implementation; the default for one selected overload.
SourceAuthored-first source with fallback and provider context retained.
PDB SourceOnly checksum-matched source selected through Portable PDB evidence.
Decompiled SourceLocally reconstructed, lowered C#; not the authored source.
Annotated SourceReconstructed C# with hidden facts and interleaved IL.
ILExact instructions, offsets, branches, tokens and calls.

One selected source payload normally renders native source; add --markdown for document framing. @Source is broader and can fetch PDB-mapped source. Use skill sourcelink when source provenance or checksum boundaries matter.

Choose overloads with Member Index, then reuse Name:N or a stable Name~digest. --all includes non-public and hidden targets. A restored --project needs current assets and output.

Follow deeper implementation evidence

dnx dotnet-inspect -y -- member --explain
dnx dotnet-inspect -y -- member JsonSerializer \
  --platform System.Text.Json Serialize:1 --explain
dnx dotnet-inspect -y -- member JsonSerializer \
  --platform System.Text.Json Serialize:1 -S IL -E .tips

--explain replaces ordinary stdout; Member -E preserves it and writes a companion explanation to stderr. -E .tips selects contextual suggestions. Use -D for available sections and -Q for query rules; a known source command does not need an explanation detour.

QuestionEntrance
Which bodies contain a rendered C# syntax kind?library -Q "Body Shapes" and explain "C# body kinds"
Which style choices changed the reconstruction?-S "Decompiled Source,Applied Taste" --taste on an exact Member
How can I emphasize one annotation family?-S "Annotated Source" --focus allocation on an exact Member
Why is reconstruction incomplete?-S "Fidelity Causes" on an exact Member
Where is a profiler/crash IL coordinate?library address 0x06000001+0x5 --library Foo.dll

Read returned bindings and vocabularies before unfamiliar syntax queries. Body Shapes locates rendered C# occurrences, not original file spans or IL offsets; whole-Library decompilation may be expensive. Narrow the subject before broad content searches.

--focus promotes matching annotations without filtering away other facts. Style options change spelling, not a runtime-cost or source-provenance claim. Load skill relationships for calls and skill performance for cost triage.

Interpret fidelity honestly

Fidelity degrades visibly from Full through Partial, StructuredOnly, IlOnly and Failed, with DEC#### diagnostics. A plausible reconstruction is not proof of faithful source semantics. Use Annotated Source or IL whenever exact execution structure matters.

Fidelity Causes distinguishes complete/no-causes, absent body and failed inspection. Preserve those outcomes instead of treating all empty results as success. If C# looks wrong, retain Decompiled Source, Annotated Source, IL and available PDB Source/Source Diff for comparison.

The coordinate entrance composes source-location, Member, instruction, exception, callsite and return-address context. Allocation, safety and cost are opt-in sections; discover them rather than assuming the default performs all analyses. Keep the exact Library build, MethodDef token and IL offset with every conclusion.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/richlander/dotnet-inspect/dotnet-inspect-decompiler">View dotnet-inspect-decompiler on skillZs</a>