Content
53%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.
The body is a well-organized, honest overview with genuinely executable workflow examples and clear one-level-deep reference signaling, but it over-relies on descriptive capability bullets that restate what Claude already knows about astropy, and its reference layer is hollow — seven placeholder files that redirect to upstream docs, creating nested indirection the skill only partially mitigates by disclosing it.
Suggestions
Replace the per-module 'Key operations' bullet lists (which restate astropy's API, something Claude largely knows) with one concrete code snippet per module showing the non-obvious idiom, cutting the body substantially.
Fill the references/*.md files with the promised content (equivalencies tables, AltAz recipe, header-editing patterns) or collapse them into a single 'upstream docs' pointer file to remove the placeholder indirection layer.
Move the IERS/offline/cross-matching caveats out of the Installation section into a dedicated 'Caveats' section with a short checklist form, and add an explicit validation step to the cross-matching workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient — terse bullet lists, no 'what is astronomy' padding, executable examples without narration — but it could be tightened: the 'Reference Files' section repeats the seven 'See:' pointers already given in 'Core Capabilities', the Overview restates the description, and the 'Key operations' bullets largely enumerate library features Claude already knows about astropy. The dense 6-line paragraph about IERS/auto-download/cross-matching caveats (line 200) is shoehorned into the Installation section and reads as an unstructured wall of text. | 3 / 5 |
Actionability | Mostly executable guidance: the Quick Start plus four Common Workflows (coordinate transform to AltAz, FITS open/header access, cosmological distances, catalog cross-match) are copy-paste ready and cover the common cases, and install commands are given. It falls short of 5 because much of the body is descriptive capability bullets ('Read and modify headers', 'Create custom WCS objects') without the concrete calls for those cases, and no example shows writing output files. | 4 / 5 |
Workflow Clarity | Workflows are presented as worked code examples rather than sequenced steps with checkpoints, and validation is implicit or absent (e.g., the cross-matching workflow filters by separation but has no verify step; the caveat paragraph at line 200 mentions inspecting epochs/units/matching policy but is buried and unstructured). It is above a 2 because the workflows themselves are coherent and Best Practices includes checks like 'Check coordinate frames' and 'Check WCS validity'. | 3 / 5 |
Progressive Disclosure | Judged against the actual bundle: all seven referenced files exist, but each is a placeholder that only links to upstream astropy docs, so the effective chain is SKILL.md → references/*.md → external URLs — two levels of indirection to the real content, matching the anti-pattern 'See advanced.md for details. (In advanced.md: See details.md for the actual instructions.)'. The body honestly discloses this at line 326 and the inline content is well-signaled, which keeps it above a 1, but content that clearly should be bundled (the promised 'comprehensive documentation') is missing. | 2 / 5 |
Total | 12 / 20 Passed |