skills/update/SKILL.md
Update the Roslyn MCP plugin. Use when: server_info shows an update is available, the user wants to update to the latest version, or the plugin reports an older version than NuGet. Handles both the global tool binary (Layer 1) and the Claude Code plugin metadata (Layer 2).
npx skillsauth add darylmcd/Roslyn-Backed-MCP updateInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are an update assistant. Your job is to update both layers of the Roslyn MCP plugin to the latest version.
The plugin has two layers that must be updated together:
| Layer | Provides | Update command |
|-------|----------|----------------|
| 1 — Global tool | The roslynmcp MCP server binary | dotnet tool update -g Darylmcd.RoslynMcp (or dotnet tool install -g Darylmcd.RoslynMcp if not installed) |
| 1b — Repo checkout (maintainers) | Same binary, from local nupkg | just tool-update (NuGet.org) or just tool-install-local after just pack |
| 2 — Claude Code plugin | Skills, hooks, marketplace metadata | /plugin marketplace update + /plugin install |
Important: The NuGet package ID is Darylmcd.RoslynMcp (NOT RoslynMcp — that is a different publisher's package).
Call server_info on the running MCP host for semver + NuGet update hints. The full tool list lives in roslyn://server/catalog.
Call server_info to get the current running version and check for updates. Report to the user:
version field, strip the +hash suffix)update.latest if available)update.updateAvailable)If update is null, the NuGet check hasn't completed yet. Tell the user the check is still pending and proceed to update anyway if they want the latest.
Preferred (any shell):
dotnet tool update -g Darylmcd.RoslynMcp || dotnet tool install -g Darylmcd.RoslynMcp
If the user is developing in this repository and has just: run just tool-update (updates or installs, then lists global tools). To install the locally built package after just pack, use just tool-install-local (Windows ends roslynmcp.exe first to avoid file locks).
Report the result. If the tool reports "already up to date", note that and continue to Layer 2.
Tell the user to run these two commands in the Claude Code chat input (they are slash commands handled by the Claude Code client, not by the agent):
/plugin marketplace update roslyn-mcp-marketplace
/plugin install roslyn-mcp@roslyn-mcp-marketplace
Note: If the user's Claude Code client does not support /plugin slash commands (i.e., they get /plugin isn't available in this environment), tell them to update via their client's plugin/marketplace UI, or to uninstall and reinstall the plugin from the marketplace. Maintainers with the Roslyn-Backed-MCP source tree checked out have an agent-executable PowerShell fallback — see the repo-local override in .claude/skills/update/ if present.
Display a summary:
tools
Consumer-facing audit of the Roslyn MCP server's live surface against a loaded C# repo. Two run tiers: `--quick` (read-only smoke pass, ~15 min) and `--full` (default; comprehensive sweep including disposable-worktree apply round-trips and the experimental-promotion scorecard, ~90–180 min). Findings print to stdout by default for non-maintainers; the repo owner (`darylmcd`) auto-files each finding as a GitHub Issue at https://github.com/darylmcd/Roslyn-Backed-MCP. Pass `--auto-file` to force-enable or `--no-auto-file` to force-disable. Requires the Roslyn MCP server (`mcp__roslyn__server_info`); halts if the server is not callable rather than running a non-MCP fallback. Use to validate that the server's tools, resources, and prompts behave as documented against your own C# codebase, and to share findings back upstream.
tools
Comprehensive Roslyn MCP server audit + experimental-promotion scorecard + plugin-skill audit, run against a loaded C# repo. Three modes — `full`, `promotion-only`, `read-only`. Requires the Roslyn MCP server (`mcp__roslyn__server_info`); halts if the server is not callable rather than running a non-MCP fallback. Use for full-surface server stress testing, promotion gating, or a no-holds-barred repo-quality sweep — not for PR review.
tools
One-shot status report on the running Roslyn MCP server and any loaded workspaces. Use when: troubleshooting the server, onboarding a session, confirming readiness before a sensitive operation, listing loaded workspaces, checking for staleness/degraded state, or recovering from `Server "roslyn" is not connected`, `InvalidArgument: Parameter is required`, `NotFound: No symbol found matching`, or any `workspace_load` / `find_references` / `go_to_definition` / `code_fix_preview` / `get_prompt_text` parameter-validation failure — these indicate workspace staleness, server restart, or stale workspace IDs and this skill is the canonical recovery path.
development
Multi-project version bump across a .NET solution. Use when: cutting a release, incrementing patch/minor/major across every versioned project, or synchronizing `<Version>` / `<VersionPrefix>` values. Takes a bump type (patch, minor, or major) as input. Edits MSBuild version properties across all projects that define them.