Agent skill

LangBot Environment Setup

by langbot-app in langbot-app/LangBot

Prepares a LangBot development and testing environment for an agent, covering service startup, proxy settings and browser access through Computer Use or Playwright MCP.

Apache-2.0Auto-check: notesDevelopment

Install LangBot Environment Setup

skills CLI
$ npx skills add langbot-app/LangBot --skill langbot-env-setup -a claude-code

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

GitHub CLI
$ gh skill install langbot-app/LangBot langbot-env-setup --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/langbot-app/LangBot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/skills/langbot-env-setup .claude/skills/langbot-env-setup && 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
langbot-env-setup
GitHub stars
18k
Token cost
~496 tokens
SKILL.md length
207 words
Files
8 (incl. references)
Skills in repo
9
Repo updated
First seen
Licence
Apache-2.0

At a glance

Prepares a LangBot development and testing environment for an agent, covering service startup, proxy settings and browser access through Computer Use or Playwright MCP.

  • Getting LangBot running before testing or verifying a change
  • SKILL.md covers Routing and Rules
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Setting up Playwright MCP browser access for the LangBot WebUI

What it does

The skill routes an agent to reference notes depending on the situation. It always starts by choosing a browser-control path: Computer Use when available, which needs little extra setup, or Playwright MCP when browser automation is required. Other notes cover LangBot service checks and startup, WSL specifics, shared local variables read from a `.env` file and proxy settings for when external logins, model provider tests or package downloads time out.

Login handling is deliberate: for GitHub OAuth the agent opens a visible browser and lets you complete the credential steps yourself, never handling a password, passkey, recovery code or 2FA secret. A fixed browser profile path is reused so later sessions can reach the logged-in WebUI, and headless automation is used only once a profile already holds a valid login. Setup counts as finished only when the LangBot services respond and the profile can open the WebUI.

When your agent uses it

  • Getting LangBot running before testing or verifying a change
  • Setting up Playwright MCP browser access for the LangBot WebUI
  • Keeping a persisted Chrome profile logged in through GitHub OAuth
  • Configuring proxy variables when downloads or logins time out

Example prompts

  • “Set up the LangBot dev environment under WSL and start the backend and frontend.”
  • “I need a persistent browser profile logged in to LangBot through GitHub so you can test the WebUI.”
  • “Package downloads keep timing out; configure the proxy settings for LangBot.”

Requirements

  • WSL or Linux
  • A LangBot checkout with its shared .env file
  • Playwright MCP or a Computer Use capable agent for browser access

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    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

    No URLs in SKILL.md.

    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.

Context cost

LangBot Environment Setup loads about 496 tokens when it runs, and up to ~2.6k if it reads all its reference files. Until then it costs about 86 tokens; SKILL.md has 207 words of instructions outside code blocks.

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

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:12
    - **Shared local variables**: read `../.env` before using URL, path, browser profile, or proxy defaults.

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 langbot-app/LangBot at commit 40a3a94, republished under its Apache-2.0 licence (© langbot-app). 207 words, ~496 tokens.

Download SKILL.mdSave it as .claude/skills/langbot-env-setup/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
langbot-env-setup
description
Prepare a local LangBot development and testing environment for an AI agent. Use when setting up WSL or Linux development, shared local URL variables, proxy variables, backend/frontend startup, Playwright MCP browser access, GitHub OAuth browser login, persisted Chrome profiles, or future Codex computer-use environment paths.

LangBot Environment Setup

Use this skill when a task needs LangBot to be in a testable state before product testing or development verification.

Routing

  • Shared local variables: read ../.env before using URL, path, browser profile, or proxy defaults.
  • Always start here: read references/browser-access-selection.md to choose the browser-control path.
  • LangBot service checks and startup: read references/service-startup.md.
  • Computer Use available: read references/computer-use.md. This path usually needs less browser/MCP setup.
  • No Computer Use, browser automation required: read references/playwright-mcp.md.
  • GitHub OAuth or persisted login profile: read references/oauth-browser-profile.md.
  • WSL-specific notes: read references/wsl-notes.md only when running under WSL.
  • Proxy setup: read references/proxy.md when external login, model provider tests, or package downloads time out.
  • Headless-only automation: use only after a profile already contains a valid LangBot login. Do not ask the agent to enter GitHub credentials or 2FA.

Rules

  • Never handle the user's GitHub password, passkey, recovery code, or 2FA secret.
  • For OAuth login, open a visible browser and let the user complete the credential steps.
  • Reuse a fixed browser profile path so the agent can later access the logged-in LangBot session.
  • Keep environment-specific paths and commands in references/, not in this file.
  • Treat environment setup as complete only after the target LangBot services are reachable and the browser profile can access the WebUI.

© langbot-app, Apache-2.0. 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 7 other files (references) in skills/skills/langbot-env-setup of langbot-app/LangBot.

  • SKILL.md
  • references/browser-access-selection.md
  • references/computer-use.md
  • references/oauth-browser-profile.md
  • references/playwright-mcp.md
  • references/proxy.md
  • references/service-startup.md
  • references/wsl-notes.md

Open the folder on GitHubat commit 40a3a94

Compare with similar skills

LangBot Environment Setup 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.

LangBot Environment Setup compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
LangBot Environment Setup this skilllangbot-app/LangBot18k—~496Automated safety check: NotesApache-2.0
Lightpandalightpanda-io/agent-skill101—~6kAutomated safety check: PassApache-2.0
Code Reviewnteract/semiotic2.7k—~1.5kAutomated safety check: PassApache-2.0
Project Pull Requestswimmwatch/cloakbrowser-mcp161—~1kAutomated safety check: PassMIT
Project Docs Maintainerswimmwatch/cloakbrowser-mcp161—~569Automated safety check: PassMIT
Project Releaseswimmwatch/cloakbrowser-mcp161—~1.9kAutomated safety check: PassMIT

Similar skills

  • Lightpanda

    lightpanda-io/agent-skill

    Lightpanda browser, drop-in replacement for Chrome-based browsing in any AI agent - faster and lighter for tasks without graphical rendering like data retrieval.

    101 GitHub stars~6k tokensUpdated 2 days ago
    Agent WorkflowsAuto-check passed
  • Code Review

    nteract/semiotic

    Review Semiotic pull requests for behavioral bugs, regressions, contract drift, and missing evidence.

    2.7k GitHub stars~1.5k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Project Pull Request

    swimmwatch/cloakbrowser-mcp

    Create, update, prepare, or review a cloakbrowser-mcp GitHub Pull Request only when the user explicitly requests PR work.

    161 GitHub stars~1k tokensUpdated 6 days ago
    DevelopmentAuto-check passed
  • Project Docs Maintainer

    swimmwatch/cloakbrowser-mcp

    Maintain, organize, consolidate, or audit the cloakbrowser-mcp documentation set only when the user explicitly requests project documentation maintenance or an authorized public change requires it.

    161 GitHub stars~569 tokensUpdated 6 days ago
    DevelopmentAuto-check passed
  • Project Release

    swimmwatch/cloakbrowser-mcp

    Prepare, publish, verify, or recover a cloakbrowser-mcp release only when the user explicitly requests release work.

    161 GitHub stars~1.9k tokensUpdated 6 days ago
    Agent WorkflowsAuto-check passed
  • Playwright Testing

    chongdashu/vibejam-starter-pack

    Plan, implement, and debug frontend tests: unit/integration/E2E/visual/a11y.

    149 GitHub stars~2.2k tokensUpdated 5 mo ago
    Testing & QAAuto-check passed

More from langbot-app/LangBot

All 9 skills in this repo
  • LangBot Plugin Development

    langbot-app/LangBot

    Guides building, debugging and testing LangBot plugins: components, SDK calls, README and locale rules, SDK pitfalls and WebSocket-based testing.

    18k GitHub stars~3.9k tokensUpdated today
    Auto-check passed
  • LangBot Deployment Guide

    langbot-app/LangBot

    Deploys and configures a LangBot instance with Docker Compose or Kubernetes, covering config.yaml, the Box sandbox runtime, the plugin runtime and the global API key.

    18k GitHub stars~1.2k tokensUpdated today
    Auto-check: notes
  • LangBot Core Development

    langbot-app/LangBot

    Covers developing the LangBot core backend and web UI: dev setup, repo layout, API auth types, adding endpoints, migrations and keeping the MCP server in step.

    18k GitHub stars~1.4k tokensUpdated today
    Auto-check: notes
  • Guides building, migrating and testing LangBot messaging-platform adapters for the Event-Based Agents layout, with unified event and message conversion.

    18k GitHub stars~4k tokensUpdated today
    Auto-check passed
  • LangBot MCP Operations

    langbot-app/LangBot

    Manages a LangBot instance over its built-in MCP server: endpoint, API-key authentication, client config and the tool set for bots, processors and more.

    18k GitHub stars~2.7k tokensUpdated today
    Auto-check passed
  • LangBot Space MCP

    langbot-app/LangBot

    Browses and searches the LangBot Space marketplaces for plugins, MCP servers and skills through its read-only MCP server, authenticated with a personal access token.

    18k GitHub stars~1.3k tokensUpdated today
    Auto-check passed

Questions about LangBot Environment Setup

What does LangBot Environment Setup do?

Prepares a LangBot development and testing environment for an agent, covering service startup, proxy settings and browser access through Computer Use or Playwright MCP. The skill routes an agent to reference notes depending on the situation. It always starts by choosing a browser-control path: Computer Use when available, which needs little extra setup, or Playwright MCP when browser automation is required.

When should I use LangBot Environment Setup?

LangBot Environment Setup fits situations like: getting LangBot running before testing or verifying a change; setting up Playwright MCP browser access for the LangBot WebUI; keeping a persisted Chrome profile logged in through GitHub OAuth; configuring proxy variables when downloads or logins time out.

How do I install LangBot Environment Setup in Claude Code?

Run `npx skills add langbot-app/LangBot --skill langbot-env-setup -a claude-code`. Or copy the skill folder (skills/skills/langbot-env-setup in langbot-app/LangBot) into .claude/skills/langbot-env-setup in your project. Claude Code loads it when a task matches its description.

How do I install LangBot Environment Setup in Codex?

Run `npx skills add langbot-app/LangBot --skill langbot-env-setup -a codex`. Or copy the skill folder (skills/skills/langbot-env-setup in langbot-app/LangBot) into .agents/skills/langbot-env-setup in your project. Codex loads it when a task matches its description.

Can I use LangBot Environment Setup 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 langbot-app/LangBot --skill langbot-env-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/langbot-env-setup, .gemini/skills/langbot-env-setup, .github/skills/langbot-env-setup and .opencode/skills/langbot-env-setup in your project.

What does LangBot Environment Setup need to run?

SKILL.md names no scripts, command-line tools or credentials: LangBot Environment Setup is instructions for the agent only. Our summary lists: WSL or Linux; A LangBot checkout with its shared .env file; Playwright MCP or a Computer Use capable agent for browser access.

Does LangBot Environment Setup access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is LangBot Environment Setup safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does LangBot Environment Setup use?

LangBot Environment Setup is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does LangBot Environment Setup use?

About 496 tokens (SKILL.md is roughly 2k 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 2.1k tokens, read only when the agent opens those files.

What are the alternatives to LangBot Environment Setup?

Skills that share tags, products or a category with LangBot Environment Setup: Lightpanda (lightpanda-io/agent-skill, 101 stars), Code Review (nteract/semiotic, 2.7k stars), Project Pull Request (swimmwatch/cloakbrowser-mcp, 161 stars) and Project Docs Maintainer (swimmwatch/cloakbrowser-mcp, 161 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains LangBot Environment Setup?

langbot-app (a GitHub organization) maintains it in langbot-app/LangBot, which has 18,043 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 7, 2026.

Source: langbot-app/LangBot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.