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.
The body is a tight, actionable dev guide with concrete code, commands, real file paths, a clear numbered workflow, and validation guidance, all supported by a well-signaled reference file. It is consistently strong but leaves minor room to tighten prose, complete a few elided examples, and externalize more detail.
Suggestions
Tighten the longer prose passages (e.g., the MCP 2026-07-28 protocol-version paragraph and the reconnect subcommand narration) into terse rules to push conciseness toward level 5.
Complete the elided action examples (fill in schema/run for the `embedApp()` and `manage-draft` blocks) so the main code samples are fully copy-paste ready.
Consider moving the protocol-versioning and auth/authz detail blocks into a reference file so the main body stays an overview pointing one level deep.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body assumes Claude's competence (no explaining of MCP/OAuth/deep-links) and uses a terse Rule/Why/How/Do/Don't structure, but at ~530 lines a few prose-heavy passages (the MCP 2026-07-28 protocol paragraph, the reconnect subcommand narration) could be trimmed, matching the efficient-with-minor-over-explanation level-4 anchor rather than the every-token-earns-its-place level 5. | 4 / 5 |
Actionability | Provides concrete executable code (the `manage-draft` `link` builder, `embedApp()`, `callMcpTool`), specific commands (`npx @agent-native/core@latest connect ...`, `mcp install ...`), and real file paths, but some examples elide schema/run with `// ...schema, run...`, leaving minor gaps that fit the mostly-executable level-4 anchor. | 4 / 5 |
Workflow Clarity | The numbered How section (1, 1a, 1b, 2, 2a, 3, 4, 5) gives a clear sequence with validation guidance ("validate with a fresh tool call", "test real ChatGPT/Claude web behavior with a fresh inline render", sparse-tools/list diagnostics) and Do/Don't checklists, but the validate→fix→retry feedback loops are not fully explicit, fitting level 4 rather than the explicit-recovery-loops level 5. | 4 / 5 |
Progressive Disclosure | Clean section structure with a single clearly-signaled, verified one-level-deep reference (`references/mcp-apps-embedding.md`, "Read it before changing the `embedApp()` shell") plus pointers to related skills and source files; content is mostly appropriately split, though substantial detail (protocol versioning, auth/authz) remains inline, fitting level 4 rather than the cleanly-split level 5. | 4 / 5 |
Total | 16 / 20 Passed |