Content
63%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, code-dense reference skill whose snippets Claude could not reconstruct from prior knowledge, with strong async/wait/error patterns and a well-signaled doc-index reference. Its weaknesses are redundancy (a link table and URL-pattern explanation each duplicated), a broken reference to a nonexistent examples/ directory, and missing safeguards around destructive operations. The contradictory CLI version requirement (frontmatter '>= v1.0.0' vs body '0.278.0') is an internal consistency defect.
Suggestions
Delete the 'Quick Reference Links' table and fold the duplicated URL-pattern explanation into one place — the per-section doc links and references/doc-index.md already cover it.
Fix or remove the reference to `examples/` — the directory does not exist in the bundle; either add the worked examples or point to references/doc-index.md alone.
Reconcile the CLI version requirement: the frontmatter says 'Requires databricks CLI (>= v1.0.0)' while the body says '0.278.0 or higher'.
Add a brief pre-delete safeguard pattern (e.g., verify cluster_id via w.clusters.get before delete) to the destructive-operation examples.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The bulk is dense, genuinely non-obvious SDK guidance (Claude cannot know these patterns), but there is real waste: the 16-row 'Quick Reference Links' table duplicates the doc link already given in every per-API section and in references/doc-index.md; the URL pattern is explained twice ('SDK Documentation Architecture' and again in 'When Uncertain'); the opening line restates the frontmatter; and unpinned version numbers ('0.278.0 or higher', contradicting the frontmatter's '>= v1.0.0') are time-sensitive. Not 2 because almost nothing explains concepts Claude already knows; not 4 because the duplicated link table and repeated URL-pattern sections are clearly trimmable. | 3 / 5 |
Actionability | Nearly every section gives copy-paste-ready, real code: full client construction for four auth modes, per-API CRUD snippets, WRONG/CORRECT asyncio.to_thread examples, three wait patterns, and try/except error handling. Not 5 because a few snippets are not verbatim-executable — `StatementState.SUCCEEDED` is used without its import, and the pagination example imports `ListJobsRequest` but never uses it; not 3 because these are isolated minor gaps in otherwise complete, concrete guidance covering all common cases. | 4 / 5 |
Workflow Clarity | The layout follows a sensible sequence (environment setup → configuration → usage → common patterns → a 'When Uncertain' section that prescribes fetch-and-verify before answering, a genuine validation loop), and error-handling/wait patterns supply checkpoints for fragile long-running operations. Not 5 because destructive operations (w.clusters.delete, dbutils.fs.rm recurse=True) are shown without safeguards or pre-validation steps, and setup has no verify-auth-before-first-use check; not 3 because verification guidance and error-recovery patterns are explicitly present. | 4 / 5 |
Progressive Disclosure | The signature-table bulk is correctly split into references/doc-index.md and clearly signaled ('For a per-API table of method signatures and direct doc URLs... see references/doc-index.md'), which is anchor-4 behavior. However, the body still inlines substantial bulk reference content (the 16-row Quick Reference Links table, the URL-pattern architecture section), the referenced `examples/` directory ('Worked examples... live under examples/') does not exist in the bundle — a broken navigation path — and the assets/ files are never referenced. These place it at 'some structure but could be better organized' rather than 'minor organization gaps'. | 3 / 5 |
Total | 14 / 20 Passed |