CtrlK
BlogDocsLog inGet started
Tessl Logo

chat-sdk

Build multi-platform chat bots with Chat SDK (`chat` npm package). Use when developers want to (1) Build a Slack, Teams, Google Chat, Discord, Telegram, GitHub, Linear, or WhatsApp bot, (2) Use Chat SDK to handle mentions, direct messages, subscribed threads, reactions, slash commands, cards, modals, files, or AI streaming, (3) Set up webhook routes or multi-adapter bots, (4) Send rich cards or streamed AI responses to chat platforms, (5) Build or maintain a custom adapter or state adapter. Triggers on "chat sdk", "chat bot", "slack bot", "teams bot", "google chat bot", "discord bot", "telegram bot", "whatsapp bot", "@chat-adapter", "@chat-adapter/state-", "custom adapter", "state adapter", "build adapter", and building bots that work across multiple chat platforms.

70

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

72%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 a well-organized overview with strong progressive disclosure and mostly executable examples, but the reading/build workflow lacks explicit validation checkpoints and a couple of advanced sections defer too much detail. Minor marketing prose slightly reduces token efficiency.

Suggestions

Add an explicit validation/verification checkpoint to the build flow (e.g., after wiring handlers, confirm the webhook route responds and the bot echoes a test mention before declaring setup complete) to lift workflow_clarity above 3.

Replace the marketing tagline ("Write bot logic once, deploy everywhere") and the restated intro sentence with a direct statement of what the SDK provides, to tighten conciseness toward anchor 5.

For the webhook-setup and custom-adapter sections, inline one minimal concrete example (a route handler skeleton; an Adapter interface stub) rather than only pointing at docs, to close the actionability gap toward anchor 5.

DimensionReasoningScore

Conciseness

The body is largely lean — path lists, API tables, and copy-paste code earn their place — but carries minor marketing prose ("Unified TypeScript SDK…", "Write bot logic once, deploy everywhere") that could be trimmed, fitting anchor 4 rather than the fully lean anchor 5.

4 / 5

Actionability

Executable Quick Start, streaming, and JSX card examples plus concrete package/factory tables give mostly copy-paste-ready guidance, but webhook routing and custom-adapter authoring remain abstract ("needs request verification, webhook parsing…"), leaving minor gaps at anchor 4.

4 / 5

Workflow Clarity

A loose sequence exists ("Read these before writing code" → Quick Start build flow) but there are no validation or verification checkpoints, matching anchor 3; not lower because steps are defined, not higher because checkpoints are absent.

3 / 5

Progressive Disclosure

SKILL.md acts as a concise overview pointing to clearly-signaled, one-level-deep node_modules/chat/docs/*.mdx references organized by topic, with no nested reference chains, matching the anchor-5 overview-plus-detail pattern.

5 / 5

Total

16

/

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.

The description is comprehensive and well-structured, explicitly stating both capabilities and use-when triggers with a broad set of natural keywords and distinct package identifiers. It uses appropriate third-person imperative voice throughout with no fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Build a Slack, Teams… bot", "handle mentions, direct messages, subscribed threads, reactions, slash commands, cards, modals, files, or AI streaming", "Set up webhook routes", "Send rich cards or streamed AI responses", "Build or maintain a custom adapter" — giving comprehensive coverage, matching the anchor-5 example.

5 / 5

Completeness

Explicitly answers both what ("Build multi-platform chat bots with Chat SDK") and when ("Use when developers want to…" plus a dedicated "Triggers on…" clause), matching the anchor-5 example.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases ("chat sdk", "chat bot", "slack bot", "teams bot", "discord bot", "whatsapp bot") plus package-name synonyms ("@chat-adapter", "@chat-adapter/state-", "custom adapter", "state adapter"), matching the anchor-5 standard of synonyms and identifiers.

5 / 5

Distinctiveness Conflict Risk

Clear niche (Chat SDK multi-platform bots) with distinct package-name triggers (@chat-adapter, chat sdk) that are unlikely to fire for unrelated skills, matching the anchor-5 minimal-conflict example.

5 / 5

Total

20

/

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
Kiz8-Team/open-agents
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.