CtrlK
BlogDocsLog inGet started
Tessl Logo

langbot-testing

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.

73

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplary routing/index skill body: concise, highly actionable with specific commands and env vars, well-structured progressive disclosure to real reference files, and sequenced workflows with validation checkpoints. The only slight gap is that some workflow validation relies on implicit understanding rather than fully explicit feedback loops.

DimensionReasoningScore

Conciseness

The body is a lean routing index plus a tight rules list with no concept explanation or padding; every line is actionable guidance (env vars, commands, file references), assuming Claude's competence and earning the 'lean and efficient' top anchor.

5 / 5

Actionability

Concrete, copy-paste-ready commands appear throughout (e.g. `bin/lbs fixture check`, `bin/lbs suite start <suite-id>`, `bin/lbs test result <case-id>`, `bin/lbs suite report <suite-id> --evidence-dir <dir>`) alongside specific env vars and file paths, covering the common cases per the top anchor.

5 / 5

Workflow Clarity

Sequenced workflows with validation checkpoints are present (run preflight before the release-gate suite; suite start → test result → suite report; "Do not mark a case pass until test result --evidence covers every value in evidence_required"), giving a clear sequence with most checkpoints, though the body is primarily a routing index so some validation is implicit rather than fully spelled out.

4 / 5

Progressive Disclosure

SKILL.md is a clear overview with 14 well-signaled, bold-labeled, one-level-deep references (all verified to exist as real files in ./references/), plus routing to a sibling skill and CLI commands, matching the 'clear overview with well-signaled one-level-deep references' top anchor.

5 / 5

Total

19

/

20

Passed

Description

87%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, third-person description that clearly states both capability and trigger conditions with concrete, domain-specific language. It is comprehensive and highly distinguishable, with only minor room to expand action specificity and trigger synonyms.

DimensionReasoningScore

Specificity

"Test LangBot WebUI and core product flows with an automated browser and backend logs" names the domain plus several concrete actions (WebUI testing, core flow testing, automated browser, backend logs), with only minor coverage gaps, matching the 'lists several specific actions' anchor rather than the fully comprehensive 5.

4 / 5

Completeness

It explicitly answers 'what' ("Test LangBot WebUI and core product flows with an automated browser and backend logs") and 'when' ("Use when validating... or troubleshooting failed LangBot end-to-end tests") with concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

The 'Use when' clause covers many natural phrases a user would say ("LangBot frontend", "pipeline Debug Chat", "model provider setup", "test buttons", "knowledge-base UI flows", "troubleshooting", "end-to-end tests"), giving good keyword coverage with a few synonyms/extensions missing, so it sits at 4 rather than the fully comprehensive 5.

4 / 5

Distinctiveness Conflict Risk

The LangBot-specific niche with distinct triggers (Debug Chat, model provider test buttons, knowledge-base UI) creates a clear niche with minimal conflict risk against other skills, matching the top anchor.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
langbot-app/LangBot
Reviewed

Table of Contents

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.