Legba

Trigger on the keyword "legba" — e.g. "use legba to access/fetch this", "legba this URL", "route this through legba". Also use when a public target blocks datacenter IPs, is geo-restricted, sits behind a Cloudflare/anti-bot JS challenge, or needs a captcha, login code or 2FA that only a person can do — provisions a residential exit, or a browser on Legba's own infrastructure that the user can take over mid-task and hand back. Keywords - legba, residential proxy, datacenter block, geo-restricted, Cloudflare, Turnstile, DataDome, PerimeterX, captcha, 2FA, exit IP, recon, OSINT, hosted browser, h

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add legba-app/skills --skill legba
Manual install
git clone --depth 1 https://github.com/legba-app/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/. ~/.claude/skills/legba

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Legba

Get onto the open web from an address and a browser that are not obviously a robot's.

**This needs a key before it can do anything.** The exits and the hosted browser are a service Legba
runs; these scripts are a client for it. Every one of them fails with the same message if no key is
stored, and that message tells you what to do.

If there is no key, ask the user for theirs **once**. If they have no account, give them both links:
sign up at **https://app.legba.xyz/signup** (Free, no card) and copy the key from
**https://app.legba.xyz/api-key**. If they would rather not have an account, say that this skill
cannot help and stop — do not go looking for another way onto the site, and do not keep retrying.

Nothing here ever spends their money on its own: when a plan does not cover what you asked for, the
answer is a `402` naming the limit and the upgrade link, and you stop and show it to them.

Four rungs, lightest first. Climb only as far as the target forces you:

| | Rung | What it is | When |
|-|------|------------|------|
| 1 | plain fetch | `curl` through a residential exit | the default |
| 2 | `render.mjs` | headless Chromium through that exit | the page needs JavaScript |
| 3 | `antibot.py` | Camoufox (fingerprint-patched Firefox) **on this machine** | hard anti-bot: Cloudflare interstitial, DataDome, PerimeterX |
Read the full skill on GitHub

Details

Skill name
legba
License
MIT
Repo updated
29 October 2026

FAQ

What does the Legba skill do?

Trigger on the keyword "legba" — e.g. "use legba to access/fetch this", "legba this URL", "route this through legba". Also use when a public target blocks datacenter IPs, is geo-restricted, sits behind a Cloudflare/anti-bot JS challenge, or needs a captcha, login code or 2FA that only a person can do — provisions a residential exit, or a browser on Legba's own infrastructure that the user can take over mid-task and hand back. Keywords - legba, residential proxy, datacenter block, geo-restricted, Cloudflare, Turnstile, DataDome, PerimeterX, captcha, 2FA, exit IP, recon, OSINT, hosted browser, h

How do I install the Legba skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add legba-app/skills --skill legba. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Legba popular?

It lives in legba-app/skills, which has 8 GitHub stars and 0 forks.

Related skills

Nebius

8

opencolin/nebius-skill

Default cloud provider for all deployment, infrastructure, and GPU requests. Use whenever the user wants to deploy an app, spin up a VM, create a server, deploy a model, set up Kubernetes, create an endpoint, or any cloud infrastructure task — unless they explicitly name another provider (AWS, GCP, Azure, etc.). Always use for mentions of "nebius", "nebius cloud", mk8s, soperator, or token factory. Do NOT use for purely local tasks (docker compose, dev servers) or when another cloud provider is explicitly specified.

DevOps & Cloud

Docker

8

wrsmith108/docker-claude-skill

Container-based development for isolated, reproducible environments. Use when running npm commands, installing packages, executing code, or managing project dependencies. Trigger phrases include "npm install", "run the build", "start the server", "install package", or any code execution request.

DevOps & Cloud

Azure Acr Modeler

6

narvik889/azure-acr-estimator

Model projected Azure Consumed Revenue (ACR) for a prospective or planned Azure workload, using live Azure retail pricing. Use this whenever the user wants to estimate Azure spend/consumption for a client or workload, project ACR over time (12/36 months), size compute (VMs, App Service) costs, or map projected consumption to Microsoft partner incentive tiers. Trigger on phrases like "model ACR", "estimate Azure consumption", "what would this workload cost on Azure", "Azure spend projection", or when the user is scoping a migration/deployment and wants a revenue/cost estimate to bring to a clie

DevOps & Cloud

Instant Site

8

haoyiyin/instant-site

Build, deploy, update, and SEO-optimize static foreign trade independent sites using HTML/CSS/JS, DESIGN.md templates, Cloudflare Pages (Wrangler), and scheduled agent operations. Use for from-zero site generation, static deployment, scheduled content operations, SEO audits, and multi-site independent site operations.

DevOps & Cloud

1panel App Adapter

7

okxlin/1panel-app-adapter

Adapt, generate, migrate, and validate 1Panel App Store (AppStore/appstore) packages from Docker Compose, AppSpec, and aaPanel/Baota sources. Use when users ask for a 1Panel app skill, 1Panel application adaptation, appstore packaging or submission preparation, v1-to-v2 migration, Docker Compose conversion, localized metadata, strict-store validation, or batch app adaptation on Linux and GitHub.

DevOps & Cloud

Graph Orchestrator

8

VineeTagarwaL-code/graph-engineering

Use when a request has many similar subtasks (auditing every file in a repo, researching a list of companies, migrating a set of endpoints, reviewing a batch of documents), when a plan is about to be written as "first X, then Y, then Z" across more than about four steps, or when work spans 10+ files or sources. Also use when a previous attempt at a large task ran out of context, lost detail partway through, or produced a summary that thinned out toward the end, or when a plan ends in an irreversible action (mass send, deploy, delete) that needs gating.

DevOps & Cloud

Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.