langbot-skills-maintenance

Maintain the langbot-skills repository with low duplication. Use when adding, editing, or auditing LangBot skills, references, cases, troubleshooting entries, indexes, or periodic entropy-control checks for this skills repository.

Jump to install

Repository: langbot-app/LangBot
Last source activity: June 20, 2026 at 07:14
Detected SKILL.md language: English
Stars: 17,430
Forks: 1,551

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/langbot-app/LangBot --skill langbot-skills-maintenance

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

2 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

langbot-space-ops

Browse and search the LangBot Space marketplaces (plugins, MCP servers, skills) through the Space MCP server. Use when an AI agent needs to discover LangBot extensions on space.langbot.app over MCP. Covers the /mcp endpoint, Personal Access Token (PAT) auth, the tool surface, and client configuration. Triggers on "langbot space mcp", "search langbot plugins", "langbot marketplace mcp", "space.langbot.app mcp".

2026-08-12

langbot-deploy

Deploy and configure a LangBot instance — Docker / Docker Compose, Kubernetes, the config.yaml model, the Box sandbox runtime, the plugin runtime, and the global API key. Use when installing, deploying, upgrading, or configuring LangBot in production or self-hosted environments. Triggers on "deploy langbot", "langbot docker", "langbot compose", "langbot kubernetes", "langbot config.yaml", "langbot box runtime", "langbot global api key".

2026-08-11

langbot-dev

Develop, build, and debug the LangBot core backend and web frontend. Use when working inside the LangBot repository — backend (Python/Quart, src/langbot/pkg), the Vite/React web UI, HTTP API controllers/services, Alembic migrations, or the MCP server. Covers the dev environment (uv, pnpm), repo layout, the API auth model (user token / API key / global key), adding API endpoints, and the rule that API changes must update the MCP server and skills. Triggers on "langbot backend", "langbot dev", "langbot api", "add langbot endpoint", "langbot migration".

2026-07-30

View all from this repository

LangBot Skills Maintenance

Use this skill before changing reusable assets in this repository.

Workflow

Read AGENTS.md, skills/.env, and the relevant existing skill files.

Classify the change:

SKILL.md for routing and concise operating rules.
references/*.md for canonical detailed workflows.
cases/*.yaml for executable test-plan skeletons.
suites/*.yaml for reusable groups of case ids.
fixtures/fixtures.json for deterministic fixture readiness metadata.
reports/evidence/<run-id>/automation-result.json as automation output and reports/evidence/<run-id>/result.json as final judgment output; neither is a catalog asset to commit.
troubleshooting/*.yaml for one reusable failure mode.

Search existing assets before adding new files:

rg "<feature|error|case id>" skills
bin/lbs case list
bin/lbs suite list
bin/lbs fixture list

Put detail in one canonical place and link to it from cases or routing bullets.

Run the checks in AGENTS.md after edits.

Entropy Rules

Prefer extending an existing reference or troubleshooting entry when the root cause is the same.

Keep cases short: setup, action, evidence, pass/fail checks. Do not paste long prompts or debug transcripts when a reference exists.

Put machine-checkable inputs in env, automation_env, or fixtures; put operator-confirmed assumptions in preconditions so test plan can surface manual_check.

Keep suites short: title, intent, tags, and ordered case ids. Do not duplicate case steps inside a suite.

Keep fixture manifests factual: id, title, path, kind, and related case ids. Do not encode environment-specific absolute paths.

Keep troubleshooting entries narrow: symptoms, patterns, likely causes, fixes, related assets.

Do not hardcode local ports, browser profile paths, secrets, tokens, or provider keys.

Use bin/lbs index --check to verify the committed index is current without writing it; run bin/lbs index when the index needs regeneration.

For periodic repository audits, read references/curation-workflow.md.