Content
78%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 strong, highly actionable body: executable code everywhere, version-specific gotchas, a breaking-changes section, an error table, and a checklist. Its weaknesses are length — much of the security, OGM, and subscriptions material should live in reference files like search-directives.md does — and the absence of explicit validation loops around destructive mutation workflows.
Suggestions
Move the Security (@authentication/@authorization) and OGM sections into separate reference files (e.g., references/security.md, references/ogm.md), keeping only the constructor/config essentials inline, to mirror the successful search-directives.md pattern and shrink the ~490-line body.
Add an explicit validation checkpoint after destructive or batch operations (e.g., 'after deleteMovies, verify counts with a query before proceeding') so workflows include a validate-then-proceed loop rather than relying only on the Common Errors table.
Trim the Schema Control Directives and Nested Mutations sections to one-line pointers plus a single example each; the full syntax can live in a reference file, reducing token cost without losing actionability.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with non-obvious, version-pinned specifics (v7 explicit 'eq' syntax, breaking-changes table, security-patch versions) and confines time-sensitive version info to a Version Matrix / 'v6 → v7 Breaking Changes' section, with almost no padding of concepts Claude already knows. Not 5 because sections like Schema Control Directives and the OGM CRUD walkthrough could be trimmed or delegated without losing actionability. | 4 / 5 |
Actionability | Fully executable throughout: copy-paste install commands, a complete minimal server setup, full directive syntax with annotated gotchas ('columnName must exactly match the RETURN alias — mismatch returns null silently'), a Common Errors table with cause/fix pairs, and a final checklist. Covers the common cases concretely. | 5 / 5 |
Workflow Clarity | Sequenced steps ('Step 1 — Install', 'Step 2 — Minimal Server Setup', security Steps 1–3) plus checkpoints ('wrap in try/catch', the checklist, and the error-recovery table) give a clear sequence with most checkpoints present. Not 5 because destructive/batch operations (deletes, nested mutations) lack an explicit validate-after-operation loop — validation is implied via the error table rather than stated as validate-then-proceed steps. | 4 / 5 |
Progressive Disclosure | The one bundle file (references/search-directives.md) is real, one level deep, and well signaled in two places, but the ~490-line body inlines substantial content that belongs in separate reference files (security/@authorization, OGM, subscriptions), leaving SKILL.md closer to a monolithic reference than an overview. This matches the level-3 anchor ('content that should be separate is inline') better than level 4. | 3 / 5 |
Total | 16 / 20 Passed |