Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
This skill enables developers to inspect the inner workings of .NET APIs by decompiling binaries into readable code. It is designed for those who need to audit framework implementations or understand the source of third-party NuGet packages when original code is unavailable.
WHO IT'S FOR
.NET Backend Engineers
inspecting internal .NET API implementations
Security Researchers
analyzing compiled .NET binaries for vulnerabilities
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.
Installs: The selected ilspy-decompile skill · Claude Code
Before you start
.NET 10 SDK or newer
In a terminal, run this from the project where Claude Code should use the skill. Replace every occurrence of the author-provided <skill-name> placeholder with ilspy-decompile while retaining the rest of the paths and URL.
Path to the compiled .NET assembly replacing <assembly-path>
API, class, or method of interest replacing <API-or-type>
Use the ilspy-decompile skill to inspect the implementation of <API-or-type> in the .NET assembly at <assembly-path>. Treat <assembly-path> as the path to my DLL and <API-or-type> as the API, class, or method I want to understand. If the exact type name is unknown, list the assembly's classes first; then decompile the relevant type and briefly explain the implementation details.
Claude
Copilot