MSBuildLocator .NET Core Loader
microsoft/MSBuildLocator
Reference for how MSBuildLocator loads MSBuild assemblies and finds the .NET SDK on .NET Core hosts, for anyone editing or debugging that loader code.
Whole-assembly call-graph leverage ranking and performance triage for libraries (experimental).
Install Dotnet Inspect Performance
$ npx skills add richlander/dotnet-inspect --skill dotnet-inspect-performance -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install richlander/dotnet-inspect dotnet-inspect-performance --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/richlander/dotnet-inspect.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/performance .claude/skills/dotnet-inspect-performance && rm -rf skills-srcUse ~/.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/
Install the "dotnet-inspect-performance" agent skill from https://github.com/richlander/dotnet-inspect/tree/main/skills/performance into .claude/skills/dotnet-inspect-performance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dotnet-inspect-performance", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/richlander/dotnet-inspect/tree/main/skills/performanceType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add richlander/dotnet-inspect --skill dotnet-inspect-performance -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install richlander/dotnet-inspect dotnet-inspect-performance --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/richlander/dotnet-inspect.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/performance .agents/skills/dotnet-inspect-performance && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "dotnet-inspect-performance" agent skill from https://github.com/richlander/dotnet-inspect/tree/main/skills/performance into .agents/skills/dotnet-inspect-performance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dotnet-inspect-performance", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add richlander/dotnet-inspect --skill dotnet-inspect-performance -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install richlander/dotnet-inspect dotnet-inspect-performance --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/richlander/dotnet-inspect.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/performance .cursor/skills/dotnet-inspect-performance && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "dotnet-inspect-performance" agent skill from https://github.com/richlander/dotnet-inspect/tree/main/skills/performance into .cursor/skills/dotnet-inspect-performance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dotnet-inspect-performance", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/richlander/dotnet-inspect.git --path skills/performance--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add richlander/dotnet-inspect --skill dotnet-inspect-performance -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install richlander/dotnet-inspect dotnet-inspect-performance --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/richlander/dotnet-inspect.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/performance .gemini/skills/dotnet-inspect-performance && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "dotnet-inspect-performance" agent skill from https://github.com/richlander/dotnet-inspect/tree/main/skills/performance into .gemini/skills/dotnet-inspect-performance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dotnet-inspect-performance", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install richlander/dotnet-inspect dotnet-inspect-performanceInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add richlander/dotnet-inspect --skill dotnet-inspect-performance -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/richlander/dotnet-inspect.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/performance .github/skills/dotnet-inspect-performance && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "dotnet-inspect-performance" agent skill from https://github.com/richlander/dotnet-inspect/tree/main/skills/performance into .github/skills/dotnet-inspect-performance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dotnet-inspect-performance", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add richlander/dotnet-inspect --skill dotnet-inspect-performance -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install richlander/dotnet-inspect dotnet-inspect-performance --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/richlander/dotnet-inspect.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/performance .opencode/skills/dotnet-inspect-performance && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "dotnet-inspect-performance" agent skill from https://github.com/richlander/dotnet-inspect/tree/main/skills/performance into .opencode/skills/dotnet-inspect-performance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dotnet-inspect-performance", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
dotnet-inspect-performance- GitHub stars
- 151
- Token cost
- ~3.8k tokens
- SKILL.md length
- 1,616 words
- Files
- 1
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- None found
At a glance
Whole-assembly call-graph leverage ranking and performance triage for libraries (experimental).
- Tasks that involve Codebase onboarding
- SKILL.md covers Rank by leverage first, Triage against rewrite shapes, Select direct caller-loop… and Triage exception-path pool churn, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Dotnet Inspect Performance is an agent skill from richlander/dotnet-inspect. Whole-assembly call-graph leverage ranking and performance triage for libraries (experimental).
Its SKILL.md is about 3.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Codebase onboarding. It works with .NET. The repository describes itself as: Tool to inspect .NET assets, like docker inspect and kubectl describe.
When your agent uses it
- Tasks that involve Codebase onboarding
Example prompts
- “/dotnet-inspect-performance”
What it can do on your machine
Read from SKILL.md and the folder at commit 2b11462. 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 Performance loads about 3.8k tokens when it runs. Until then it costs about 31 tokens; SKILL.md has 1,616 words of instructions outside code blocks.
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
Without a licence we can't republish the file, so here is its outline and opening line. It has 1,616 words (~3,841 tokens).
“Use this skill to find the members worth optimizing or hardening first in a .NET assembly, and to triage them against actionable rewrite shapes. This analysis is experimental; section names and signal sets may change between releases.”
- name
- dotnet-inspect-performance
- version
- 0.1.0
Files
Just SKILL.md in skills/performance of richlander/dotnet-inspect.
Open the folder on GitHubat commit 2b11462
Compare with similar skills
Dotnet Inspect Performance 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Dotnet Inspect Performance this skillrichlander/dotnet-inspect | 151 | — | ~3.8k | Automated safety check: Pass | None | |
| MSBuildLocator .NET Core Loadermicrosoft/MSBuildLocator | 263 | — | ~1.1k | Automated safety check: Pass | Custom licence | |
| Codebase Knowledge Graph Q&AEgonex-AI/Understand-Anything | 86k | 1 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Understand ExplainEgonex-AI/Understand-Anything | 86k | 1 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Speckit ConstitutionWeihanLi/WeihanLi.Common | 242 | 11 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Repomix Codebase Exploreryamadashy/repomix | 29k | 1 repos | ~2.7k | Automated safety check: Pass | MIT |
Similar skills
- Official
Codebase Knowledge Graph Q&A
Egonex-AI/Understand-Anything
Answers questions about a codebase by searching a prebuilt knowledge graph of its files, functions, classes and dependencies, not by rereading every source file.
Understand Explain
Egonex-AI/Understand-Anything
Gives an in-depth explanation of one file, function or module by reading the project's knowledge graph and checking that the graph is still fresh.
Speckit Constitution
WeihanLi/WeihanLi.Common
Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.
Repomix Codebase Explorer
yamadashy/repomix
Packs a local or remote repository into a single AI-friendly file with the Repomix CLI, then reads and searches that output to explain structure, find patterns or report metrics.
- Official
Microsoft Code Reference
MicrosoftDocs/mcp
Find working code samples, verify API signatures, and fix Microsoft SDK errors using official docs.
More from richlander/dotnet-inspect
All 21 skills in this repoCorpus Maintenance
richlander/dotnet-inspect
A skill your agent uses for authored-source correspondence corpus maintenance: verify the vendored CIVIL/EVIL snapshot for drift against upstream, re-harvest or re-pin it, run the offline benchmark…
Daily Operations
richlander/dotnet-inspect
A skill your agent uses for daily chores in dotnet-inspect; establish release-candidate readiness, then inspect main CI, staging, performance, runtime-pin, security, dependency, and regression runs.
Deep Inspect
richlander/dotnet-inspect
A skill your agent uses when a dotnet-inspect change needs expensive evidence outside normal PR CI, or when preparing release certification; coordinate Deep Inspect lanes (full slow tests…
Deep Inspect Analysis
richlander/dotnet-inspect
A skill your agent uses for opt-in Deep Inspect run triage: test lane failures, census artifacts, pinned-subset drift, and routing findings into issues or tracker updates.
Dotnet Inspect Package Skills
richlander/dotnet-inspect
Discover and use version-matched agent skills from NuGet packages, and persist selected skills in a repository only when the user explicitly requests it.
Release
richlander/dotnet-inspect
A skill your agent uses when shipping a new dotnet-inspect version; independently validate one immutable candidate, present concerns, and publish only after the operator decides.
Related
Works with
Categories
Questions about Dotnet Inspect Performance
What does Dotnet Inspect Performance do?
Whole-assembly call-graph leverage ranking and performance triage for libraries (experimental). Dotnet Inspect Performance is an agent skill from richlander/dotnet-inspect. Whole-assembly call-graph leverage ranking and performance triage for libraries (experimental).
When should I use Dotnet Inspect Performance?
Dotnet Inspect Performance fits situations like: tasks that involve Codebase onboarding.
How do I install Dotnet Inspect Performance in Claude Code?
Run `npx skills add richlander/dotnet-inspect --skill dotnet-inspect-performance -a claude-code`. Or copy the skill folder (skills/performance in richlander/dotnet-inspect) into .claude/skills/dotnet-inspect-performance in your project. Claude Code loads it when a task matches its description.
How do I install Dotnet Inspect Performance in Codex?
Run `npx skills add richlander/dotnet-inspect --skill dotnet-inspect-performance -a codex`. Or copy the skill folder (skills/performance in richlander/dotnet-inspect) into .agents/skills/dotnet-inspect-performance in your project. Codex loads it when a task matches its description.
Can I use Dotnet Inspect Performance 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 richlander/dotnet-inspect --skill dotnet-inspect-performance -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-performance, .gemini/skills/dotnet-inspect-performance, .github/skills/dotnet-inspect-performance and .opencode/skills/dotnet-inspect-performance in your project.
What does Dotnet Inspect Performance need to run?
SKILL.md names no scripts, command-line tools or credentials: Dotnet Inspect Performance is instructions for the agent only.
Does Dotnet Inspect Performance 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 Performance 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 Performance use?
No licence was found for Dotnet Inspect Performance or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Dotnet Inspect Performance use?
About 3.8k tokens (SKILL.md is roughly 15k 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 Performance?
Skills that share tags, products or a category with Dotnet Inspect Performance: MSBuildLocator .NET Core Loader (microsoft/MSBuildLocator, 263 stars), Codebase Knowledge Graph Q&A (Egonex-AI/Understand-Anything, 86k stars), Understand Explain (Egonex-AI/Understand-Anything, 86k stars) and Speckit Constitution (WeihanLi/WeihanLi.Common, 242 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Dotnet Inspect Performance?
richlander (a GitHub user) maintains it in richlander/dotnet-inspect, which has 151 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 8, 2026.
Source: richlander/dotnet-inspect on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.