wave-ecosystem-guide

Select Python browser automation tools via CDP and BiDi decision frameworks.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/MathiasPaulenko/ai-toolkit --skill wave-ecosystem-guide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wave-ecosystem-guide
Source: https://github.com/MathiasPaulenko/ai-toolkit/tree/main/skills/wave-ecosystem-guide
Command: npx skills add https://github.com/MathiasPaulenko/ai-toolkit --skill wave-ecosystem-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This skill resolves the complexity of choosing the right browser automation tool by providing a unified architectural overview and decision framework for the Wave ecosystem, eliminating the need for heavy dependencies like Node.js or Selenium.

Core Features & Use Cases

  • Tool Selection: Provides a clear decision tree to choose between cdpwave, bidiwave, wavexis, and wavexis-mcp based on specific project requirements.
  • Architecture Guidance: Explains how to integrate low-level CDP/BiDi backends with high-level CLI and MCP server layers.
  • Migration Support: Offers structured paths for transitioning from legacy tools like Playwright, Selenium, or pyppeteer to the modern, Python-native Wave ecosystem.

Quick Start

Ask the AI to explain which Wave tool is best suited for your specific browser automation task by describing your requirements and preferred browser.

Frequently Asked Questions about wave-ecosystem-guide

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

FAQPage Schema
What is the best Python library for browser automation without Node.js or Selenium?

The Wave ecosystem provides Python-native browser automation using cdpwave and bidiwave, eliminating heavy Node.js or Selenium dependencies while supporting tasks from scraping to LLM agentic control.

How do I choose between CDP and WebDriver BiDi backends for web scraping?

Use the decision framework to map specific use cases to either CDP or BiDi backends, selecting the appropriate library or service layer like cdpwave, bidiwave, wavexis, or wavexis-mcp based on project requirements.

Can I migrate existing Playwright or pyppeteer scripts to Python-native browser automation?

Yes, the guide offers structured migration paths for transitioning from legacy tools like Playwright, Selenium, or pyppeteer to the modern Python-native Wave ecosystem.

How do I integrate an MCP server with low-level CDP for LLM-driven browser control?

The architecture guidance explains how to integrate low-level CDP and BiDi backends with high-level CLI and MCP server layers to achieve LLM-driven agentic browser control.

When should I use wavexis-mcp instead of cdpwave for scraping tasks?

Wavexis-mcp is suited for LLM-driven agentic browser control, while cdpwave handles CLI-based scraping; the decision tree maps your specific requirements to the correct tool.