browser-testing-with-devtools

Redirect deprecated browser-testing-with-devtools requests to browser-runtime-observation or chrome-devtools-mcp.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/Handy369/passto-pi-frame --skill browser-testing-with-devtools-handy369
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-testing-with-devtools
Source: https://github.com/Handy369/passto-pi-frame/tree/main/skills/browser-testing-with-devtools
Command: npx skills add https://github.com/Handy369/passto-pi-frame --skill browser-testing-with-devtools-handy369

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents outdated or explicitly named legacy requests for browser testing with DevTools from being treated as an independent, maintained entry point, and instead routes them to the correct modern skills.

Core Features & Use Cases

  • Compatibility shim: Explains that the skill name is deprecated and should not remain as a standalone main route.
  • Deterministic redirection: Directs browser runtime evidence work to browser-runtime-observation and routes low-level DevTools MCP requests to chrome-devtools-mcp.
  • Scope guardrails: Blocks further expansion into full testing or diagnosis flows within this deprecated shell.
  • Use Case: You have an old prompt or documentation snippet that mentions browser-testing-with-devtools; you want the AI to immediately continue with the unified canonical skill path.

Quick Start

Ask the AI to handle your request previously labeled as browser-testing-with-devtools and ensure it redirects you to browser-runtime-observation or chrome-devtools-mcp as appropriate.

Frequently Asked Questions about browser-testing-with-devtools

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate legacy DevTools testing prompts to a modern workflow?

To migrate legacy DevTools testing prompts, this compatibility shim intercepts deprecated requests and automatically redirects them to canonical skills like browser-runtime-observation or chrome-devtools-mcp.

Why does my old browser testing documentation reference a deprecated entry point?

Your browser testing documentation references a deprecated entry point because the workflow was consolidated, requiring an immediate compatibility redirect to unified canonical skills instead of executing standalone testing flows.

What is the best way to route low-level DevTools MCP requests correctly?

The best way to route low-level DevTools MCP requests is through this deterministic redirection layer, which evaluates your intent and directs you to chrome-devtools-mcp for low-level reference needs.

Can I run full browser testing diagnosis flows directly inside this legacy prompt shell?

You cannot run full browser testing diagnosis flows inside this legacy prompt shell, as scope guardrails block further expansion and immediately route execution to modern canonical paths.

When do I need a prompt deprecation compatibility shim for browser testing?

You need a prompt deprecation compatibility shim for browser testing when outdated documentation or prompts explicitly reference legacy skill names, requiring deterministic redirection to prevent duplicate workflow execution.