Content
82%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 dense, command-first skill body with an excellent phase-gated reading table, fully executable scaffolding and validation commands, and correct decision guidance ("When to Use What"). Deductions are minor: some repetition of naming rules and inlined manifest detail slightly bloat the main file, the validate-failure recovery loop is implicit, and one bundle cross-link is broken.
Suggestions
State the app-name rule once (Generic Guidelines) and reference it from the `apps init` and Directory Naming sections to remove the triple repetition.
Add an explicit error-recovery step after `databricks apps validate`, e.g. "If validation fails: read the error, fix app.yaml/selectors, re-run validate — only deploy when it passes" to complete the feedback loop.
Fix the broken cross-link in references/appkit/proto-first.md:312 (`references/plugin-contracts.md` should be `proto-contracts.md`) and consider moving the manifest/resources explanation into a scaffolding reference file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and imperative throughout — commands, tables, and warnings with almost no explanation of concepts Claude already knows ("LLMs already know these frameworks — the challenge is Databricks platform integration"). Not 5: the app-name rule is stated three times (Generic Guidelines, the `--name` bullet, Directory Naming) and the manifest/resources prose is wordy enough to tighten. | 4 / 5 |
Actionability | Fully executable, copy-paste-ready commands cover the common cases: `databricks apps manifest`, `databricks apps init --name ... --features ... --set <plugin>.<resourceKey>.<field>=<value>`, `npm run typegen`, `npx @databricks/appkit docs`, and `databricks apps validate --profile <PROFILE>`, plus a wrong-vs-right scaffolding example. Every referenced file in the body (11 of them) exists in the bundle. | 5 / 5 |
Workflow Clarity | "Development Workflow (FOLLOW THIS ORDER)" gives a numbered sequence with explicit validation checkpoints ("verify all queries show ✓", `apps validate`, update smoke-test selectors before validation) and the scaffolding flow (manifest → derive flags → init with `--run none`). Not 5: there is no explicit validate→inspect-error→fix→revalidate feedback loop, and the Lakebase path defers its sequence to the reference file. | 4 / 5 |
Progressive Disclosure | The "Required Reading by Phase" table maps each task to a real, one-level-deep reference file, and all 11 referenced paths exist (references/appkit/{sql-queries,frontend,appkit-sdk,trpc,lakebase,proto-first,proto-contracts,overview}.md, platform-guide.md, other-frameworks.md, testing.md). Not 5: the body inlines ~40 lines of manifest/plugin/resource detail that could live in a scaffold reference, the two Project Structure sections duplicate scaffolding content, and the bundle contains one broken link (appkit/proto-first.md:312 points to `references/plugin-contracts.md` instead of the sibling `proto-contracts.md`). | 4 / 5 |
Total | 17 / 20 Passed |