Content
86%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 reference skill: executable examples throughout, a clear API-selection decision table, and clean progressive disclosure to real, one-level-deep reference files. The only costs are redundant gotcha coverage (Common Mistakes table + Checklist restate inline examples) and missing explicit feedback loops around batch/database operations.
Suggestions
Collapse the 'Common Mistakes' table and final 'Checklist' into a single section — they restate the inline ❌/✅ examples nearly verbatim, and one combined checklist would cut ~40 lines without losing coverage.
Add an explicit post-write verification step to the 'Batch Writes with UNWIND' section (e.g., checking summary.counters.updates().nodesCreated against the input array length) to provide the feedback loop expected for batch database operations.
Show a brief retry/recovery pattern for session.run failures (e.g., catching SERVICE_UNAVAILABLE and re-running once), since it is the one API without auto-retry and currently has no recovery guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and code-dense with no basic-concept padding, but the 13-row 'Common Mistakes' table and the 13-item 'Checklist' largely restate the inline ❌/✅ guidance, giving a third pass over the same gotchas that could be trimmed. Version-gated notes ('6.3.0+', 'Node 20+') add further tokens, so it sits just below the 'every token earns its place' anchor. | 4 / 5 |
Actionability | Every section ships copy-paste-ready executable code covering the common cases: driver construction with all auth options, all three query APIs, error-code dispatch, TypeScript annotations, and UNWIND batch writes. The '❌/✅' pairs make correct and incorrect usage immediately actionable. | 5 / 5 |
Workflow Clarity | The 'Choose the Right API' decision table sequences API selection, and explicit checkpoints exist (verifyConnectivity() fail-fast, session.close() in finally, error-code handling, counters verification, closing checklist). However, there is no explicit validate→fix→retry feedback loop, and the batch UNWIND section shows no post-write verification step, so it falls short of the top anchor for a database-operations skill. | 4 / 5 |
Progressive Disclosure | The body is a well-organized overview with five one-level-deep references, all of which exist on disk, each introduced with a one-line scope description; 'When NOT to Use' also routes to the RxJS reference. Verified no nested references (only an external GitHub link), so navigation is clean. | 5 / 5 |
Total | 18 / 20 Passed |