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".

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

90%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, highly actionable deployment skill with concrete commands, config keys, and pitfalls. It loses a little on workflow clarity (no explicit validation checkpoint before production deploy) and progressive disclosure (external rather than bundled references).

Suggestions

Add an explicit validation checkpoint before the production deploy step (e.g. 'verify config with `langbot config check` or that all three services are healthy before exposing the endpoint').

Pull the config.yaml key table and runtimes/flags detail into a bundled reference file under references/ and link to it one level deep, keeping SKILL.md as an overview.

Add a short verify step after `docker compose --profile all up` (e.g. check :5300 responds and Box :5410 is reachable) so the workflow has a feedback loop.

Dimension	Reasoning	Score
Conciseness	Lean operational prose with no padding or explanations of basic Docker/Kubernetes concepts; every line carries specific config keys, ports, env overrides, or pitfalls Claude would not already know.	5 / 5
Actionability	Copy-paste ready commands (docker compose --profile all up, openssl rand -hex 32), exact config keys with defaults, port mappings, and ENV__ overrides cover the common deployment cases concretely.	5 / 5
Workflow Clarity	The Docker Compose path gives a clear clone→cd→up sequence and a pitfalls section that acts as a checklist, but there is no explicit validate-then-proceed feedback loop for the risky production/sandbox deploy.	4 / 5
Progressive Disclosure	Well-organized into clear sections with signaled pointers (docker/kubernetes.yaml, docs/API_KEY_AUTH.md, langbot-mcp-ops, langbot-dev), though references point to out-of-tree files rather than a one-level-deep bundle and some reference material (config table, runtimes) is inlined.	4 / 5
	Total	18 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, complete description: it states concrete capabilities, gives explicit 'Use when' guidance, and lists natural trigger phrases scoped to a distinct niche. No vague fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — Docker / Docker Compose, Kubernetes, the config.yaml model, the Box sandbox runtime, the plugin runtime, and the global API key — covering the deploy/configure domain comprehensively rather than with generic verbs.	5 / 5
Completeness	Clearly answers both 'what' (deploy and configure a LangBot instance…) and 'when' (Use when installing, deploying, upgrading, or configuring LangBot…) with concrete trigger phrases attached.	5 / 5
Trigger Term Quality	Explicit triggers ("deploy langbot", "langbot docker", "langbot compose", "langbot kubernetes", "langbot config.yaml", "langbot box runtime", "langbot global api key") are natural phrases a user would actually say, with the langbot-qualified variants covering the common cases.	5 / 5
Distinctiveness Conflict Risk	The langbot-prefixed triggers carve a clear niche for production/self-hosted LangBot deployment with minimal overlap risk against other skills.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: langbot-app/LangBot
Path: skills/skills/langbot-deploy/SKILL.md
Commit: 267232c

Reviewed: 7 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.