agent-onboarding
The entry point to all Bright Data skills - start here, and it guides the agent to the right skill for the task at hand - web data and scraping, fetching or unblocking a page, search, browser automation, and the CLI, SDK and MCP surfaces. Use when Bright Data is not set up or stops authenticating - the CLI is missing ("bdata is not recognized"), login is needed or fails ("No API key found"), there is no Bright Data account yet and one must be created without a browser, a call is refused with 401, 407 or another auth error, an expected zone like cli_unlocker is missing, a key must be set in a project's .env, CI, or a container (BRIGHTDATA_API_KEY), or the user asks to install Bright Data, log in, get started, or which skill fits their task. Auth for every other Bright Data skill lives here.
Install
With your agent
Install OMGSkills skill "brightdata/skills:agent-onboarding" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/brightdata/skills /tmp/skills && ln -s /tmp/skills/skills/agent-onboarding ~/.claude/skills/agent-onboardingFrom README
Bright Data - Start Here the CLI and the skills, log in once, then route to the task skill. Never ask the user to paste an API key into chat. Login is one browser approval. The key never touches the conversation. Already set up? Three free checks before doing any work: bdata --version works: skip to Add the skills. Pick the skill from the route table below (Route to the task skill), then run node /scripts/check-auth.mjs --for (scripts/check-auth.mjs). The path is relative to this skill's folder, not to the project: a "Cannot find module" error means a wrong path, never a login problem. One free call, and the exit code is the answer: 0 ready, go to that skill. 2 means log in. 3 means the key was never tested (network or server), so fix that instead of logging in. 1 means the key works but the account has no zone of the type that skill needs, which is one free call (in Log in below), never another login.
More from this repo
brd-browser-debug
Used to debug Bright Data Scraping Browser sessions using the Browser Sessions API.
bright-data-mcp
Bright Data MCP handles ALL web data operations.
brightdata-proxy
Used to generate working code that routes HTTP requests through Bright Data proxy networks (Datacenter, ISP,...