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 highly actionable, well-sequenced deployment walkthrough with concrete commands at every step and explicit validation checkpoints including a thoughtful read-only vs. mutating auth distinction. Its main weaknesses are structural: everything lives in one file with no progressive disclosure, and error-recovery paths for failed migrations or stuck provisioning are not addressed.
Suggestions
Move the per-language connection examples to a references file (e.g. references/connection-examples.md) and keep only one inline example plus a pointer, tightening the main body.
Add explicit error-recovery guidance: what to do when a --queries-file migration statement fails (inspect the error, fix the SQL, re-run) and how to poll or react when `cloud service get` shows a state other than 'running'.
Give a concrete readiness check command (e.g. the actual grep/jq invocation against `cloud service get` output) instead of the vague "You can grep the 'state' field".
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is efficient — every step leads with a concrete command and minimal framing, and the marketing-style blockquote is scripted user-facing text rather than explanation for Claude — but the three full per-language connection examples (Python, Node.js, Go) and the six-step console walkthrough for API key creation could be trimmed or offloaded. | 4 / 5 |
Actionability | Fully executable throughout: copy-paste commands for install (`curl -fsSL https://clickhouse.com/cli | sh`), both auth modes, `cloud service create --name <service-name>`, `--queries-file` schema migration, SHOW TABLES / DESCRIBE verification, plus complete client snippets in three languages covering the common connection cases. | 5 / 5 |
Workflow Clarity | A clearly ordered six-step sequence with real checkpoints — wait for user account confirmation, verify auth with `cloud org list`, wait for service readiness, verify deployment with SHOW TABLES/DESCRIBE — and prominent warnings that mutating operations require API key auth. It stays at 4 rather than 5 because there are no error-recovery loops (what to do when a migration query fails or the service never reaches 'running'), which the rubric flags as especially important for database operations; validation is present, so the missing-validation cap at 3 does not apply. | 4 / 5 |
Progressive Disclosure | No bundle files exist (no references/, scripts/, or assets/), so everything — including ~45 lines of per-language connection code and the detailed API-key creation walkthrough — is inlined in a single ~220-line SKILL.md. Section headers are clear, but content that would sit better in a one-level-deep reference is inline and there are no external references to signal, matching the 'could be better organized' anchor. | 3 / 5 |
Total | 16 / 20 Passed |