playwright-dev

Define a structured process for adding Playwright APIs, MCP tools, CLI commands, and vendor dependencies.

6|1|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/guillempuche/batuda --skill playwright-dev-guillempuche
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright-dev
Source: https://github.com/guillempuche/batuda/tree/main/docs/repos/playwright/.claude/skills/playwright-dev
Command: npx skills add https://github.com/guillempuche/batuda --skill playwright-dev-guillempuche

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured blueprint for contributors to expand Playwright by adding APIs, MCP tools, CLI commands, and vendor dependencies. It clarifies the development workflow and documentation expectations to streamline community contributions.

Core Features & Use Cases

  • Step-by-step guidance for implementing client APIs, server dispatchers, MCP tooling, and CLI commands within the Playwright ecosystem.
  • Instructions for integrating vendor dependencies and updating references documentation to support new capabilities.
  • Real-world scenario: a maintainer adds a new API surface and a CLI tool to automate onboarding workflows or internal tooling, with associated vendor packages.

Quick Start

Identify the SKILL.md frontmatter name and description, then locate or create optional directories (scripts/, references/, assets/) to load operational details during activation.

Frequently Asked Questions about playwright-dev

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

FAQPage Schema
How do I add new APIs and MCP tools to Playwright?

To add new Playwright APIs and MCP tools, define a structured process within a Skill unit that specifies client APIs, server dispatchers, and CLI commands, utilizing a SKILL.md file to declare the name and description.

What is the process for integrating vendor dependencies into Playwright?

Integrating vendor dependencies into Playwright involves following a structured blueprint within the Skill unit, adding the necessary packages, and updating the references documentation to support the new capabilities.

How do I structure a Playwright contribution for tooling and CLI commands?

Structuring a Playwright contribution requires creating a SKILL.md file with frontmatter declaring name and description, then organizing operational details into optional scripts/, references/, and assets/ directories for activation.

Can I use this Skill to extend the Playwright server and client layers?

Yes, this Skill is applicable to core library maintainers and contributors who extend the Playwright platform across client, server, and tooling layers, providing step-by-step guidance for each layer.

What documentation references do I need to update when adding Playwright CLI commands?

When adding Playwright CLI commands, you must update the references documentation to support new capabilities, ensuring the structured blueprint clarifies development workflow and documentation expectations for community contributions.