langbot-plugin-dev

Develop, debug, and test LangBot plugins. Use when creating new LangBot plugins, fixing plugin bugs, setting up a LangBot test environment, or testing plugins via WebSocket. Covers plugin component architecture (EventListener, Command, Tool), the plugin SDK API (invoke_llm, get_llm_models, send_message, plugin storage), common pitfalls, and automated WebSocket-based testing. Triggers on "langbot plugin", "lbp", "GroupChatSummary", "plugin debug", "langbot test".

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

71%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.

The body is highly actionable with executable code throughout and clear sequencing for debugging and restart operations. It is held back by duplicated restart-timing content, inlined bulk that belongs in reference files, and missing explicit validation checkpoints in the deployment workflow.

Suggestions

Split the 'Critical SDK Pitfalls' catalog and 'API Quick Reference' into separate files under references/ (e.g. references/sdk-pitfalls.md, references/api-quick-ref.md) and summarize them in SKILL.md with one-level-deep links.

Merge the duplicate container-restart guidance in 'Plugin Hot-Reload' and 'Container Restart Timing' into a single authoritative section to remove redundancy.

Add explicit validation checkpoints to the test-environment workflow (e.g. 'verify plugin listed via GET /api/v1/plugins' before moving to WebSocket testing).

Dimension	Reasoning	Score
Conciseness	Prose is lean and assumes Claude's competence (no 'what is a plugin' filler), but container restart timing is documented twice (Plugin Hot-Reload and Container Restart Timing sections) and a large API reference plus the 10-pitfall catalog are inlined rather than split out.	3 / 5
Actionability	Pervasive copy-paste-ready code: corrected ❌/✅ SDK pitfalls, EventContext handler snippets, WebSocket send/receive payloads, and curl commands with concrete request bodies; the referenced test-env-setup.md is real and consistent.	5 / 5
Workflow Clarity	Clear sequences exist (numbered debugging checklist, container restart order with a warning about not restarting both simultaneously), but the deploy→configure→test flow delegates to the reference and lacks explicit validation checkpoints beyond the debugging checklist.	4 / 5
Progressive Disclosure	Section headers are clear and references/test-env-setup.md is signaled once, but only one reference file exists while large API reference and pitfall-catalog content that clearly belongs in separate files is inlined in SKILL.md.	3 / 5
	Total	15 / 20 Passed

Description

92%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.

The description is specific, well-triggered, and fully answers both 'what' and 'when' with concrete trigger phrases. It is clearly distinct from generic skills. Only minor: a few natural synonyms could be added to the trigger list.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Develop, debug, and test LangBot plugins') plus named component types ('EventListener, Command, Tool') and specific SDK APIs ('invoke_llm, get_llm_models, send_message, plugin storage'), giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers 'what' (plugin component architecture, SDK API, pitfalls, WebSocket testing) and 'when' ('Use when creating new LangBot plugins, fixing plugin bugs, setting up a LangBot test environment, or testing plugins via WebSocket').	5 / 5
Trigger Term Quality	Triggers on 'langbot plugin', 'lbp', 'GroupChatSummary', 'plugin debug', 'langbot test' — good natural-term coverage, but a few common synonyms a user might say are missing.	4 / 5
Distinctiveness Conflict Risk	A clear LangBot-plugin niche with specific component/SDK triggers (e.g. 'lbp', 'GroupChatSummary') that are unlikely to fire for unrelated skills; minimal conflict risk.	5 / 5
	Total	19 / 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-plugin-dev/SKILL.md
Commit: 7803d56

Reviewed: about 3 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.