Content
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality, well-structured skill that serves as an effective hub for Lakeflow Declarative Pipelines development. Its greatest strengths are the decision tree for dataset type selection, the concrete error/fix mappings, and the excellent progressive disclosure to reference files. The main weakness is that the extensive API reference tables, while useful, add significant token weight and could potentially be moved to a separate reference file to keep the main skill leaner.
Suggestions
Consider moving the large API reference tables (Dataset Definition, Flow/Sink, CDC, Data Quality, Reading Data, Table/Schema Features) into a separate `api-reference.md` file and linking to it, keeping only the most critical 1-2 tables inline to reduce token cost.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is dense and comprehensive but could be tightened. The API reference tables are extensive and somewhat redundant (repeating the same reference file links across many rows). The decision tree and common traps sections are efficient, but the sheer volume of tables — especially the legacy migration table and the reading data APIs — pushes toward verbosity. However, it avoids explaining basic concepts Claude already knows. | 2 / 3 |
Actionability | The skill provides highly concrete, actionable guidance: exact CLI commands for running pipelines, specific API names and decorators, precise error-to-fix mappings, and clear decision trees. Code snippets are executable (e.g., `databricks bundle deploy -t dev --profile <profile>`), and the legacy migration table gives exact before/after patterns. | 3 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with explicit validation checkpoints. The 'Running a Pipeline' section has ordered steps (validate → deploy → run → check status), warns about destructive operations (full refresh data loss), requires explicit user approval for dangerous actions, and mandates polling the update rather than top-level state. The three workflow choices (A, B, C) are clearly delineated with decision criteria. | 3 / 3 |
Progressive Disclosure | The skill is an excellent overview that delegates detailed content to well-organized reference files. References are one level deep, clearly signaled with markdown links, and organized by feature and language in structured tables. The Reference Index at the bottom provides a clean navigation map. Content is appropriately split between the main skill (decision trees, common traps, workflow selection) and detailed references. | 3 / 3 |
Total | 11 / 12 Passed |