Content
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill body is highly actionable with a clear, validated workflow and concrete code/commands — its main weakness is conciseness and structure. It is long with genuine cross-section redundancy, and it leans on a single reference file where more content could be split out.
Suggestions
Consolidate the retry/throttling guidance into one section; 'Prefer the shared REST framework', 'Retry and throttling strategy', and the pitfalls entry all restate 'don't wrap tenacity around status codes', and the partition 'never use updated_at' rule is repeated three times — state each once and cross-reference.
Tighten the unreleasedSource step (currently ~20 lines) to the core rule plus one rationale; the why-it-matters detail can move to a reference or be trimmed since it is restated in the checklist.
Split large inline blocks into reference files — e.g. move the multi-schema SQL checklist and the DataWarehouseSourceCategory enum list into references/ and link to them — so the SKILL.md overview stays scannable and progressive disclosure improves.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and assumes Claude's competence (no basic-concept padding), but at ~780 lines it repeats itself: retry/throttling guidance appears in 'Prefer the shared REST framework', 'Retry and throttling strategy', and pitfalls; the 'never use updated_at' partition rule and the unreleasedSource warning are each restated several times, so it could be tightened. | 2 / 3 |
Actionability | Provides copy-paste-ready code (base-class combos, resumable/webhook patterns, canonical_descriptions, get_non_retryable_errors, connection_host_fields), exact commands (pnpm run generate:source-configs, schema:build, DEBUG=1 ./bin/migrate, ruff), and concrete file paths throughout. | 3 / 3 |
Workflow Clarity | A clearly sequenced 15-step end-to-end workflow with verification checkpoints (confirm the generated config class appears, run migrations only if needed), a dedicated 'API behavior verification checklist' feedback loop (docs AND curl), a full implementation checklist, and a 'Common pitfalls' error-recovery section. | 3 / 3 |
Progressive Disclosure | There is one well-signaled, one-level-deep reference ([references/oauth-app-deployment.md], a real bundle file) and clear section headings, but the body is largely monolithic — substantial blocks like the multi-schema SQL checklist, canonical descriptions, and the full category enum list are inline rather than split into reference files. | 2 / 3 |
Total | 10 / 12 Passed |