browser-skill-creator

Create site-specific browser-automation skills using Playwright MCP and SKILL.md templates.

12|2|Updated Feb 2, 2020

Search Tags:#workflow #template #qa #playwright #browser-automation #selectors #skill-generation

Ready to run

npx skills add https://github.com/servitola/dotfiles --skill browser-skill-creator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: browser-skill-creator
Source: https://github.com/servitola/dotfiles/tree/main/claude-code/skills/browser-skill-creator
Command: npx skills add https://github.com/servitola/dotfiles --skill browser-skill-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Generates a repeatable process for creating site-specific browser-automation skills driven by Playwright MCP, with persistent profiles and a proven SKILL.md template, stopping one step before final confirmation so the user completes irreversible actions themselves.

Core Features & Use Cases

Phase-driven workflow: Discovery interview, Site recon, Draft skills, QA, and Validate the final skill.
Outputs a ready-to-run SKILL.md with frontmatter, flows, selectors, and safety gates; stores the persistent profile at ~/.claude-playwright-profiles/<name>.
Uses the references/skill-template.md and references/selector-strategy.md as guidance to ensure maintainability and robust selectors.

Quick Start

Run the browser-skill-creator to initiate Phase 1 discovery and begin building a new site-specific browser skill.

Frequently Asked Questions about browser-skill-creator

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

FAQPage Schema

How do I generate site-specific browser automation skills with Playwright?▼

You can generate site-specific browser automation skills by running a phase-driven workflow that covers discovery, site reconnaissance, draft skill creation, QA, and validation. This produces a ready-to-run SKILL.md with selectors and safety gates using Playwright MCP.

What is the workflow for creating a Playwright browser automation skill?▼

The browser automation skill creation workflow follows deterministic phases: discovery interview, site reconnaissance, draft skill creation, QA testing, and formal validation. It applies a proven SKILL.md template and selector strategy guidelines to ensure maintainable outputs.

Does browser automation skill generation support safety gates for irreversible actions?▼

Yes, browser automation skill generation implements safety gates by stopping one step before final confirmation. This ensures users complete irreversible actions themselves, preventing automated processes from executing destructive website operations.

Can I use persistent profiles for Playwright MCP site automation?▼

Yes, you can use persistent profiles for Playwright MCP site automation. Generated skills store persistent profiles at ~/.claude-playwright-profiles/<name>, maintaining session data and authentication states across multiple automation runs.

How do I maintain robust selectors in generated browser automation skills?▼

Robust selectors in generated browser automation skills are maintained using the references/selector-strategy.md guidance. This ensures selector maintainability and robustness across complex site automation tasks, including multi-language UIs.

What are the limitations of automating complex sites with Playwright MCP?▼

A key limitation of automating complex sites with Playwright MCP is that the workflow stops one step before final confirmation of irreversible actions, requiring manual user completion. Complex automation also requires full discovery, QA, and validation phases.