SKILL.md
$2a
- Use
filePathparameter for large outputs (screenshots, snapshots, traces)
- Use pagination (
pageIdx,pageSize) and filtering (types) to minimize data
- Set
includeSnapshot: falseon input actions unless you need updated page state
Tool selection
- Automation/interaction:
take_snapshot(text-based, faster, better for automation)
- Visual inspection:
take_screenshot(when user needs to see visual state)
- Additional details:
evaluate_scriptfor data not in accessibility tree
Parallel execution
You can send multiple tool calls in parallel, but maintain correct order: navigate → wait → snapshot → interact.
Testing an extension
- Install: Use
install_extensionwith the path to the unpacked extension.
- Identify: Get the extension ID from the response or by calling
list_extensions.
- Trigger Action: Use
trigger_extension_actionto open the popup or side panel if applicable.
- Verify Service Worker: Use
evaluate_scriptwithserviceWorkerIdto check extension state or trigger background actions.
- Verify Page Behavior: Navigate to a page where the extension operates and use
take_snapshotto check if content scripts injected elements or modified the page correctly.
Troubleshooting
If chrome-devtools-mcp is insufficient, guide users to use Chrome DevTools UI:
If there are errors launching chrome-devtools-mcp or Chrome, refer to https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/main/docs/troubleshooting.md.