What problem does it solve? The tik4net.mcp MCP server is a compiled binary that never picks up source changes on its own, so edits to Tools/tik4net.mcp/ or the tik4net library silently fail to appear in the MCP tools. This Skill diagnoses and fixes stale servers, locked-file build failures, and broken installs. ## Core Features & Use Cases - Dev launcher refresh: Rebuilds the solution and explains the staged-copy launcher in .mcp.json, including how to verify the running build via the timestamp stamp in every tool response. - Global tool installation: Runs install-tool.ps1 to stop running servers, pack Release, purge the stale NuGet cache, uninstall, reinstall, and verify the binary starts. - Troubleshooting: Resolves locked binaries under Tools/tik4net.mcp/bin or .dotnet\tools, no-op dotnet tool update at unchanged versions, and missing tools after install. - Use Case: You changed the tik4net library but mikrotik_call still behaves the old way — use this Skill to rebuild, reconnect the server, and confirm the new build stamp. ## Quick Start Rebuild and reconnect the tik4net-mcp MCP server so my recent changes to the tik4net library show up in the MCP tools.