Content
80%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 high-quality reference skill body: executable SQL, strong progressive disclosure, and efficient structure. Its main gap is the absence of validation checkpoints for the irreversible UniForm/CLUSTER BY table-property operations, which limits workflow clarity.
Suggestions
Add explicit validation checkpoints to the UniForm-enable and CLUSTER BY workflows (e.g., 'After ALTER TABLE, run DESCRIBE EXTENDED to confirm universalFormat.enabledFormats and Iceberg metadata generation before proceeding').
Tighten the long MUST bullet contrasting PARTITIONED BY vs CLUSTER BY into a short table or bulleted sub-points so the two syntax differences read at a glance.
Surface a brief 'verify reader compatibility before switching compression codec / format-version' step in the Common Issues entries that involve irreversible format changes.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly lean and well-organized with tables, tight MUST/MUST NOT rules, and executable SQL, assuming Claude's prior knowledge; the long run-on critical-rule bullet contrasting PARTITIONED BY vs CLUSTER BY could be tightened to earn the top score. | 4 / 5 |
Actionability | Provides copy-paste-ready, executable SQL across the common cases (managed Iceberg with PARTITIONED BY and CLUSTER BY on v2/v3, plus UniForm ALTER TABLE TBLPROPERTIES) alongside a capability matrix and a When-to-Use routing table. | 5 / 5 |
Workflow Clarity | Routing via 'When to Use' and MUST/MUST NOT guardrails gives a clear decision sequence, but the destructive/irreversible table-property workflows (enabling UniForm, disabling deletion vectors, CLUSTER BY changes) lack explicit validate-then-proceed checkpoints, which caps this dimension per the batch/destructive guideline. | 3 / 5 |
Progressive Disclosure | Serves as a concise overview pointing to five well-signaled, one-level-deep reference files through both a Reference Files table and a When-to-Use routing table; all referenced paths verified to exist and content is appropriately split. | 5 / 5 |
Total | 17 / 20 Passed |