browserstack
alirezarezvani/claude-skills
Run Playwright tests on BrowserStack's cloud grid for cross-browser and cross-device testing.
What is browserstack?
This skill integrates Playwright with BrowserStack to execute tests across multiple browsers and operating systems in the cloud. Use it when you need to verify application behavior on Safari, Firefox, Chrome, and WebKit across Windows, macOS, and other platforms without maintaining local test environments.
- Configure Playwright to connect to BrowserStack's cloud grid with browser/OS combinations
- Run tests across Chrome, Firefox, and WebKit on Windows and macOS simultaneously
- Retrieve build results, session details, videos, and logs from BrowserStack
- List available browsers and OS versions compatible with Playwright
- Set up local tunneling for testing localhost or staging environments behind firewalls
How to install browserstack
npx skills add https://github.com/alirezarezvani/claude-skills --skill browserstack- BrowserStack account with valid username and access key
- Environment variables BROWSERSTACK_USERNAME and BROWSERSTACK_ACCESS_KEY set
- Playwright project with test files already configured
- Manual setup of BrowserStack MCP server (pw-browserstack) in your MCP config; setting env vars alone is insufficient
How to use browserstack
- 1.Set BROWSERSTACK_USERNAME and BROWSERSTACK_ACCESS_KEY environment variables from your BrowserStack account settings
- 2.Run `/pw:browserstack setup` to add BrowserStack connect options to your playwright.config.ts with Chrome, Firefox, and WebKit projects
- 3.Run `/pw:browserstack run` to execute tests on the BrowserStack cloud grid across all configured browsers
- 4.Run `/pw:browserstack results` to fetch and display build results, session status, video links, and logs per browser
- 5.Optionally run `/pw:browserstack browsers` to list available browser/OS combinations or `/pw:browserstack local` to set up local tunneling
Use cases
- Verify web application compatibility across Safari on macOS, Firefox on Windows, and Chrome on multiple OS versions before release
- Run automated E2E tests on a browser matrix in CI/CD without maintaining physical devices
- Debug browser-specific failures by accessing BrowserStack session videos and network logs
- Test internal staging environments through BrowserStack Local tunneling without exposing them publicly
- Validate responsive design and feature parity across Chromium, Firefox, and WebKit engines
- QA engineers running cross-browser test suites
- Frontend developers verifying compatibility before deployment
- CI/CD pipeline maintainers automating browser matrix testing
- Teams without access to physical device labs
browserstack FAQ
The skill will inform you how to retrieve your BrowserStack username and access key from browserstack.com/accounts/settings and will not proceed until they are configured.
The BrowserStack MCP server (pw-browserstack) is not auto-registered. You must manually install it by running `cd integrations/browserstack-mcp && npm install` and registering it in your user or project MCP config.
Yes, use `/pw:browserstack local` to set up BrowserStack Local tunneling, which creates a secure connection to your internal environment.
Run `/pw:browserstack browsers` to list all Playwright-compatible options. The skill includes Chrome, Firefox, and WebKit on Windows 11 and macOS Ventura by default.
Run `/pw:browserstack results` to retrieve session details including video URLs and log links from the BrowserStack dashboard for each browser.
Full instructions (SKILL.md)
Source of truth, from alirezarezvani/claude-skills.
name: "browserstack" description: >- Run tests on BrowserStack. Use when user mentions "browserstack", "cross-browser", "cloud testing", "browser matrix", "test on safari", "test on firefox", or "browser compatibility".
BrowserStack Integration
Run Playwright tests on BrowserStack's cloud grid for cross-browser and cross-device testing.
Prerequisites
Environment variables must be set:
BROWSERSTACK_USERNAME— your BrowserStack usernameBROWSERSTACK_ACCESS_KEY— your access key
If not set, inform the user how to get them from browserstack.com/accounts/settings and stop.
The BrowserStack MCP server is not auto-registered (issue #978).
pw-browserstackwas removed from the plugin's.mcp.jsonbecause it failed to connect for every user (the plugin ships nonode_modules). Thebrowserstack_*MCP tools used below, and the/pw:browserstackcommand, will fail with "tool not found" until it is enabled manually — see the Integrations section of the plugin'sCLAUDE.md(cd integrations/browserstack-mcp && npm install, then register the server in your own user/project MCP config). Setting the env vars alone is not sufficient.
Capabilities
1. Configure for BrowserStack
/pw:browserstack setup
Steps:
- Check current
playwright.config.ts - Add BrowserStack connect options:
// Add to playwright.config.ts
import { defineConfig } from '@playwright/test';
const isBS = !!process.env.BROWSERSTACK_USERNAME;
export default defineConfig({
// ... existing config
projects: isBS ? [
{
name: "chromelatestwindows-11",
use: {
connectOptions: {
wsEndpoint: `wss://cdp.browserstack.com/playwright?caps=${encodeURIComponent(JSON.stringify({
'browser': 'chrome',
'browser_version': 'latest',
'os': 'Windows',
'os_version': '11',
'browserstack.username': process.env.BROWSERSTACK_USERNAME,
'browserstack.accessKey': process.env.BROWSERSTACK_ACCESS_KEY,
}))}`,
},
},
},
{
name: "firefoxlatestwindows-11",
use: {
connectOptions: {
wsEndpoint: `wss://cdp.browserstack.com/playwright?caps=${encodeURIComponent(JSON.stringify({
'browser': 'playwright-firefox',
'browser_version': 'latest',
'os': 'Windows',
'os_version': '11',
'browserstack.username': process.env.BROWSERSTACK_USERNAME,
'browserstack.accessKey': process.env.BROWSERSTACK_ACCESS_KEY,
}))}`,
},
},
},
{
name: "webkitlatestos-x-ventura",
use: {
connectOptions: {
wsEndpoint: `wss://cdp.browserstack.com/playwright?caps=${encodeURIComponent(JSON.stringify({
'browser': 'playwright-webkit',
'browser_version': 'latest',
'os': 'OS X',
'os_version': 'Ventura',
'browserstack.username': process.env.BROWSERSTACK_USERNAME,
'browserstack.accessKey': process.env.BROWSERSTACK_ACCESS_KEY,
}))}`,
},
},
},
] : [
// ... local projects fallback
],
});
- Add npm script:
"test:e2e:cloud": "npx playwright test --project='chrome@*' --project='firefox@*' --project='webkit@*'"
2. Run Tests on BrowserStack
/pw:browserstack run
Steps:
- Verify credentials are set
- Run tests with BrowserStack projects:
BROWSERSTACK_USERNAME=$BROWSERSTACK_USERNAME \ BROWSERSTACK_ACCESS_KEY=$BROWSERSTACK_ACCESS_KEY \ npx playwright test --project='chrome@*' --project='firefox@*' - Monitor execution
- Report results per browser
3. Get Build Results
/pw:browserstack results
Steps:
- Call
browserstack_get_buildsMCP tool - Get latest build's sessions
- For each session:
- Status (pass/fail)
- Browser and OS
- Duration
- Video URL
- Log URLs
- Format as summary table
4. Check Available Browsers
/pw:browserstack browsers
Steps:
- Call
browserstack_get_browsersMCP tool - Filter for Playwright-compatible browsers
- Display available browser/OS combinations
5. Local Testing
/pw:browserstack local
For testing localhost or staging behind firewall:
- Install BrowserStack Local:
npm install -D browserstack-local - Add local tunnel to config
- Provide setup instructions
MCP Tools Used
| Tool | When |
|---|---|
browserstack_get_plan | Check account limits |
browserstack_get_browsers | List available browsers |
browserstack_get_builds | List recent builds |
browserstack_get_sessions | Get sessions in a build |
browserstack_get_session | Get session details (video, logs) |
browserstack_update_session | Mark pass/fail |
browserstack_get_logs | Get text/network logs |
Output
- Cross-browser test results table
- Per-browser pass/fail status
- Links to BrowserStack dashboard for video/screenshots
- Any browser-specific failures highlighted
Related skills
More from alirezarezvani/claude-skills and the wider catalog.

business-growth-skills
Router for 4 business & growth skills: customer success, sales engineering, revenue ops, and contracts.

c-level-advisor
Virtual board of directors for founders: 10 C-level roles with structured decision support and multi-role board meetings.

campaign-analytics
Analyzes campaign performance with multi-touch attribution, funnel conversion analysis, and ROI calculation for marketing optimization. Use when analyzing marketing campaigns, ad performance, attribution models, conversion rates, or calculating marketing ROI, ROAS, CPA, and campaign metrics across channels.

capa-officer
CAPA system management for medical device QMS. Covers root cause analysis, corrective action planning, effectiveness verification, and CAPA metrics. Use when running CAPA investigations, 5-Why analysis, fishbone diagrams, root cause determination, corrective action tracking, effectiveness verification, or CAPA program optimization.

ceo-advisor
Executive leadership guidance for strategic decision-making, organizational development, and stakeholder management. Use when planning strategy, preparing board presentations, managing investors, developing organizational culture, making executive decisions, fundraising, or when user mentions CEO, strategic planning, board meetings, investor updates, organizational leadership, or executive strategy.

cfo-advisor
Financial leadership for startups and scaling companies. Financial modeling, unit economics, fundraising strategy, cash management, and board financial packages. Use when building financial models, analyzing unit economics, planning fundraising, managing cash runway, preparing board materials, or when user mentions CFO, burn rate, runway, fundraising, unit economics, LTV, CAC, term sheets, or financial strategy.