astropy
Astropy is the core Python package for astronomy, providing essential functionality for astronomical research and data analysis.
50
40%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/astropy/SKILL.mdQuality
Discovery
22%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description reads more like a tagline for the Astropy package than a skill description. It fails to list any concrete capabilities and completely lacks trigger guidance ('Use when...'), making it very difficult for Claude to know when to select this skill over others. The domain is identifiable but the description needs substantial improvement in specificity and completeness.
Suggestions
List specific concrete actions the skill enables, such as 'Parse and manipulate FITS files, perform celestial coordinate transformations, convert astronomical units, query astronomical databases, and work with time series data.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user mentions astropy, FITS files, celestial coordinates, WCS, astronomical catalogs, or sky coordinate transformations.'
Remove the generic 'essential functionality' phrasing and replace with enumerated capabilities to improve both specificity and distinctiveness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain ('astronomy') and uses vague language like 'essential functionality' and 'data analysis' without listing any concrete actions such as coordinate transformations, FITS file handling, unit conversions, or table operations. | 1 / 3 |
Completeness | The description weakly addresses 'what' (provides essential functionality for astronomy) but never addresses 'when' — there is no 'Use when...' clause or equivalent trigger guidance, and the 'what' itself is too vague to be useful. | 1 / 3 |
Trigger Term Quality | It includes 'Astropy', 'Python', 'astronomy', and 'astronomical research' which are relevant keywords, but misses common user terms like 'FITS files', 'celestial coordinates', 'astropy units', 'WCS', or 'sky coordinates' that users would naturally mention. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Astropy' and 'astronomy' provides some distinctiveness from general data analysis or Python skills, but the vague 'data analysis' phrasing could overlap with other scientific computing or data processing skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill excels at progressive disclosure and actionability with executable code examples and well-organized references to detailed module documentation. However, it is significantly too verbose - the 'When to Use This Skill' section, the 'Core Capabilities' summaries, and the 'Key operations' bullet lists are largely redundant given that Claude already understands these concepts and the reference files exist. The content could be cut by 50%+ while preserving all useful information.
Suggestions
Remove the 'When to Use This Skill' section entirely - Claude can infer applicability from the Quick Start and Core Capabilities sections.
Collapse each 'Core Capabilities' entry to just the module name, a one-line description, and the 'See:' reference link - remove the 'Key operations' bullet lists which duplicate the reference file content.
Remove the 'Additional Capabilities' section and fold those module references into the Reference Files list at the bottom.
Cut the Best Practices list to 4-5 items that are non-obvious or astropy-specific, removing generic advice like 'use context managers' and 'prefer arrays over loops'.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~250+ lines. It explains what astropy is, lists 'When to Use This Skill' scenarios Claude already knows, describes each module's purpose redundantly (both in overview and in 'Core Capabilities'), and includes lengthy 'Key operations' bullet lists that essentially duplicate what the reference files cover. The 'Overview' section restates the description, and many sections explain concepts Claude would already understand. | 1 / 3 |
Actionability | The skill provides fully executable, copy-paste ready code examples throughout - Quick Start, coordinate conversion, FITS file reading, cosmological calculations, and catalog cross-matching are all concrete and complete with proper imports and realistic usage patterns. | 3 / 3 |
Workflow Clarity | The Common Workflows section provides clear multi-step examples, but they are essentially standalone code blocks rather than workflows with validation checkpoints. For operations like FITS file manipulation, there are no explicit validation or error-handling steps. The best practices section mentions checking WCS validity but doesn't show how. | 2 / 3 |
Progressive Disclosure | The skill has a clear overview structure with well-signaled one-level-deep references to specific module documentation files (references/units.md, references/coordinates.md, etc.). Navigation is easy with a dedicated 'Reference Files' section at the bottom and inline 'See:' links within each capability section. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
1a9f5ac
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.