Content
65%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is highly actionable, packed with executable SQL, but its reference structure is undercut by missing bundle files and it lacks an explicit validation feedback loop for the destructive/batch SQL operations it demonstrates.
Suggestions
Consolidate the Quick Reference and Reference Files tables, which both list the same five files and their contents, into a single table to remove redundancy and tighten the SKILL.md body.
Add an explicit validation feedback loop for destructive/batch SQL (e.g. MERGE, INSERT, CREATE PROCEDURE): a sequenced 'run via execute_sql_multi -> review errors -> fix -> re-validate' workflow rather than a single guideline bullet.
Add the five referenced files (sql-scripting.md, materialized-views-pipes.md, geospatial-collations.md, ai-functions.md, best-practices.md) to the bundle so the progressive disclosure chain resolves, and consider moving some of the inline Common Patterns examples into those files to slim the overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly dense, executable SQL with little conceptual padding, but the Quick Reference and Reference Files tables redundantly enumerate the same five files, and ~11 full inline code examples overlap the reference files' purpose, so it could be tightened rather than earning the lean anchor 3. | 2 / 3 |
Actionability | It provides fully executable, copy-paste-ready SQL across stored procedures (with DECLARE EXIT HANDLER), materialized views with scheduling, pipe syntax, AI functions, http_request, read_files, and recursive CTEs, matching the executable anchor 3. | 3 / 3 |
Workflow Clarity | It is organized as a pattern catalog rather than a sequenced workflow, and validation appears only as a single guideline bullet ('Use MCP tools (execute_sql, execute_sql_multi) to test and validate all SQL before deploying') with no structured validate->fix->retry loop for destructive/batch ops like MERGE and INSERT, capping it at 2. | 2 / 3 |
Progressive Disclosure | The structure is well-signaled with a one-level-deep 'When to Read' reference table (an anchor-3 pattern), but verification shows the five referenced files (sql-scripting.md, materialized-views-pipes.md, etc.) are not present in the bundle, so the disclosure chain does not resolve to real content. | 2 / 3 |
Total | 9 / 12 Passed |