Content
88%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.
An exemplary operational runbook: fully executable steps, an explicit gating pre-flight, validation at every stage, and error-recovery guidance tied to exact failure signatures. The only weaknesses are mild verbosity in two long passages and references to bundle files that are not actually present alongside SKILL.md.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and almost entirely project-specific (seam versions, gateway route scoping, directive fences) with no teaching of known concepts, but a few passages — the credential-gateway paragraph and the HTTP/2 troubleshooting bullet — are long clause-chains that could be tightened without losing information. | 4 / 5 |
Actionability | Every step is an exact executable command: the 'node -e' compatibility predicate, the full nc:copy file manifest, the nc:append barrel imports, the '@cursor/sdk@1.0.28' pin, vitest/bun test invocations, the contract-verifier command, and platform-specific restart instructions — copy-paste ready with no gaps. | 5 / 5 |
Workflow Clarity | A pre-flight compatibility guard ('If it prints no, stop and tell the operator') gates every later directive via 'when:cursor_core_ready=yes', and the install → build/test → authenticate → use sequence carries explicit validation (registration/conformance/gateway-proxy suites, the contract verifier) plus a troubleshooting section with exact error strings and their remediations. | 5 / 5 |
Progressive Disclosure | Well-organized sections with clearly signaled one-level links ('[REMOVE.md](REMOVE.md)', '[docs/provider-migration.md](../../docs/provider-migration.md)'), but those referenced files and the 'payload/' tree are absent from this bundle, and the deep HTTP/2/egress troubleshooting detail is inlined where a separate reference file would serve better. | 4 / 5 |
Total | 18 / 20 Passed |