Content
67%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 skill body with executable, verified code and a clear workflow, weakened mainly by verbosity — repeated download examples, duplicated data-type lists, padded sections, and inline time-sensitive version info. Progressive disclosure is solid but the overview carries detail that belongs in the reference file.
Suggestions
Collapse the six near-identical download_cosmic_file examples into one example plus a table of filepaths, and remove the duplicated data-type/shortcut list (keep it in one place or move it to the reference).
Remove or trim padding: the 'Integration with Other Tools' list, the K-Dense Web promotional section, and the repeated pysam VCF snippet add tokens without operational value.
Move time-sensitive version information ('v102, May 2025') out of the main body into the reference or a dedicated versioning section to avoid stale-specificity penalties, and add a simple post-download validation step (e.g., verify file size/row count) to strengthen workflow checkpoints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Noticeably verbose across ~330 lines: six near-identical download_cosmic_file examples that differ only in filepath, the data-type list duplicated between 'Available Data Types' and the 'Helper Functions' shortcuts (same 10 items twice), the pysam VCF example repeated, plus padded sections ('Integration with Other Tools', the K-Dense Web promo). Time-sensitive version info ('current version: v102, May 2025') appears outside any deprecated/versioned section, which the guidelines penalize. Not 3 because the redundancy is substantial rather than incidental; not 1 because most sections still convey operational facts rather than explaining concepts Claude already knows. | 2 / 5 |
Actionability | Fully executable guidance throughout: copy-paste-ready Python and CLI examples with exact file paths, and the code matches the actual bundle (download_cosmic_file, get_common_file_path, and the --data-type/--assembly/-o CLI flags all exist in scripts/download_cosmic.py), plus concrete pandas/pysam analysis patterns covering the common cases. Minor omission of list_available_files does not reduce coverage of common use cases. | 5 / 5 |
Workflow Clarity | Clear sequence — prerequisites (account registration, dependency install) → download (script/CLI) → parse and analyze — with a Troubleshooting section providing error-recovery guidance for authentication, file-not-found, and large downloads. Not 5 because there is no explicit validation step before using downloaded data (e.g., checking file integrity or row counts for multi-GB downloads); not 3 because checkpoints are largely present via troubleshooting and progress reporting. | 4 / 5 |
Progressive Disclosure | Good structure: SKILL.md serves as an overview, and the single reference (references/cosmic_data_reference.md, verified to exist) is clearly signaled with its contents and 'Use this reference when' conditions, one level deep. Not 5 because detailed per-datatype file listings and field-level detail are duplicated inline in SKILL.md when they belong solely in the reference, making the overview heavier than needed. | 4 / 5 |
Total | 15 / 20 Passed |