browserbase
You are an expert in BrowserBase, the cloud platform for running headless browsers at scale. You help developers deploy browser-based automations, AI agents, and web scraping pipelines using managed Chromium instances with residential proxies, session recording, stealth mode, and parallel execution — without managing browser infrastructure.
What this skill does
# BrowserBase — Cloud Browser Infrastructure for AI Agents
You are an expert in BrowserBase, the cloud platform for running headless browsers at scale. You help developers deploy browser-based automations, AI agents, and web scraping pipelines using managed Chromium instances with residential proxies, session recording, stealth mode, and parallel execution — without managing browser infrastructure.
## Core Capabilities
### Session Management
```typescript
import Browserbase from "@browserbasehq/sdk";
import { chromium } from "playwright-core";
const bb = new Browserbase({ apiKey: process.env.BROWSERBASE_API_KEY! });
// Create a browser session
const session = await bb.sessions.create({
projectId: process.env.BROWSERBASE_PROJECT_ID!,
browserSettings: {
fingerprint: {
locales: ["en-US"],
screen: { maxWidth: 1920, maxHeight: 1080 },
},
viewport: { width: 1280, height: 720 },
},
proxies: true, // Residential proxy (avoid blocks)
keepAlive: true, // Keep session alive between connections
timeout: 300, // Max session duration (seconds)
});
// Connect with Playwright
const browser = await chromium.connectOverCDP(session.connectUrl);
const context = browser.contexts()[0];
const page = context.pages()[0];
await page.goto("https://example.com");
// ... automation logic ...
// Session recording available at:
console.log(`Recording: https://browserbase.com/sessions/${session.id}`);
```
### Parallel Execution
```typescript
// Process 50 URLs concurrently with cloud browsers
async function scrapeInParallel(urls: string[], concurrency = 10) {
const results: any[] = [];
// Process in batches
for (let i = 0; i < urls.length; i += concurrency) {
const batch = urls.slice(i, i + concurrency);
const batchResults = await Promise.allSettled(
batch.map(async (url) => {
const session = await bb.sessions.create({
projectId: process.env.BROWSERBASE_PROJECT_ID!,
proxies: true,
keepAlive: false, // Auto-cleanup
});
const browser = await chromium.connectOverCDP(session.connectUrl);
const page = browser.contexts()[0].pages()[0];
try {
await page.goto(url, { waitUntil: "networkidle" });
const data = await page.evaluate(() => {
// Extract data from page
return { title: document.title, text: document.body.innerText.substring(0, 5000) };
});
return { url, ...data };
} finally {
await browser.close();
}
})
);
results.push(...batchResults);
}
return results;
}
```
### Persistent Context (Login Sessions)
```typescript
// Create a context that persists cookies/auth across sessions
const context = await bb.contexts.create({
projectId: process.env.BROWSERBASE_PROJECT_ID!,
});
// First session: log in and save context
const loginSession = await bb.sessions.create({
projectId: process.env.BROWSERBASE_PROJECT_ID!,
browserSettings: { context: { id: context.id, persist: true } },
});
// ... log in via Playwright ...
// Later sessions reuse the authenticated context
const workSession = await bb.sessions.create({
projectId: process.env.BROWSERBASE_PROJECT_ID!,
browserSettings: { context: { id: context.id, persist: true } },
});
// Already logged in — cookies persisted
```
## Installation
```bash
npm install @browserbasehq/sdk playwright-core
# Get API key: https://browserbase.com
```
## Best Practices
1. **Proxies for scraping** — Enable `proxies: true` for sites that block datacenter IPs; BrowserBase provides residential proxies
2. **Session recordings** — Every session is recorded; use recordings to debug failed automations without re-running
3. **Persistent contexts** — Use contexts to share login state across sessions; avoid re-authenticating every time
4. **keepAlive for multi-step** — Set `keepAlive: true` for long workflows; `false` for one-shot scraping
5. **Stealth by default** — BrowserBase configures fingerprints and headers to look like a real browser; no extra stealth plugins needed
6. **Concurrency limits** — Respect your plan's concurrent session limit; use batching with `Promise.allSettled` for parallel work
7. **Combine with Stagehand** — Use BrowserBase as the browser backend for Stagehand AI automation; set `env: "BROWSERBASE"`
8. **Timeouts** — Set session `timeout` to prevent zombie sessions; sessions auto-terminate when the timeout expires
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.