Content
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable skill that provides concrete, executable guidance for every supported editor and transport mode. Its main weakness is length — the repeated JSON config blocks for editors with identical structure inflate the token count unnecessarily. The workflow is well-sequenced with smart validation checkpoints (especially the smoke test advice about empty databases), and the troubleshooting table is excellent.
Suggestions
Collapse editors that share identical JSON structure (Claude Code, Claude Desktop, Cursor, Windsurf, Antigravity, Cline) into a single template block with a table mapping editor → config file path, reducing ~60 lines of repetition.
Consider extracting the HTTP transport section and per-editor config paths into a separate reference file to reduce the main skill's token footprint.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient and provides genuinely useful information (absolute path rationale, editor-specific configs), but there's significant repetition across editor configs — Claude Code, Claude Desktop, Cursor, Windsurf, Antigravity all share the same JSON structure and could be collapsed. The APOC section and some env var explanations are slightly verbose but not egregiously so. | 2 / 3 |
Actionability | Excellent actionability throughout: every step has concrete, copy-paste-ready commands and JSON configs. Installation, credential verification, editor configuration, smoke testing, and HTTP transport all have executable examples with specific paths, commands, and expected outputs. | 3 / 3 |
Workflow Clarity | The 5-step installation workflow is clearly sequenced with explicit validation checkpoints: verify connectivity before configuring (Step 2), restart editor (Step 4), smoke test with a specific query that works even on empty DBs (Step 5). The troubleshooting table and final checklist provide excellent error recovery guidance and verification steps. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and a logical flow, but it's a long monolithic file (~250 lines) with no bundle files. The per-editor configs, HTTP transport details, and troubleshooting could be split into separate referenced files. However, for a skill with no bundle, the section organization and table of env vars are reasonable. | 2 / 3 |
Total | 10 / 12 Passed |