菜单
Use when the user wants to run JavaScript in the browser, run code in Node, or batch multiple MCP tool calls. Run script, execute code, batch tools.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | execute-workflows |
| description | Use when the user wants to run JavaScript in the browser, run code in Node, or batch multiple MCP tool calls. Run script, execute code, batch tools. |
Use this skill when the user asks to run JavaScript, execute code in the page or on the server, or batch several tool calls into one.
There are no separate run-JS tools. Always use the MCP tool execute.
Use execute with page.evaluate():
// execute tool, code:
return await page.evaluate(() => document.title);
You have access to page (Playwright Page) and callTool(name, input, returnOutput?) inside the execute VM. Use await with callTool.
Use execute without page.evaluate() — e.g. Buffer, crypto, or multiple callTool calls:
return Buffer.from('hello').toString('base64');
Use execute and call tools via await callTool(name, input, returnOutput?):
await callTool('interaction_fill', { selector: 'e3', value: 'user@test.com' });
await callTool('interaction_click', { selector: 'e7', waitForNavigation: true });
const snapshot = await callTool('a11y_take-aria-snapshot', {}, true);
return snapshot;
Max 50 callTool calls per execution. Pass true as third argument to include that tool’s output in the response toolOutputs.
On Node platform, execute has no page; use callTool only. See commands/node/execute.md.
page, callTool, VM APIcallTool onlyAutomated browser testing and debugging using Browser DevTools MCP. Use when testing web pages, debugging frontend issues, verifying UI behavior, or automating browser interactions.
Debug Node.js backend processes using non-blocking tracepoints, logpoints, exceptionpoints, and JavaScript execution. Use when debugging API servers, workers, or backend scripts.
Debug web applications by inspecting console logs, network requests, JavaScript errors, and using non-blocking tracepoints/logpoints. Use when debugging web pages, inspecting API calls, or tracing code execution.
Monitor and debug web applications using OpenTelemetry, console logs, network requests, and distributed tracing. Use when correlating frontend and backend requests or debugging request flow across services.
Analyze web page performance using Web Vitals and network timing metrics. Use when optimizing load times, checking Core Web Vitals, or investigating slow pages.
Perform visual testing and UI verification using screenshots and DOM inspection. Use when verifying UI appearance, comparing with designs, or checking for visual regressions.