Content
71%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 exceptionally actionable, well-organized API reference with executable examples, common-mistake recovery patterns, and thorough error documentation. Its main weaknesses are repeated boilerplate across examples and a monolithic single-file structure that inlines several sub-features which belong in separate reference files.
Suggestions
Split self-contained sub-features (harness plugin, MCP Apps client-side UI, MCP Events, Codegen CLI) into references/ files and keep a short overview plus one canonical example per topic in SKILL.md, matching the pattern already used for docs/mcp/apps.md.
Deduplicate the repeated createMCPClient boilerplate by showing the transport config once and abbreviating later examples (e.g. 'const client = await createMCPClient({...})'), and remove the duplicated get_weather server example in the stdio section.
Tighten the clipped one-sentence-per-line prose blocks (e.g. the spec-2025/2026 behavior notes around requestInput) into compact bullets or a small spec-behavior table to reduce token cost.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with package-specific facts rather than explanations of known concepts, but it repeats boilerplate: the createMCPClient({ transport: { type: 'http', ... } }) construction with full imports appears in roughly fifteen examples, and the get_weather toolDefinition().server() example is duplicated nearly verbatim in the stdio section. | 3 / 5 |
Actionability | Every section provides copy-paste-ready, executable TypeScript or shell (install, npx generate, mcp.config.ts) covering the common cases for hosting, client use, auth, transports, pools, harness, apps, and events. | 5 / 5 |
Workflow Clarity | Task-oriented sections, three clearly ordered lifecycle options with wrong/correct Common Mistakes pairs, a numbered Codegen CLI procedure, and a full error-class catalog with causes give clear sequences and recovery guidance, but there are no explicit validation checkpoints in the workflows (not required here, as no destructive/batch operations). | 4 / 5 |
Progressive Disclosure | There are no bundle files at all — the harness plugin, MCP Apps UI, MCP Events, codegen CLI, and resources/prompts sections are all inlined in a single ~1470-line SKILL.md. Section structure and headers are good and cross-skill references are signaled, but clearly separable sub-feature content that should live in reference files is inline. | 3 / 5 |
Total | 15 / 20 Passed |