/SKILL.md
# Visual Studio Debugger Skill When debugging code in Visual Studio, use the vs-debugger MCP tools to control the debugger directly. This works for any language VS can debug (C#, C++, Python, TypeScript, etc.). ## Available Tools - `vs_status` - Check VS state (design/running/break mode), solution name, breakpoints - `vs_set_breakpoint` - Set a breakpoint at file:line, with optional condition - `vs_remove_breakpoint` - Remove a breakpoint at file:line - `vs_launch` - Start debugging (F5) or r
npx skillsauth add isaacsimms/vsdebugclaudemcpandskill vsdebugclaudemcpandskillInstall 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.
When debugging code in Visual Studio, use the vs-debugger MCP tools to control the debugger directly. This works for any language VS can debug (C#, C++, Python, TypeScript, etc.).
vs_status - Check VS state (design/running/break mode), solution name, breakpointsvs_set_breakpoint - Set a breakpoint at file:line, with optional conditionvs_remove_breakpoint - Remove a breakpoint at file:linevs_launch - Start debugging (F5) or resume from breakvs_stop - Stop debugging (Shift+F5)vs_get_locals - Read local variables (break mode only)vs_evaluate - Evaluate any C# expression (break mode only)vs_step_over - Step over current line (F10)vs_step_into - Step into method call (F11)vs_step_out - Step out of current method (Shift+F11)vs_get_callstack - View the call stack (break mode only)vs_status first to confirm VS is running and see the current statevs_set_breakpointvs_launchvs_get_locals and vs_evaluatevs_get_callstack to understand how execution reached the current pointvs_step_over, vs_step_into, or vs_step_outvs_stop when donevs_status before other commands to know the current statevs_evaluate to test fix hypotheses without modifying code (e.g. myList.Count, customer?.Name)tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
tools
A CLI tool for making authenticated requests to the X (Twitter) API. Use this skill when you need to post tweets, reply, quote, search, read posts, manage followers, send DMs, upload media, or interact with any X API v2 endpoint.