Content
78%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 body with an excellent executable example and sound decision guidance for choosing access patterns. Its structural weakness is that two provided reference files (census_schema.md, common_patterns.md) are never linked, leaving the skill a self-contained overview that duplicates reference material instead of navigating to it.
Suggestions
Add a clearly signaled reference section linking [references/census_schema.md] and [references/common_patterns.md] (e.g., under 'Implementation Details': 'Full data schema: See census_schema.md'), and trim the inlined data-model/filtering details that those files already cover.
Drop or fold the 'Key Features' section into 'When to Use' and state the is_primary_data best practice once to remove redundancy and save tokens.
Add a brief verification checkpoint in the example (e.g., sanity-check returned cell counts against census_info summary counts) to give the workflow an explicit validation step.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with non-generic, skill-specific guidance (install commands, a complete runnable script, filter semantics, access-pattern selection) and does not explain background concepts Claude already knows. Minor trims are available: the 'Key Features' section substantially restates 'When to Use' and 'Implementation Details', and the is_primary_data best practice is stated twice ("always filter primary data" in the example comment and again under 'Filtering semantics'). This fits anchor 4 ("Efficient; minor instances of over-explanation that could be trimmed"); it is not 5 because of that redundancy and not 3 because the padding is genuinely minor rather than a section's worth of unnecessary explanation. | 4 / 5 |
Actionability | The body provides a complete, executable script covering the four core access patterns (open_soma with a pinned version, get_obs metadata exploration, get_anndata in-memory slice, axis_query out-of-core iteration with soma_data/soma_dim_0/soma_dim_1 semantics), plus copy-paste install commands including the optional extras variant. This matches anchor 5 ("Fully executable; copy-paste ready code or commands; specific examples cover the common cases"); it is not 4 because there are no gaps requiring the reader to fill in details for the common cases — the one intentionally brief area (experimental ML) is explicitly flagged as optional. | 5 / 5 |
Workflow Clarity | The sequence is clear: pin a version, open with a context manager, explore metadata, then choose an access pattern — with an explicit decision rule ("< ~100k cells" heuristic choosing get_anndata vs axis_query) that serves as a checkpoint. This fits anchor 4 ("Clear sequence with most checkpoints present; minor validation gaps"); it is not 5 because there are no verification or error-recovery steps (e.g., how to sanity-check cell counts or handle an invalid filter), and it is not 3 because the operations are read-only queries, so the destructive/batch validation cap does not apply and the sequence plus decision checkpoint is explicit rather than implicit. | 4 / 5 |
Progressive Disclosure | The bundle contains references/census_schema.md and references/common_patterns.md, but the body never mentions or links either file — navigation to them is absent while the 'Implementation Details' section (data model, filtering semantics, chunk schema) partially duplicates content that belongs in those references. Per the guideline to score against the actual bundle structure, this matches anchor 3 ("references present but not clearly signaled; content that should be separate is inline"); it is not 4/5 precisely because well-organized bundle references exist but are undiscoverable from SKILL.md, and it is not 2 because the body itself is well-sectioned rather than a monolithic dump. | 3 / 5 |
Total | 16 / 20 Passed |