bright-data-best-practices 是做什麼的？
建構適合生產環境的 Bright Data 整合，內建最佳實務。供使用編碼助手（Claude Code、Cursor 等）的開發者參考，實作網頁爬取、搜尋、瀏覽器自動化與結構化資料提取。涵蓋 Web Unlocker API、SERP API、Web Scraper API 及 Browser API (Scraping Browser)。
建構適合生產環境的 Bright Data 整合，內建最佳實務。供使用編碼助手（Claude Code、Cursor 等）的開發者參考，實作網頁爬取、搜尋、瀏覽器自動化與結構化資料提取。涵蓋 Web Unlocker API、SERP API、Web Scraper API 及 Browser API (Scraping Browser)。
此技能為開發者提供完整的 Bright Data 整合指南，專為使用 AI 編碼助手（如 Claude Code、Cursor、Codex）的團隊設計。它涵蓋四大核心 API：Web Unlocker API（繞過反爬機制）、SERP API（搜尋引擎結果頁提取）、Web Scraper API（結構化資料爬取），以及 Browser API（自動化瀏覽器操作）。技能文件內建生產環境最佳實務，包含錯誤處理、速率限制、代理輪換等關鍵模式，確保整合的穩定性與可擴展性。開發者可直接在 IDE 中透過 AI 助手參考此文件，加速實作並降低整合風險。支援所有主流程式語言，並提供清晰的使用範例。
npx skills add https://github.com/brightdata/skills/tree/main/skills/bright-data-best-practicesInstalled? Explore more 研究與資料分析 skills: affaan-m/uspto-database, affaan-m/scholar-evaluation, affaan-m/literature-review · View all 6 →
建構適合生產環境的 Bright Data 整合，內建最佳實務。供使用編碼助手（Claude Code、Cursor 等）的開發者參考，實作網頁爬取、搜尋、瀏覽器自動化與結構化資料提取。涵蓋 Web Unlocker API、SERP API、Web Scraper API 及 Browser API (Scraping Browser)。
This repo contains 3 individual skills — each has its own dedicated page.
Guide for using the Bright Data CLI (`brightdata` / `bdata`) to scrape websites, search the web, extract structured data from 40+ platforms, manage proxy zones, and check account budget. Use this skill whenever the user wants to scrape a URL, search Google/Bing/Yandex, extract data from Amazon/LinkedIn/Instagram/TikTok/YouTube/Reddit or any other platform, check their Bright Data balance or zones, or do anything involving web data collection from the terminal. Also trigger when the user mentions brightdata, bdata, web scraping CLI, SERP API, or wants to install Bright Data skills into their coding agent.
Scrape web content as clean markdown/HTML/JSON via the Bright Data CLI (`bdata scrape`). Use when the user wants to fetch a page, extract content from a list of URLs, or crawl paginated listings. Hands off to `data-feeds` for supported platforms (Amazon, LinkedIn, TikTok, Instagram, YouTube, Reddit, etc.) and to `search` when URLs must be discovered first. Requires the Bright Data CLI; proactively guides install + login if missing.
When the user wants to audit, review, or diagnose SEO issues on their site. Uses live web data via the Bright Data CLI for accurate detection of JS-injected schema, hreflang, canonicals, and live SERP-based ranking checks. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For implementing structured data, see schema-markup. For AI search optimization, see ai-seo.
USPTO patent and trademark data workflow for official record lookup, PatentSearch queries, TSDR checks, assignment data, and reproducible IP research logs.
Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback.
Systematic literature-review workflow for academic, biomedical, technical, and scientific topics, including search planning, source screening, synthesis, citation checks, and evidence logging.
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Agent skill repository discovered by 10x-chat research.
Review backend code for quality, security, maintainability, and best practices based on established checklist rules. Use when the user requests a review, analysis, or improvement of backend files (e.g., `.py`) under the `api/` directory. Do NOT use for frontend files (e.g., `.tsx`, `.ts`, `.js`). Supports pending-change review, code snippets review, and file-focused review.