Use this skill when the user wants to search the web without a full browser session: find URLs, titles, and metadata for a query. Prefer it over a browser when you just need search results, not page content. Returns structured results with titles, URLs, authors, and dates.
npx skills add https://github.com/browserbase/skills --skill search
Search the web and return structured results — no browser session required.
Get your API key from: https://browserbase.com/settings
export BROWSERBASE_API_KEY="your_api_key"
| Use Case | Search API | Browser Skill |
|----------|-----------|---------------|
| Find URLs for a topic | Yes | Overkill |
| Get page titles and metadata | Yes | Overkill |
| Read full page content | No | Yes |
| JavaScript-rendered pages | No | Yes |
| Form interactions | No | Yes |
| Speed | Fast | Slower |
Rule of thumb: Use Search to find relevant URLs and metadata. Use the Browser skill when you need to visit and interact with the pages. Use Fetch to retrieve page content without JavaScript rendering.
curl -X POST "https://api.browserbase.com/v1/search" \
-H "Content-Type: application/json" \
-H "X-BB-API-Key: $BROWSERBASE_API_KEY" \
-d '{"query": "browserbase web automation"}'
| Field | Type | Default | Description |
|-------|------|---------|-------------|
| query | string | *required* | The search query |
| numResults | integer (1-25) | 10 | Number of results to return |
Returns JSON with:
| Field | Type | Description |
|-------|------|-------------|
| requestId | string | Unique identifier for the search request |
| query | string | The search query that was executed |
| results | array | List of search result objects |
Each result object contains:
| Field | Type | Description |
|-------|------|-------------|
| id | string | Unique identifier for the result |
| url | string | URL of the result |
| title | string | Title of the result |
| author | string? | Author of the content (if available) |
| publishedDate | string? | Publication date (if available) |
| image | string? | Image URL (if available) |
| favicon | string? | Favicon URL (if available) |
> Note: The @browserbasehq/sdk does not have a search method yet. Use cURL or direct HTTP calls.
curl -X POST "https://api.browserbase.com/v1/search" \
-H "Content-Type: application/json" \
-H "X-BB-API-Key: $BROWSERBASE_API_KEY" \
-d '{"query": "web scraping best practices", "numResults": 5}'
| Status | Meaning |
|--------|---------|
| 400 | Invalid request body (check query and parameters) |
| 403 | Invalid or missing API key |
| 429 | Rate limit exceeded (retry later) |
| 500 | Internal server error (retry later) |
numResults when you only need a few top resultsFor detailed examples, see EXAMPLES.md.
For API reference, see REFERENCE.md.
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Replace with description of the skill and when Claude should use it.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Take browserbase/search from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.