Transferred from dotnet/skills#981 — originally filed by @verdie-g.
When using a NuGet package, it would be useful for an AI agent to explore its API (including XML docs) without relying solely on LSP. The proposal outlines a tiered approach:
- Locate the package/type in the local NuGet cache (
~/.nuget/packages/)
- Read shipped XML docs next to the DLL
- Enumerate public surface via reflection
- Resolve real source files via Source Link embedded in PDBs
- Shallow-clone the source repo as a last resort
A full skill draft and a download-sourcelink.cs helper script are included in the original issue.
Credit to @verdie-g for the detailed proposal and implementation sketch.
Transferred from dotnet/skills#981 — originally filed by @verdie-g.
When using a NuGet package, it would be useful for an AI agent to explore its API (including XML docs) without relying solely on LSP. The proposal outlines a tiered approach:
~/.nuget/packages/)A full skill draft and a
download-sourcelink.cshelper script are included in the original issue.Credit to @verdie-g for the detailed proposal and implementation sketch.