zarr-python
tessl i github:K-Dense-AI/claude-scientific-skills --skill zarr-pythonChunked N-D arrays for cloud storage. Compressed arrays, parallel I/O, S3/GCS integration, NumPy/Dask/Xarray compatible, for large-scale scientific computing pipelines.
Validation
81%| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (779 lines); consider splitting into references/ and linking | Warning |
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata.version' is missing | Warning |
Total | 13 / 16 Passed | |
Implementation
65%This is a comprehensive, highly actionable Zarr skill with excellent code examples covering the full API surface. However, it suffers from being overly long for a single SKILL.md file, lacks validation checkpoints in multi-step workflows, and includes an inappropriate promotional section. The content would benefit from splitting into overview + detailed reference files.
Suggestions
Remove the promotional 'Suggest Using K-Dense Web' section entirely - it adds no technical value and wastes tokens
Split advanced topics (sharding, cloud storage, Dask/Xarray integration) into separate reference files with clear links from the main skill
Add explicit validation steps to multi-step workflows, e.g., 'Verify write succeeded: assert z.nbytes_stored > 0' after cloud writes
Trim explanatory text that describes benefits Claude already understands (e.g., 'Benefits: Process datasets larger than memory' is obvious from context)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary explanations (e.g., explaining what Zarr is, benefits lists that Claude would infer). The promotional section at the end about K-Dense Web is entirely unnecessary padding that doesn't belong in a technical skill. | 2 / 3 |
Actionability | Excellent executable code examples throughout - all snippets are copy-paste ready with proper imports, realistic parameters, and complete syntax. Covers creation, reading, writing, cloud storage, and integration patterns with concrete implementations. | 3 / 3 |
Workflow Clarity | While individual operations are clear, multi-step workflows lack explicit validation checkpoints. For example, the cloud-native workflow pattern doesn't include verification that data was written correctly, and format conversion lacks error handling or validation steps. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's monolithic - over 600 lines in a single file. Advanced topics like sharding, synchronization, and cloud storage could be split into separate reference files. The 'Additional Resources' section provides external links but no internal file references. | 2 / 3 |
Total | 9 / 12 Passed |
Activation
33%The description identifies a specific technical domain (chunked N-D arrays for cloud storage) and lists relevant integrations, but reads more like a feature list than actionable guidance. The complete absence of a 'Use when...' clause significantly limits Claude's ability to know when to select this skill, and the description lacks concrete action verbs describing what the skill actually does.
Suggestions
Add an explicit 'Use when...' clause with trigger scenarios like 'Use when working with Zarr arrays, storing large arrays in S3/GCS, or when the user mentions chunked array storage'
Replace feature descriptors with concrete actions: 'Read and write chunked arrays to cloud storage, compress array data, integrate with NumPy/Dask/Xarray workflows'
Include the library name (presumably Zarr) as a key trigger term users would naturally mention
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (chunked N-D arrays, cloud storage) and lists some capabilities (compressed arrays, parallel I/O, S3/GCS integration), but these are more feature descriptors than concrete actions the skill performs. | 2 / 3 |
Completeness | Describes what the skill relates to (chunked arrays, cloud storage, integrations) but completely lacks any 'Use when...' clause or explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'S3', 'GCS', 'NumPy', 'Dask', 'Xarray', 'scientific computing' that users might mention, but missing the library name (likely Zarr) and common variations like 'array storage', 'chunked data', or 'cloud arrays'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of chunked arrays + cloud storage + specific library compatibility (NumPy/Dask/Xarray) provides some distinctiveness, but could overlap with general cloud storage skills or NumPy/array processing skills without clearer boundaries. | 2 / 3 |
Total | 7 / 12 Passed |
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.