AWS Cdk Development
zxkane/aws-skills
AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.
Agent skill
Brightdata Upgrade Migration
by jeremylongshore in jeremylongshore/tons-of-skills-marketplace
Migrate Bright Data SDK, API, product, or response-header contracts with fixture evidence and a reversible canary.
Install Brightdata Upgrade Migration
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill brightdata-upgrade-migration -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace brightdata-upgrade-migration --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-upgrade-migration .claude/skills/brightdata-upgrade-migration && rm -rf skills-srcUse ~/.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/
Install the "brightdata-upgrade-migration" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/brightdata-upgrade-migration into .claude/skills/brightdata-upgrade-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brightdata-upgrade-migration", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/brightdata-upgrade-migrationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill brightdata-upgrade-migration -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace brightdata-upgrade-migration --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.curated/brightdata-upgrade-migration .agents/skills/brightdata-upgrade-migration && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "brightdata-upgrade-migration" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/brightdata-upgrade-migration into .agents/skills/brightdata-upgrade-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brightdata-upgrade-migration", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill brightdata-upgrade-migration -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace brightdata-upgrade-migration --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.curated/brightdata-upgrade-migration .cursor/skills/brightdata-upgrade-migration && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "brightdata-upgrade-migration" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/brightdata-upgrade-migration into .cursor/skills/brightdata-upgrade-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brightdata-upgrade-migration", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path skills/.curated/brightdata-upgrade-migration--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill brightdata-upgrade-migration -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace brightdata-upgrade-migration --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.curated/brightdata-upgrade-migration .gemini/skills/brightdata-upgrade-migration && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "brightdata-upgrade-migration" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/brightdata-upgrade-migration into .gemini/skills/brightdata-upgrade-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brightdata-upgrade-migration", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jeremylongshore/tons-of-skills-marketplace brightdata-upgrade-migrationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill brightdata-upgrade-migration -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.curated/brightdata-upgrade-migration .github/skills/brightdata-upgrade-migration && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "brightdata-upgrade-migration" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/brightdata-upgrade-migration into .github/skills/brightdata-upgrade-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brightdata-upgrade-migration", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill brightdata-upgrade-migration -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace brightdata-upgrade-migration --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.curated/brightdata-upgrade-migration .opencode/skills/brightdata-upgrade-migration && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "brightdata-upgrade-migration" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/brightdata-upgrade-migration into .opencode/skills/brightdata-upgrade-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brightdata-upgrade-migration", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
brightdata-upgrade-migration- GitHub stars
- 2.8k
- Token cost
- ~911 tokens
- SKILL.md length
- 328 words
- Files
- 2 (incl. references)
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Migrate Bright Data SDK, API, product, or response-header contracts with fixture evidence and a reversible canary.
- Works in 4 steps: Build the delta → Update one boundary → Verify compatibility → …
- Upgrading the Python SDK
- SKILL.md covers Overview, Prerequisites, Instructions and Tool Discipline, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Brightdata Upgrade Migration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Migrate Bright Data SDK, API, product, or response-header contracts with fixture evidence and a reversible canary. Use when upgrading the Python SDK, moving dataset endpoints, renaming Scraping Browser to Browser API, or removing legacy headers. Trigger with: "upgrade Bright Data", "migrate x-luminati headers", "change a Bright Data API contract".
Its SKILL.md is about 910 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 DevOps & Cloud, covering Deployment, Web scraping and API design. It works with Bright Data and Python. 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
- Upgrading the Python SDK
- Moving dataset endpoints
- Renaming Scraping Browser to Browser API
- Removing legacy headers
Example prompts
- “upgrade Bright Data”
- “migrate x-luminati headers”
- “change a Bright Data API contract”
- “/brightdata-upgrade-migration”
Requirements
- Python 3
- 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.
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:
ReadGrepWriteEditBash(python:*)
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
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 no API keys, tokens, secrets or passwords.
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 Upgrade Migration loads about 911 tokens when it runs, and up to ~1.1k if it reads all its reference files. Until then it costs about 95 tokens; SKILL.md has 328 words of instructions outside code blocks.
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). 328 words, ~911 tokens.
Download SKILL.mdSave it as
.claude/skills/brightdata-upgrade-migration/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- brightdata-upgrade-migration
- description
- Migrate Bright Data SDK, API, product, or response-header contracts with fixture evidence and a reversible canary. Use when upgrading the Python SDK, moving dataset endpoints, renaming Scraping Browser to Browser API, or removing legacy headers. Trigger with: "upgrade Bright Data", "migrate x-luminati headers", "change a Bright Data API contract".
- 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
- [current-to-target-contract]
- model
- inherit
- effort
- high
- license
- MIT
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- tags
- saas, web-data, bright-data, upgrade-migration, operations
Bright Data Contract Migration
Overview
Inventory the exact current behavior before changing dependencies or products. Treat an SDK update, API endpoint change, Browser API rename, and product migration as separate changes with separate rollback boundaries.
Prerequisites
- A pinned current dependency or configuration and documented target contract
- Golden synthetic fixtures plus representative redacted receipts
- A dual-read or feature-flag path and rollback owner
Instructions
Step 1: Build the delta
Read the lockfile, adapter, and runbooks; Grep for x-luminati, old product names, obsolete endpoints, raw vendor response coupling, and undocumented ports.
Step 2: Update one boundary
Write the target dependency, API, or header mapping. Current diagnostics use Proxy-Status and x-brd-*; Browser API replaces the former Scraping Browser name. Do not invent version transitions.
Step 3: Verify compatibility
Edit fixture tests for success, authentication, policy, throttle, lifecycle, schema, and delivery states. Use Bash(python:*) for the pinned type and test suite and compare normalized outputs.
Step 4: Canary and retire
Run an authorized feature-flag canary, compare data and operational receipts, then remove the old path only after rollback expiry and owner signoff.
Tool Discipline
Use Read and Grep for the migration inventory. Use Write and Edit for dependency, adapter, fixture, and runbook changes. Use Bash(python:*) for local tests; it does not authorize live migration traffic or credential changes.
Output
- Current-to-target contract matrix
- Passing old and new fixture comparison and canary receipt
- Rollback path plus explicit old-contract retirement decision
Examples
First replace parsing of x-luminati-error with current x-brd-error and Proxy-Status fixtures. Keep a short dual-read window for retained historical receipts, but require current fields from new live responses.
Error Handling
| Failure | Meaning | Response |
|---|---|---|
| Migration combines product and SDK changes | Failure attribution is impossible | Split the rollout into independently reversible steps |
| Golden fixture contains live data | Test evidence is unsafe | Replace it with a synthetic contract fixture |
| New path changes normalized output | Downstream behavior would drift | Hold promotion and reconcile the schema |
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-upgrade-migration of jeremylongshore/tons-of-skills-marketplace.
- SKILL.md
- references/official-docs.md
Open the folder on GitHubat commit cfae287
Compare with similar skills
Brightdata Upgrade Migration 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Brightdata Upgrade Migration this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~911 | Automated safety check: Pass | MIT | |
| AWS Cdk Developmentzxkane/aws-skills | 367 | 2 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Azure Architecture Autopilotgithub/awesome-copilot | 40k | 1 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Brightdata Proxybrightdata/skills | 264 | — | ~5.1k | Automated safety check: Pass | MIT | |
| Blocks Networkblocksnetwork/blocks-sdk | 146 | — | ~2.3k | Automated safety check: Notes | Proprietary | |
| Monitor With HaolemeHaolemeApp/Haoleme | 157 | — | ~1.3k | Automated safety check: Pass | AGPL-3.0 |
Similar skills
- Official
Azure Architecture Autopilot
github/awesome-copilot
Designs Azure infrastructure from a natural-language description, or diagrams an existing resource group, then refines the design through conversation and deploys it with Bicep.
Brightdata Proxy
brightdata/skills
Generate working code that routes HTTP requests through Bright Data proxy networks (Datacenter, ISP, Residential, Mobile) and help users decide which network and IP pool type to use (shared pool…
Blocks Network
blocksnetwork/blocks-sdk
Modify, validate, run, register, publish, consume, and troubleshoot agents on Blocks Network.
Monitor With Haoleme
HaolemeApp/Haoleme
Selectively monitor important long-running or resource-intensive commands with Haoleme by prefixing them with hao, so status, output, and completion notifications sync to the mobile app.
DDNS Build and Release Maintenance
NewFuture/DDNS
Maintains the DDNS project's GitHub Actions, Docker and Nuitka builds, packaging and release preparation without touching publishing credentials.
More from jeremylongshore/tons-of-skills-marketplace
All 3,342 skills in this repoPerforming 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.
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.
Agent Context Loader
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
Aggregating Performance Metrics
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
Analyzing Capacity Planning
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
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.
Related
Works with
Categories
Questions about Brightdata Upgrade Migration
What does Brightdata Upgrade Migration do?
Migrate Bright Data SDK, API, product, or response-header contracts with fixture evidence and a reversible canary. Brightdata Upgrade Migration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Migrate Bright Data SDK, API, product, or response-header contracts with fixture evidence and a reversible canary.
When should I use Brightdata Upgrade Migration?
Brightdata Upgrade Migration fits situations like: upgrading the Python SDK; moving dataset endpoints; renaming Scraping Browser to Browser API; removing legacy headers.
How do I install Brightdata Upgrade Migration in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill brightdata-upgrade-migration -a claude-code`. Or copy the skill folder (skills/.curated/brightdata-upgrade-migration in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/brightdata-upgrade-migration in your project. Claude Code loads it when a task matches its description.
How do I install Brightdata Upgrade Migration in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill brightdata-upgrade-migration -a codex`. Or copy the skill folder (skills/.curated/brightdata-upgrade-migration in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/brightdata-upgrade-migration in your project. Codex loads it when a task matches its description.
Can I use Brightdata Upgrade Migration 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-upgrade-migration -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-upgrade-migration, .gemini/skills/brightdata-upgrade-migration, .github/skills/brightdata-upgrade-migration and .opencode/skills/brightdata-upgrade-migration in your project.
What does Brightdata Upgrade Migration need to run?
SKILL.md names no scripts, command-line tools or credentials: Brightdata Upgrade Migration is instructions for the agent only. Our summary lists: Python 3. 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 Upgrade Migration 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 Upgrade Migration 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 Upgrade Migration use?
Brightdata Upgrade Migration 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 Upgrade Migration use?
About 911 tokens (SKILL.md is roughly 3.6k 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 185 tokens, read only when the agent opens those files.
What are the alternatives to Brightdata Upgrade Migration?
Skills that share tags, products or a category with Brightdata Upgrade Migration: AWS Cdk Development (zxkane/aws-skills, 367 stars), Azure Architecture Autopilot (github/awesome-copilot, 40k stars), Brightdata Proxy (brightdata/skills, 264 stars) and Blocks Network (blocksnetwork/blocks-sdk, 146 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Brightdata Upgrade Migration?
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.