Plugin
The whole .NET plugin: every skill it ships, each with its full file, and a single command that installs the lot.
3 skills
A skill is plain Markdown. The agent loads it on its own when the task matches its description.
/plugin marketplace add https://jesusprodriguez.com/skills/marketplace.json
/plugin install dotnet@jprodriguez-toolkitThe native route, and the only one that updates itself: add the marketplace once and `/plugin marketplace update` brings in new versions. Skills get their own namespace (`azure-devops:azure-pr-review`).
SKILL=azure-pr-review
curl -fsSL https://jesusprodriguez.com/skills/$SKILL/SKILL.md --create-dirs -o .claude/skills/$SKILL/SKILL.mdOne command at the root of your project. Claude Code discovers it on its own: nothing to register.
$SKILL = "azure-pr-review"
New-Item -ItemType Directory -Force ".claude/skills/$SKILL" | Out-Null
Invoke-WebRequest "https://jesusprodriguez.com/skills/$SKILL/SKILL.md" -OutFile ".claude/skills/$SKILL/SKILL.md"One command at the root of your project. Claude Code discovers it on its own: nothing to register.
curl -fsSL https://jesusprodriguez.com/skills/install.sh -o install.sh
sh install.sh --allDownload the script, read it, run it. Installs one skill, a whole stack or all of them, and pulls in the dependencies between skills. With `--check` it compares the sha256 of what you have installed and lists only what changed.
Build · .NET Core
Structure and checklist for a REST API in .NET 8: Minimal APIs per resource, EF Core without N+1, and errors as ProblemDetails.
when: When creating endpoints, modelling entities with EF Core or debugging slow queries.
How to ask
Build the orders endpoint in .NET 8, following the structure the project already has.
Minimal APIs · EF Core · ProblemDetails · Configuration and secrets
A targeted hunt for correctness bugs in C# and TypeScript: concurrency, nulls, dates, half-finished transactions and swallowed errors.
when: When hunting bugs, reviewing a suspicious module or making sense of an intermittent failure.
How to ask
Hunt for correctness bugs in the billing module: an amount comes out wrong every now and then.
Follow the data · Async and concurrency · Dates and decimals · Reports with a scenario
Document · .NET Core
Checking the official docs before writing code against Azure or .NET SDKs: that the method exists, that the signature is right, and that the pattern is not deprecated.
when: When using a Microsoft API for the first time, or when an error does not match what you expected.
How to ask
Check the official docs on whether BlobClient.UploadAsync accepts that overload.
Queries that narrow down · Verifying signatures · Mixed SDK versions · Deprecated patterns