Content
100%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.
An exemplary SDK skill body: lean, fully executable REST and WebSocket examples with an explicit failure checkpoint, and high-value gotchas that capture non-obvious behavior. References are well signaled and one level deep, with nothing inlined that belongs in a separate file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section conveys Deepgram-specific knowledge Claude cannot already know (actual method names ToStream/ToFile, the linear16 raw-PCM-no-WAV-header caveat, AutoFlushSpeakDelta, ToFile clearing response.Stream). There is no padding and no explanation of basic concepts; matches the "every token earns its place" anchor. | 5 / 5 |
Actionability | Both quick starts are complete, copy-paste-ready code with usings, initialization, schema objects, and an explicit connection-failure branch; plus an install command, concrete param lists, and executable gotchas. No gaps across the common REST and WebSocket cases, so it exceeds 4's 'minor gaps'. | 5 / 5 |
Workflow Clarity | The WebSocket flow is a clearly sequenced process — subscribe, connect, explicit "if (!connected)" checkpoint with error output, SpeakWithText, Flush, Stop — and the REST flow is a single unambiguous call. This is not a destructive/batch operation, so the validation cap does not apply, and the connection check provides a real checkpoint. | 5 / 5 |
Progressive Disclosure | No bundle files exist, so the SKILL.md is the entire skill; it is cleanly sectioned with a clearly labeled References section (in-repo source files, OpenAPI/AsyncAPI specs, product docs) and an example-files list, all one level deep and easy to navigate. Inline content (quick starts, params, gotchas) is appropriately sized. | 5 / 5 |
Total | 20 / 20 Passed |