Content
75%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured, token-efficient reference skill: executable quick-start and streaming examples, concrete handler and adapter tables, and a clearly signaled map to the published docs. The main gaps are the thin webhook-setup section and reference tables inlined in the overview.
Suggestions
Add a minimal concrete webhook route example (e.g., an app/api/webhooks/slack/route.ts handler delegating to bot.webhooks.slack) so the webhook setup section matches the actionability of the rest of the body.
Trim the marketing tagline ("Write bot logic once, deploy everywhere") and the opening sentence that restates the description to tighten token efficiency.
Consider moving the full adapter inventory and community/coming-soon lists into a referenced doc (consistent with the node_modules docs pattern) and keeping only the official adapters table in the overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense tables, lists, and code with no explanation of concepts Claude already knows, but "Write bot logic once, deploy everywhere" and the opening line restating the description are minor padding that keeps it off the lean 5 anchor. | 4 / 5 |
Actionability | The quick start, streaming example, and JSX card example are executable TypeScript, and the handler/adapter tables give concrete package and factory names, but webhook setup only says "Wire those directly to your HTTP framework routes" without a concrete route example — a minor gap versus the copy-paste-complete 5 anchor. | 4 / 5 |
Workflow Clarity | A clear directive sequence is present ("Read these before writing code" with a prioritized doc list, then quick start, then handler wiring), and it correctly defers to exact API docs; no validation checkpoints are needed since the skill involves no destructive or batch operations, so it sits between the implicit-checkpoint 3 and explicit-validation 5 anchors. | 4 / 5 |
Progressive Disclosure | With no bundle files provided, the body acts as an overview that points one level deep to clearly signaled published docs (each node_modules/chat/docs/*.mdx path annotated with its topic), which is good structure; reference-style inventory tables are inlined that could be split out, leaving minor organization gaps versus the 5 anchor. | 4 / 5 |
Total | 16 / 20 Passed |