web-routing

Route browser requests to browser or webapp-testing skills by keywords.

5|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/lidge-jun/cli-jaw-skills --skill web-routing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web-routing
Source: https://github.com/lidge-jun/cli-jaw-skills/tree/main/web-routing
Command: npx skills add https://github.com/lidge-jun/cli-jaw-skills --skill web-routing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill simplifies the process of directing browser-related requests to the appropriate tool, ensuring that general web tasks are handled by one system and specific web application testing by another.

Core Features & Use Cases

  • Intelligent Request Routing: Automatically determines whether a request pertains to general web browsing or web application testing.
  • Keyword-Based Decision Making: Uses specific keywords like 'e2e', 'regression', or 'test' to classify requests.
  • Use Case: When you ask the AI to "browse to example.com and log in," it routes to browser. If you ask it to "run e2e tests on my local web app," it routes to webapp-testing.

Quick Start

Use the web-routing skill to determine the correct tool for browsing example.com.

Frequently Asked Questions about web-routing

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

FAQPage Schema
How does web request routing work for automated browser tasks?

Web request routing evaluates predefined keywords like 'e2e' or 'test' to direct browser tasks, sending general web navigation to a browser skill and testing requests to a webapp-testing skill.

When do I need automated routing for web application testing?

You need automated routing for web application testing when managing both general web browsing and dedicated end-to-end regression analysis, ensuring specific testing requests are separated from standard navigation.

How do I route Playwright requests to the correct browser tool?

To route Playwright requests, the system maps them to a general browser skill by default, unless testing is explicitly mentioned in the request, which then redirects them to a webapp-testing skill.

Can I use keyword-based decision making to separate web browsing from e2e tests?

Yes, you can use keyword-based decision making to separate tasks by identifying specific terms like 'e2e', 'regression', or 'test' to route requests to webapp-testing instead of general browser handling.

What distinguishes general web navigation routing from local web app regression routing?

General web navigation routing handles browsing and form input, while local web app regression routing specifically targets end-to-end testing and regression analysis based on predefined testing keywords in the request.