Content
92%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 strong, highly actionable skill body: executable examples throughout, an explicit routing decision procedure with validation checkpoints, and exemplary progressive disclosure via a trigger-based navigation table. The only real weakness is repetition — the install-cost rationale and version-check guidance are each stated twice, keeping it just short of maximal token efficiency.
Suggestions
State the REST-vs-install cost rationale once (in Data Access Options) and have the Overview routing gate simply reference it, removing the duplicated ~77 MB / pandas / pyarrow / duckdb explanation.
Consolidate the repeated check_version.py guidance (Overview, MCP Server section, Best Practices, Troubleshooting) into a single canonical mention plus the routing gate, trimming near-duplicate sentences.
Tighten the longest multi-clause sentences (e.g., the REST row-cap and version-compatibility paragraphs) into shorter statements or table rows.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and high-value — join tables, argument-order gotchas, exact endpoints, licensing obligations — and avoids explaining concepts Claude already knows. However, the REST-vs-install rationale (the ~77 MB install cost) and the check_version.py guidance each appear in both Overview and Data Access Options, and several long multi-clause sentences could be tightened. This is "efficient with minor instances that could be trimmed" (4), not the lean every-token-earns-its-place level (5). | 4 / 5 |
Actionability | Nearly everything is executable as written: complete SQL queries, a fully copy-paste-ready curl block for the REST path, a correct end-to-end download example that explicitly corrects the most common mistake (DataFrame vs UID list), exact method signatures, and concrete troubleshooting commands. The examples cover the common cases (query, download, visualize, license, cite, no-install metadata), matching the fully-executable 5 anchor rather than the minor-gaps 4. | 5 / 5 |
Workflow Clarity | The core workflow is stated explicitly (query with sql_query → download_from_selection → get_viewer_URL) and the routing gate is a numbered decision procedure with a hard validation checkpoint ("A launch failure is not a pass"). Batch download operations carry safeguards — size checks, LIMIT-first testing, verify UIDs exist, resume/retry guidance — and the Troubleshooting section provides issue→cause→solution feedback loops, so the batch-operation cap does not apply. | 5 / 5 |
Progressive Disclosure | The Quick Navigation table gives each of the 13 reference guides an explicit "When to Load" trigger, every inline references/*.md and scripts/check_version.py path resolves to a real bundled file, and the bulk detail (BigQuery, REST endpoints, pathology, clinical joins) lives in those one-level-deep guides rather than inline. This is a clear overview with well-signaled references and easy navigation. | 5 / 5 |
Total | 19 / 20 Passed |