New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

LangBot Testing

by langbot-app in langbot-app/LangBot

Tests LangBot's WebUI and core flows through an automated browser and backend logs, with a routing table to reference guides per feature area.

Apache-2.0Auto-check: notesTesting & QA

Install LangBot Testing

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

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

GitHub CLI
$ gh skill install langbot-app/LangBot langbot-testing --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-testing .claude/skills/langbot-testing && 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-testing
GitHub stars
18k
Token cost
~1k tokens
SKILL.md length
416 words
Files
212 (incl. references)
Skills in repo
9
Repo updated
First seen
Licence
Apache-2.0

At a glance

Tests LangBot's WebUI and core flows through an automated browser and backend logs, with a routing table to reference guides per feature area.

  • Verifying the LangBot WebUI after a frontend or backend change
  • SKILL.md covers Routing and Rules
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Testing the pipeline Debug Chat or a model provider's test button

What it does

Use it when an agent has to verify LangBot behavior through the WebUI, not just by reading code. The SKILL.md is mainly a router: general WebUI testing, pipeline Debug Chat, the Dify and local agent runners, model provider setup and test buttons, plugin install and runtime smoke tests, LangRAG knowledge bases, MCP stdio tools, performance and chaos probes, workspace release gates and known failures each point to their own reference file.

Rules keep runs reproducible: read the .env file first and use LANGBOT_FRONTEND_URL and LANGBOT_BACKEND_URL instead of fixed ports, confirm both frontend and backend are running, and run bin/lbs fixture check before fixture-heavy tests. Reusable test groups come from bin/lbs suite list and suite plan, and runner release checks run the preflight case before the full release gate so configuration blockers are separated from product failures.

For driving a live instance programmatically, a companion langbot-mcp-ops skill uses the instance's MCP endpoint on port 5300, which helps set up bots, pipelines and models as fixtures. The folder carries a large set of YAML test cases.

When your agent uses it

  • Verifying the LangBot WebUI after a frontend or backend change
  • Testing the pipeline Debug Chat or a model provider's test button
  • Running a release preflight and gate for the agent runners
  • Troubleshooting a failed LangBot end-to-end test

Example prompts

  • “Test the pipeline Debug Chat in the LangBot WebUI and check the backend logs for errors.”
  • “Run the agent runner release preflight before the full release gate.”
  • “Check that the model provider test button works for the configured provider.”
  • “Show me the available LangBot test suites and plan one for knowledge base flows.”

Requirements

  • A running LangBot backend and frontend configured in the .env file
  • The bin/lbs test runner from the LangBot repository
  • A browser automation tool the agent can drive

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 Testing loads about 1k tokens when it runs, and up to ~24k if it reads all its reference files. Until then it costs about 75 tokens; SKILL.md has 416 words of instructions outside code blocks.

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

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:32
    - Read `../.env` first and use `LANGBOT_FRONTEND_URL` and `LANGBOT_BACKEND_URL` instead of hardcoded ports.

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). 416 words, ~1,004 tokens.

Download SKILL.mdSave it as .claude/skills/langbot-testing/SKILL.md (or your agent's skills folder). This skill also uses 211 other files; get the full folder from GitHub.
name
langbot-testing
description
Test LangBot WebUI and core product flows with an automated browser and backend logs. Use when validating the configured LangBot frontend, pipeline Debug Chat, model provider setup and test buttons, bot and knowledge-base UI flows, or troubleshooting failed LangBot end-to-end tests.

LangBot Testing

Use this skill when an agent needs to verify LangBot behavior through the WebUI instead of only reading code.

Routing

  • General WebUI testing: read references/web-ui-testing.md.
  • Pipeline Debug Chat: read references/pipeline-debug-chat.md.
  • Dify Runner: read references/dify-agent-runner.md.
  • Model provider setup or test button: read references/model-provider-testing.md.
  • Plugin install/runtime/tool/page smoke: read references/plugin-e2e-smoke.md.
  • Local Runner: read references/local-agent-runner.md.
  • Local Runner path coverage: read references/local-agent-runner-coverage.md.
  • Diff-aware Runner QA after code changes: read references/agent-runner-qa-workflow.md.
  • Runner release gate: read references/agent-runner-release-gate.md.
  • Sandbox-backed skill authoring: read references/sandbox-skill-authoring.md.
  • LangRAG knowledge bases: read references/langrag-knowledge-base.md.
  • MCP stdio tool testing: read references/mcp-stdio-testing.md.
  • Performance, reliability, or chaos probes: read references/performance-reliability-testing.md.
  • Cross-repository workspace and release gates: read references/workspace-release-testing.md.
  • Drive a live instance over MCP (not raw HTTP): use the langbot-mcp-ops skill — the instance exposes an MCP server at http://<host>:5300/mcp (reuses API keys). Useful for setting up bots/pipelines/models as test fixtures programmatically.
  • Known failures and fixes: read references/troubleshooting.md.
  • Reusable test groups: run bin/lbs suite list and bin/lbs suite plan <suite-id> before manually assembling a case set.

Rules

  • Read ../.env first and use LANGBOT_FRONTEND_URL and LANGBOT_BACKEND_URL instead of hardcoded ports.
  • If a standalone frontend dev server is running, LANGBOT_FRONTEND_URL may point to LANGBOT_DEV_FRONTEND_URL; otherwise it may point to the backend WebUI.
  • Confirm the backend and frontend are actually running before testing.
  • Run bin/lbs fixture check before fixture-heavy MCP, RAG, multimodal, or plugin smoke tests.
  • For runner externalization release checks, run bin/lbs test run agent-runner-release-preflight before the full agent-runner-release-gate suite so configuration blockers are separated from product failures.
  • Read Manual Readiness in bin/lbs test plan <case-id>; manual_check means the declared preconditions or setup still need operator confirmation for this run.
  • Use an authenticated browser profile prepared by langbot-env-setup.
  • Do not expose API keys, OAuth secrets, tokens, or localStorage token values in output.
  • A WebUI test is not complete until the visible UI result is checked against backend logs or network behavior.
  • A performance result is not complete without metrics evidence and a clear split between LangBot overhead and external provider/tool/network time.
  • A chaos or reliability result is not complete until the fault scope, cleanup, and recovery checks are recorded.
  • For a suite, use bin/lbs suite start <suite-id> to create the suite evidence root, per-case directories, and suite-start.json/suite-start.md handoff files; use bin/lbs test result <case-id> to write final per-case result.json, then run bin/lbs suite report <suite-id> --evidence-dir <dir>.
  • Do not mark a case pass until test result --evidence covers every value in the case's evidence_required.
  • For runner-specific Debug Chat cases, use the case-specific pipeline env declared by automation_pipeline_url_env / automation_pipeline_name_env; do not silently reuse a generic LANGBOT_PIPELINE_URL.

© 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 211 other files (references) in skills/skills/langbot-testing of langbot-app/LangBot.

  • SKILL.md
  • cases/acp-agent-runner-debug-chat.yaml
  • cases/agent-run-ledger-audit.yaml
  • cases/agent-runner-async-db-readiness.yaml
  • cases/agent-runner-behavior-matrix.yaml
  • cases/agent-runner-fixture-contract.yaml
  • cases/agent-runner-health-visibility.yaml
  • cases/agent-runner-ledger-concurrency.yaml
  • cases/agent-runner-ledger-contention.yaml
  • cases/agent-runner-ledger-invariants.yaml
  • cases/agent-runner-ledger-stress.yaml
  • cases/agent-runner-live-install.yaml
  • cases/agent-runner-qa-debug-chat.yaml
  • cases/agent-runner-release-preflight.yaml
  • cases/agent-runner-runtime-chaos.yaml
  • cases/bot-event-routing-product-flow.yaml
  • cases/box-mcp-heartbeat-recovery.yaml
  • cases/claude-code-agent-debug-chat.yaml
  • cases/codex-agent-debug-chat.yaml
  • cases/dify-agent-debug-chat.yaml
  • … and 192 more

Open the folder on GitHubat commit 40a3a94

Compare with similar skills

LangBot Testing 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 Testing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
LangBot Testing this skilllangbot-app/LangBot18k—~1kAutomated safety check: NotesApache-2.0
Diff-Driven Smoke TestsSkyvern-AI/skyvern23k—~5.2kAutomated safety check: PassAGPL-3.0
Agentic Browser Testingpetrkindlmann/qa-skills165—~4.5kAutomated safety check: PassMIT
Whole-App Health Sweepreticlehq/reticle1.2k—~1.1kAutomated safety check: PassApache-2.0
Playwright E2E Testsonyx-dot-app/onyx32k1 repos~2.8kAutomated safety check: NotesCustom licence
Hands On Testktnyt/cclsp675—~1.7kAutomated safety check: PassMIT

Similar skills

  • Diff-Driven Smoke Tests

    Skyvern-AI/skyvern

    Reads your git diff, writes a handful of happy-path browser smoke tests, runs them with Skyvern or Chrome DevTools MCP and posts screenshot evidence to the PR.

    23k GitHub stars~5.2k tokensUpdated today
    Testing & QAAuto-check passed

  • Agentic Browser Testing

    petrkindlmann/qa-skills

    Goal-driven E2E testing where a browser agent (Playwright MCP / computer-use) reads a natural-language goal and explores the app via the accessibility tree to assert outcomes — no pre-written script.

    165 GitHub stars~4.5k tokensUpdated 3 mo ago
    Testing & QAAuto-check passed

  • Whole-App Health Sweep

    reticlehq/reticle

    Sweeps a running web app by clicking every reachable control, then reports dead buttons, console errors, failed requests and mismatches between API data and the screen.

    1.2k GitHub stars~1.1k tokensUpdated today
    Testing & QAAuto-check passed

  • Playwright E2E Tests

    onyx-dot-app/onyx

    Write and maintain Playwright end-to-end tests for the Onyx application.

    32k GitHub starsUsed in 1 repo~2.8k tokens
    Testing & QAAuto-check: notes

  • Hands On Test

    ktnyt/cclsp

    Performs manual hands-on testing of a web application using playwright-cli.

    675 GitHub stars~1.7k tokensUpdated 7 mo ago
    Testing & QAAuto-check passed

  • Glance Test

    DebugBase/glance

    Run E2E browser tests on any web application using Glance MCP.

    156 GitHub stars~827 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

  • LangBot EBA Adapter Development

    langbot-app/LangBot

    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

Works with

Categories

Questions about LangBot Testing

What does LangBot Testing do?

Tests LangBot's WebUI and core flows through an automated browser and backend logs, with a routing table to reference guides per feature area. Use it when an agent has to verify LangBot behavior through the WebUI, not just by reading code.md is mainly a router: general WebUI testing, pipeline Debug Chat, the Dify and local agent runners, model provider setup and test buttons, plugin install and runtime smoke tests, LangRAG knowledge bases, MCP stdio tools, performance and chaos probes, workspace release gates and known failures each point to their own reference file.

When should I use LangBot Testing?

LangBot Testing fits situations like: verifying the LangBot WebUI after a frontend or backend change; testing the pipeline Debug Chat or a model provider's test button; running a release preflight and gate for the agent runners; troubleshooting a failed LangBot end-to-end test.

How do I install LangBot Testing in Claude Code?

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

How do I install LangBot Testing in Codex?

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

Can I use LangBot Testing 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-testing -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-testing, .gemini/skills/langbot-testing, .github/skills/langbot-testing and .opencode/skills/langbot-testing in your project.

What does LangBot Testing need to run?

SKILL.md names no scripts, command-line tools or credentials: LangBot Testing is instructions for the agent only. Our summary lists: A running LangBot backend and frontend configured in the .env file; The bin/lbs test runner from the LangBot repository; A browser automation tool the agent can drive.

Does LangBot Testing 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 Testing 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 Testing use?

LangBot Testing 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 Testing use?

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

What are the alternatives to LangBot Testing?

Skills that share tags, products or a category with LangBot Testing: Diff-Driven Smoke Tests (Skyvern-AI/skyvern, 23k stars), Agentic Browser Testing (petrkindlmann/qa-skills, 165 stars), Whole-App Health Sweep (reticlehq/reticle, 1.2k stars) and Playwright E2E Tests (onyx-dot-app/onyx, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains LangBot Testing?

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.