Content
53%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.
The body is exceptionally actionable — complete, executable YAML for every Rill driver with exact properties, ports, and credential patterns — but it is a 1,900-line monolith in which the same driver information is repeated across three sections, capped by a ~1,380-line raw JSON schema inlined verbatim. There is also no sequenced creation workflow or validation step for connector setup. Moving the schema and per-driver reference into separate files and adding a quick-start sequence would transform it.
Suggestions
Move the full JSON schema (lines 523-1904) into a separate reference file (e.g. references/schema.md) and replace it with a one-line pointer, keeping SKILL.md as a lean overview; this alone removes ~72% of the token load.
Deduplicate the Driver-Specific Notes and Examples sections — either merge each driver's key properties into its example or keep notes only and cut the redundant example variants (e.g. three ClickHouse examples that restate the dev/prod guidance already shown in Core Concepts).
Add a short sequenced quick-start workflow with a validation checkpoint, e.g. 1. create connectors/<driver>.yaml, 2. add credentials to .env, 3. reference them via {{ .env.* }}, 4. verify the connector reconciles successfully before building downstream models.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The same information is presented three times: Driver-Specific Notes (lines 88-207), an Examples section that largely duplicates them (209-521), and a ~1,380-line raw JSON schema dump (523-1904) restating every property with descriptions. It avoids score 1 because nothing explains concepts Claude already knows — the material is genuinely domain-specific — but the massive duplication and padding place it firmly at "noticeably verbose; several unnecessary padded sections". | 2 / 5 |
Actionability | The body provides 25+ complete, copy-paste-ready YAML examples covering every driver, exact ports (8443/9440/9000), exact property names, {{ .env.* }} templating syntax, DSN formats with character-escaping rules, and an openssl recipe for Snowflake private keys. This matches "Fully executable; copy-paste ready code or commands; specific examples cover the common cases". | 5 / 5 |
Workflow Clarity | There is no sequenced process for creating a connector (write connectors/*.yaml, add secrets to .env, deploy, verify) and no validation or verification step anywhere — nothing tells Claude how to confirm a connector reconciles or connects. Preventive guidance exists ("Use mode: read ... to prevent unintended modifications", dev managed: true to avoid overwriting prod), keeping it above score 2, but checkpoints are missing or implicit, matching anchor 3. | 3 / 5 |
Progressive Disclosure | No bundle files exist, and the body is a monolith: a "## Reference documentation" section inlines a ~1,380-line JSON schema (72% of the file) that clearly belongs in a separate reference file. Top-level headers keep it above score 1's "impossible to navigate", but the anchor-2 condition — "content that clearly belongs in separate files is inlined" — dominates at this scale; at 1,900 lines the file cannot serve as a lean overview. | 2 / 5 |
Total | 12 / 20 Passed |