Content
63%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 highly actionable and framework-specific with a clean numbered setup workflow, concrete code for every integration point, and an excellent pitfalls section covering real failure modes. Its weaknesses are length and monolithic structure: duplicated examples, very dense run-on paragraphs, and deep-dive topics (Live Copies, poll-boost timing, saved copies) inlined in SKILL.md instead of split into reference files.
Suggestions
Move the Live Copies contract, the collab poll boost timing internals, and the "Opening from a saved copy" behavior into one-level-deep reference files (e.g., references/live-copies.md, references/sync-cadence.md), leaving a short summary and a clearly signaled link in SKILL.md.
Deduplicate the createCollabPlugin resource-mode example (shown verbatim in Security and again in Enabling step 2) and trim the "Missing access" pitfall to a one-line cross-reference to the Security section.
Break the multi-clause run-on bullets (e.g., the ~15-line "Collab poll boost" bullet and the Live Copies prose) into shorter scannable statements, keeping only timing constants and rules.
Add an explicit verification step to the setup workflow (e.g., check the Doctor output or confirm /_agent-native/collab/:docId/state returns after wiring) so the sequence ends in a checkpoint.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body assumes Claude knows Yjs/CRDT/SSE (never explains them), so it is above anchor 2, but it is still ~520 lines that could be tightened: the createCollabPlugin resource-mode example appears verbatim in both Security and Enabling step 2, the "Missing access" pitfall re-states the Security section, and dense run-on passages like the 15-line "Collab poll boost" timing bullet pad the token budget without setup-flow value. | 3 / 5 |
Actionability | The five-step "Enabling Collaboration" flow (pnpm add, server plugin, useCollaborativeDoc, TipTap extensions, optimizeDeps) is copy-paste ready and covers the common case, but several advanced snippets are illustrative fragments — "resolveRect={(edit) => /* map descriptor → DOMRect, or null */ null}", "apply: (ops) => applyGranularOps(ops)" — leaving minor gaps versus the fully-executable anchor 5. | 4 / 5 |
Workflow Clarity | "Enabling Collaboration" is a clearly numbered 1–5 sequence, and pitfalls supply error-recovery guidance ("false means delivery failed, so retry later instead of saving"), but verification is implicit — Doctor is only mentioned as flagging misconfigurations, with no explicit checkpoint after setup — which is a minor validation gap versus anchor 5. | 4 / 5 |
Progressive Disclosure | Section headers and the routes table give real structure, but the entire 23 KB skill is one inlined file: the "Live Copies" deep-dive, the "Collab poll boost" timing internals, and the ~40-line "Opening from a saved copy" subsection clearly belong in one-level-deep reference files, and no references/, scripts/, or assets/ bundle exists. | 3 / 5 |
Total | 14 / 20 Passed |