mcpbeat

Generate Run Commands

microsoft/generate-run-commands

Generate or modify run commands for the current session. Use when the user wants to set up or update run commands that appear in the session's Run button.

595 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
188278
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/microsoft/vscode --skill generate-run-commands

The instruction itself

4 sections, as written by the author

<!-- Customize this skill and select save to override its behavior. Delete that copy to restore the built-in behavior. -->

Generate Run Commands

Help the user set up run commands for the current Agent Session workspace. Run commands appear in the session's Run button in the title bar.

Understanding the task schema

A run command is a tasks.json task with:

  • "inAgents": true — required: makes the task appear in the Agents run button
  • "runOptions": { "runOn": "worktreeCreated" } — optional: auto-runs the task whenever a new worktree is created (use for setup/install commands)
{
  "tasks": [
    {
      "label": "Install dependencies",
      "type": "shell",
      "command": "npm install",
      "inAgents": true,
      "runOptions": { "runOn": "worktreeCreated" }
    },
    {
      "label": "Start dev server",
      "type": "shell",
      "command": "npm run dev",
      "inAgents": true
    }
  ]
}

Decision logic

First, read the existing .vscode/tasks.json to check for existing run commands (inAgents: true tasks).

If run commands already exist: treat this as a modify request — ask the user what they'd like to change (add, remove, or update a command).

If no run commands exist: try to infer the right commands from the workspace:

  • Check package.json, Makefile, pyproject.toml, Cargo.toml, go.mod, .nvmrc, or other project files to understand the stack and common commands.
  • If it's clear what the setup command is (e.g., npm install, pip install -r requirements.txt), add it with "runOptions": { "runOn": "worktreeCreated" } — no need to ask.
  • If it's clear what the primary run/dev command is (e.g., npm run dev, cargo run), add it with just "inAgents": true.
  • Only ask the user if the commands are ambiguous (e.g., multiple equally valid options, no recognizable project structure, or the project uses a non-standard setup).

Writing the file

Always write to .vscode/tasks.json in the workspace root. If the file already exists, merge — do not overwrite unrelated tasks.

After writing, briefly confirm what was added and how to trigger it from the Run button.

How to use it

Copy the folder

Take microsoft/generate-run-commands from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.

Install what it needs

The instructions reference pip, npm. Without those the skill loads but fails at the first command.