Agent skill

Brightdata Install Auth

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Bootstrap Bright Data access without mixing proxy-zone credentials and REST API keys.

MITAuto-check passedBackend & APIs

Install Brightdata Install Auth

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill brightdata-install-auth -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace brightdata-install-auth --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/brightdata-install-auth .claude/skills/brightdata-install-auth && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
brightdata-install-auth
GitHub stars
2.8k
Token cost
~960 tokens
SKILL.md length
372 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Bootstrap Bright Data access without mixing proxy-zone credentials and REST API keys.

  • Works in 4 steps: Inventory the access path → Define the secret contract → Bind ownership → …
  • Onboarding an integration
  • SKILL.md covers Overview, Prerequisites, Instructions and Tool Discipline, plus 4 more sections
  • Needs BRIGHTDATA_API_KEY and BRIGHTDATA_PROXY_PASSWORD

What it does

Brightdata Install Auth is an agent skill from jeremylongshore/tons-of-skills-marketplace. Bootstrap Bright Data access without mixing proxy-zone credentials and REST API keys. Use when onboarding an integration, changing credential ownership, or proving least-privilege access. Trigger with: "set up Bright Data access", "configure a Bright Data zone", "separate proxy and API credentials".

Its SKILL.md is about 960 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/official-docs.md`). Compatibility notes: Requires an approved Bright Data account or offline fixtures, current Bright Data documentation, and an authorized public-data collection purpose

It sits in Backend & APIs, covering REST APIs. It works with Bright Data. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Onboarding an integration
  • Changing credential ownership
  • Proving least-privilege access
  • With: set up Bright Data access

Example prompts

  • “set up Bright Data access”
  • “configure a Bright Data zone”
  • “separate proxy and API credentials”
  • “/brightdata-install-auth”

Requirements

  • A credential in BRIGHTDATA_API_KEY
  • Compatibility (from SKILL.md): Requires an approved Bright Data account or offline fixtures, current Bright Data documentation, and an authorized public-data collection purpose
  • Pre-approved tools (allowed-tools): Read, Grep, Write, Edit, Bash(python:*)

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Inventory the access path
  2. Define the secret contract
  3. Bind ownership
  4. Validate without disclosure

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Grep
    • Write
    • Edit
    • Bash(python:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are dotenv).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • docs.brightdata.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • BRIGHTDATA_API_KEY
    • BRIGHTDATA_PROXY_PASSWORD

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires an approved Bright Data account or offline fixtures, current Bright Data documentation, and an authorized public-data collection purpose

    From compatibility in the SKILL.md frontmatter.

Context cost

Brightdata Install Auth loads about 960 tokens when it runs, and up to ~1.1k if it reads all its reference files. Until then it costs about 81 tokens; SKILL.md has 372 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~81
When it runs · the whole SKILL.md, loaded when a task matches
~960
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 372 words, ~960 tokens.

Download SKILL.mdSave it as .claude/skills/brightdata-install-auth/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
brightdata-install-auth
description
Bootstrap Bright Data access without mixing proxy-zone credentials and REST API keys. Use when onboarding an integration, changing credential ownership, or proving least-privilege access. Trigger with: "set up Bright Data access", "configure a Bright Data zone", "separate proxy and API credentials".
allowed-tools
Read, Grep, Write, Edit, Bash(python:*)
compatibility
Requires an approved Bright Data account or offline fixtures, current Bright Data documentation, and an authorized public-data collection purpose
version
2.0.0
argument-hint
[integration-root]
model
inherit
effort
high
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, web-data, bright-data, install-auth, operations

Bright Data Access Bootstrap

Overview

Establish the product, identity, zone, target, and secret boundaries before any live collection. Native proxy clients use a zone username/password, while REST API clients use a named-user API key; treat them as different credentials with different blast radii.

Prerequisites

  • An approved public-data purpose and target allowlist
  • A Bright Data account owner who can grant only the required product and zone
  • A secret manager and a non-production validation environment

Instructions

Step 1: Inventory the access path

Read the integration and Grep for existing Bright Data hosts, environment names, and secret references. Classify each call as native proxy, Browser API, or REST API before choosing credentials.

Step 2: Define the secret contract

Write an example-only configuration that declares names but contains no values.

dotenv
BRIGHTDATA_API_KEY=
BRIGHTDATA_PROXY_USERNAME=
BRIGHTDATA_PROXY_PASSWORD=
BRIGHTDATA_ZONE=
Step 3: Bind ownership

Record the named owner, permitted zone, approved target classes, expiry or review condition, and revocation path. Do not reuse an account-wide API key when a zone credential is sufficient.

Step 4: Validate without disclosure

Use Bash(python:*) only to check that required names are present and mutually consistent; never print values. Run one separately approved smoke test through the product-specific workflow.

Tool Discipline

Use Read and Grep to inventory existing access. Use Write and Edit only for approved example, configuration, and runbook paths. Use Bash(python:*) for local presence/schema checks that never print secret values; this skill does not authorize a live request.

Show full SKILL.md (141 more words)Show less

Output

  • Credential-mode decision: native proxy or REST API
  • Named secret bindings, owner, scope, and revocation receipt
  • An approved smoke-test handoff with no credential material

Examples

For a Web Scraper API worker, bind one named-user API key in the deployment secret manager and keep proxy username/password variables absent. For a Playwright proxy client, bind only the approved zone credentials. Stop if the product or target authorization is ambiguous.

Error Handling

FailureMeaningResponse
Both credential modes are populatedIntegration boundaries are mixedSplit the clients and remove unused secrets
Zone is inactive or missingWrong account, spelling, or entitlementHave the account owner verify the zone; do not broaden access
Secret appears in logsUnsafe diagnostics or command constructionRevoke it, scrub retained output, and correct the logging path

Resources

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/.curated/brightdata-install-auth of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/official-docs.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Brightdata Install Auth next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Brightdata Install Auth compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Brightdata Install Auth this skilljeremylongshore/tons-of-skills-marketplace2.8k—~960Automated safety check: PassMIT
Proxy6VKirill/claude-lane-stack122—~3.6kAutomated safety check: PassMIT
Discover APIbrightdata/skills264—~2.4kAutomated safety check: PassMIT
Paperclippaperclipai/paperclip99k—~9.6kAutomated safety check: PassMIT
Nodejs Backend Patternsever-works/ever-works16218 repos~4kAutomated safety check: PassAGPL-3.0
OpenAPI to MCP Servermcp-use/mcp-use11k—~5.2kAutomated safety check: PassApache-2.0

Similar skills

  • Proxy6

    VKirill/claude-lane-stack

    [RU: интеграция proxy6.net — покупка/продление прокси, пул, ipauth, scraping] proxy6.net REST API — RU proxy provider for IPv4/IPv4 Shared/IPv6/MTproto.

    122 GitHub stars~3.6k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Discover API

    brightdata/skills

    Use Bright Data's Discover API — intent-ranked, AI-relevance-scored web search at scale (not keyword SERP).

    264 GitHub stars~2.4k tokensUpdated 3 days ago
    Productivity & AutomationAuto-check passed
  • Paperclip

    paperclipai/paperclip

    Interact with the Paperclip control plane API for task coordination and governance.

    99k GitHub stars~9.6k tokensUpdated today
    Backend & APIsAuto-check passed
  • Nodejs Backend Patterns

    ever-works/ever-works

    Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices.

    162 GitHub starsUsed in 18 repos~4k tokens
    Backend & APIsAuto-check passed
  • OpenAPI to MCP Server

    mcp-use/mcp-use

    Turns an OpenAPI or Swagger spec into an MCP server with the mcp-use TypeScript SDK, mapping each operation to a tool, wiring auth, testing and deploying.

    11k GitHub stars~5.2k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Use Yaak

    mountain-loop/yaak

    A skill your agent uses when the user mentions Yaak, a Yaak workspace, or the yaak command, or asks to call, hit, or smoke test HTTP/REST endpoints, save or organize API requests for reuse or manual…

    19k GitHub stars~1.9k tokensUpdated 3 days ago
    Backend & APIsAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Brightdata Install Auth

What does Brightdata Install Auth do?

Bootstrap Bright Data access without mixing proxy-zone credentials and REST API keys. Brightdata Install Auth is an agent skill from jeremylongshore/tons-of-skills-marketplace. Bootstrap Bright Data access without mixing proxy-zone credentials and REST API keys.

When should I use Brightdata Install Auth?

Brightdata Install Auth fits situations like: onboarding an integration; changing credential ownership; proving least-privilege access; with: set up Bright Data access.

How do I install Brightdata Install Auth in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill brightdata-install-auth -a claude-code`. Or copy the skill folder (skills/.curated/brightdata-install-auth in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/brightdata-install-auth in your project. Claude Code loads it when a task matches its description.

How do I install Brightdata Install Auth in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill brightdata-install-auth -a codex`. Or copy the skill folder (skills/.curated/brightdata-install-auth in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/brightdata-install-auth in your project. Codex loads it when a task matches its description.

Can I use Brightdata Install Auth in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill brightdata-install-auth -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/brightdata-install-auth, .gemini/skills/brightdata-install-auth, .github/skills/brightdata-install-auth and .opencode/skills/brightdata-install-auth in your project.

What does Brightdata Install Auth need to run?

Going by SKILL.md and its folder, Brightdata Install Auth needs credentials named BRIGHTDATA_API_KEY and BRIGHTDATA_PROXY_PASSWORD. Our summary lists: A credential in BRIGHTDATA_API_KEY. Its frontmatter pre-approves these tools: Read, Grep, Write, Edit, Bash(python:*). Compatibility (from SKILL.md): Requires an approved Bright Data account or offline fixtures, current Bright Data documentation, and an authorized public-data collection purpose.

Does Brightdata Install Auth access the network?

SKILL.md names 1 domain. As links in the text: docs.brightdata.com. This is read from the text; nothing was executed.

Is Brightdata Install Auth safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Brightdata Install Auth use?

Brightdata Install Auth is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Brightdata Install Auth use?

About 960 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 178 tokens, read only when the agent opens those files.

What are the alternatives to Brightdata Install Auth?

Skills that share tags, products or a category with Brightdata Install Auth: Proxy6 (VKirill/claude-lane-stack, 122 stars), Discover API (brightdata/skills, 264 stars), Paperclip (paperclipai/paperclip, 99k stars) and Nodejs Backend Patterns (ever-works/ever-works, 162 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Brightdata Install Auth?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.