Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/brightdata-install-auth

@820dfc8
Run it yourself

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".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/brightdata-install-auth

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈81 tokens for metadata: the name and description. ≈764 when used: this file. ≈178 more on demand in 1 file.

Description uses 4.1% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈326 characters, or 4.1%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.

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.

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

Failure Meaning Response
Both credential modes are populated Integration boundaries are mixed Split the clients and remove unused secrets
Zone is inactive or missing Wrong account, spelling, or entitlement Have the account owner verify the zone; do not broaden access
Secret appears in logs Unsafe diagnostics or command construction Revoke it, scrub retained output, and correct the logging path

Resources

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill provides standard instructions for configuring Bright Data proxy authentication. It follows security best practices by recommending environment variables for secret management and ensuring sensitive files are excluded from version control via .gitignore. It downloads a required SSL certificate from a legitimate service domain.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 20 hours ago.

Activeupdated 2 months ago
What it can do
Reads files Edits files Runs commands
Modelinherit
version
2.0.0
argument-hint
[integration-root]
model
inherit
All 5 allowed tools
ReadGrepWriteEditBash(python:*)
Other metadata
effort
high
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
[
  "saas",
  "web-data",
  "bright-data",
  "install-auth",
  "operations"
]
compatibility
Requires an approved Bright Data account or offline fixtures, current Bright Data documentation, and an authorized public-data collection purpose

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/brightdata-install-auth